Dashboard > SAS: Science Analysis Systems > Home > Computing Schedule and Uptime Needs
  SAS: Science Analysis Systems Log In View a printable version of the current page.  
  Computing Schedule and Uptime Needs
Added by Richard Dubois, last edited by Rob Cameron on Jul 12, 2007  (view change)
Labels: 
(None)

 This page attempts to block out the noticeable episodes of computing and their priority and need for resource availability.

Instrument Related - Pre Launch

What When Resource Uptime Needed
vibe/acoustic
 
TVAC Aug-Sept (40 days)
up to 8 hr outages allowed
Kennedy Ops
   

ISOC testing - Pre-launch

What When
Resource Uptime Needed
ETE3 August 2007 (2 days)
uptime needed
ETE4 Oct 2007 (2 days)
uptime needed
ETE5   uptime needed
ETE6   uptime needed
ISOC Ops Sim 1
Oct 2007 (about 4 days)
uptime needed
ISOC Ops Sim 2
Dec 2007 (about 4 days)
uptime needed

 Flight Operations Post Launch

What When Resource Uptime Needed
First 2 weeks
Feb "Guaranteed" up
Next 6 weeks
Through to end March
 
Routine Ops
April onwards
up to 8 hrs; max 48 hrs

Simulations

What When Resource Uptime Needed
Preparations for 1 year run Several bursts of 1-3 farm-days, July-Aug
Advance notice for up to a few days' outage
Backgrounds for 1 year run 3 weeks in Sept
Advance notice for < 1 day outage
1 year run
3 weeks in Oct
Advance notice for < 1 day outage
ISOC test datasets
More bursts of 1-3 farm days, July-Sept
Advance notice for up to a few days' outage
Post ISOC test/pre launch datasets
end Oct - Jan
Advance notice for up to a few days' outage
     
     

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.8 Build:#814 Oct 02, 2007) - Bug/feature request - Contact Administrators