From SEDSWiki

Questions for the general meeting on 2007/12/30

1. When will we get feedback from the design review eg. anything that the CC has identified which we need to improve on?

2. A few weeks ago in a general meeting, we discussed power available, and Power agreed to work out the estimated power per orbit. On the Power wiki page they've now got a figure of 8183 Joules per orbit. This works out at a maximum of 1.3 Watts (average) power consumption per orbit. First, is this correct? Second, would it be worth all the teams doing a quick check of their estimated energy usage, then making sure these numbers all fit within the allocated power budgets? Maybe making a table which breaks down the estimated energy usage per orbit of each subsystem?

3. Can Power hard-wire the backup battery to Communications, so that we are guaranteed power even if everything else fails (at least until the battery runs out)?

4. I think all of our suggested requirements at http://wiki.seds.org/index.php/SEDSAT-2_Requirements_Communications look reasonable. If nobody disagrees with them, I'd like to put them into protoforge and finalize them. In particular:

4.1 The final requirement, an operating temperature range of 0-70 degrees, assumes that somebody else will ensure the thermal environment inside SEDSAT-2 will never exceed these limits. Will Structures take charge of Thermal Control, or do we have to increase the operating temperature range in our spec to -100 to +125 (the LEO temperature range), and then provide our own thermal control?

5. We're beginning to produce things - diagrams, schematics, matlab code etc... Do we have access to a versioning repository for storing this data (eg. SVN or CVS), so we can check-in/check-out files to a central location where they get backed-up, get roll-back access to earlier versions, allow multiple people to work on the same files etc... This will become increasingly important as development begins to really kick off, especially given the distributed nature of all of the teams. Perhaps just get an account at sourceforge with one sub-directory for each team? Or maybe Aaron/Kirk have access to a SVN server we could use?