12.07.2015 Views

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.5.1 ReliabilityFigure 4-12. <strong>GP</strong>-B Computer Network.The computer hardware performed near flawlessly during the <strong>Gravity</strong> <strong>Probe</strong> B mission. The moc-server had anuptime of 290 days before a breaker was accidentally tripped during a routine cleanup causing a reboot.During the IOC phase of the mission, two hardware malfunctions occurred, both involving hard drives. ThePOD E5 client disk failed, as did the Science server boot disk. Both disks were replaced within 45 minutes, andno data were lost.During the science phase of the mission, several computer power supplies failed, but were replaced within 2hours (MOC specifications require 24 hour turn around time). The SUN blade computers, the main class ofcomputer on both the MOC and Science Networks, performed exceptionally well.No problems were reported during the calibration phase of the mission.Despite repeated attempts, neither network was ever compromised by hackers. Logs routinely showed hackerattempts on our clients connected to the open IONET. However, our firewall did an excellent job keepinghackers off our science net – not a single entry was recorded.4.5.2 Disk Storage IssuesDisk storage proved a particular problem during the <strong>Gravity</strong> <strong>Probe</strong> B mission, with space requirementsconsistently underestimated.The extension of the IOC phase did cause several problems for the hardware group, although more from amanagement standpoint than from equipment concerns. In particular, prior to launch, the decision was madeto lock down all hardware modifications, even though disk usage was close to maximum. Considering a 44 dayIOC, the decision to increase disk storage after IOC seemed reasonable. Unfortunately, increased storage needsdue to an extended IOC caused disk usage to max out several times. User disk storage space was increasedshortly after the end of IOC, and has been sufficient.The <strong>GP</strong>-B database was similarly stressed, as storage requirements increased and necessary databasemaintenance postponed. Fortunately the database was fully checked out several weeks prior to launch, andefficiently managed during IOC. Prelaunch predictions underestimated the amount of data to be stored,requiring the acquisition of significantly more data base storage space.<strong>Gravity</strong> <strong>Probe</strong> B — <strong>Post</strong> <strong>Flight</strong> Analysis • Final <strong>Report</strong> March 2007 119

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!