Example of such an orbit plan is below:
The details of each observing mode are still to be provided by SoloHI.
|Observing modes - Example plan||Use case||#images / day||Science data volume / day||SoloHI data rate||Observing duration / orbit|
|(Gbits) estimate||(kbits/s)||(days) example|
|Perihelion programs:||0.28-0.29 AU|
SoloHI Solar Wind Turbulence @perih
SoloHI Shock Formation @perih
|Near-Perihelion programs:||0.29-0.36 AU|
|SoloHI Near-perihelion Synoptic Program||348||1.69||20.3||5|
|SoloHI Solar Wind Turbulence Near-perihelion||750||1.94||23.2||2|
|SoloHI Shock Formation Near-perihelion||516||2.45||29.3||2|
|SoloHI Far-Perihelion Synoptic Program||132||1.64||19.7||7|
|Southern Out-of-ecliptic programs:||0.5-0.7 AU|
|SoloHI Southern Synoptic Program||104||0.84||10.3||8|
Examples of more-detailed observing program for 1 type of orbit during the mission (source: 04_130904_SoloHI_CDR_ObsProg.ppt):
Based on table above:
- a typical perihelion programme would produce 24.7kbps (during 4 days),
- near-perihelion SoloHI would produce ~20kbps (during 8 days) ,
- 18.4kbps even further out (during 12 days) and
- in the far-out RSwindow, a datarate of typically 8.5kbps would be reached.
(see also SoloHI concept study report Dec 2011 )
How to organize SoloHI observations in coordination with the other instruments, i.e. does SoloHI have 'observing modes' to choose from for each solar distance?, is still to be discussed in more detail. Also, while the schema above may be optimal from a science perspective, the varying downlink rate & SSMM storage limits may impose limitations on when which datarate can be used.