Science Activity Plan. Yannis Zouganelis & The Solar Orbiter SOC

Transcription

1 Science Activity Plan Yannis Zouganelis & The Solar Orbiter SOC

2 Science Activity Plan We have a first draft! Yannis Zouganelis & The Solar Orbiter SOC

3 The Science Activity Plan The SAP is the strategic plan detailing which science objectives will be addressed and how throughout the mission. We need a plan to make sure that: We address all of Solar Orbiter s science objectives. The mission is feasible in terms of operational constraints and downlink. We make smart use of resources by going beyond EID-A average rates when possible. We know how many communications passes to request and when. MOC have enough information to plan resources. The SAP isn t set in stone, it can be updated by the SWT via mission level planning. BUT the SAP should be a feasible operational plan that will work unless circumstances change. We won t start from scratch every six months. The SAP is the responsibility of the SWT.

4 The Science Activity Plan / Current status All science objectives have been detailed and approved. Dedicated meetings held for Objectives #1 and #2: Science activities defined. At Objective #2 meeting, the RS working group suggested that it would be beneficial to first define common sets of observations that could then be used to address multiple sub-objectives. After these discussions, Project Scientists and SOC defined these common sets of observations from multiple instruments (SOOPs). They fully cover Objectives #1 and #2. Objective #3 discussions held today and new SOOPs defined. Today we present a first version of the SAP (v0): All SOOPs for Obj. 1-3 are defined. All sub-objectives are mapped to SOOPs. All SOOPs have been scheduled throughout the Nominal Mission Phase. We have simulated it (SSMM, TM, instrument stored data volumes) and it works*!

5 The Science Activity Plan / Current status You can find all details in Confluence SOC Public pages.

6 How to build a mission-long SAP? SolO s (sub)objectives SOOPs 10 instruments, many modes Step 1 SOOP A SOOP B SOOP C EPD normal+burst EUI/HRI AR mode MAG Normal Metis GLOBAL PHI/HRT NOM 0 RPW normal+burst SOOP D Step 2 Strategy 10 years mission timeline B A A A D To be checked against mission constraints Step 3 Simulation

7 Step 1 SUB-OBJECTIVES GROUPED IN SOOPS

8 Sub-objectives grouped into SOOPs A SOOP Solar Orbiter Observing Plan is the analogue of a SoHO JOP and Hinode HOP. Project Scientists and SOC have worked together to produce a menu of SOOPs that, as near as possible, addresses all the Solar Orbiter sub-objectives A SOOP is a set of common operations from multiple instruments: i.e., a collection of instrument modes and parameters. It can be reused during different orbital opportunities. It can therefore address several mission sub-objectives at once One SOOP many sub-objectives Different objectives may need different targets/orbital opportunities Rule of thumb: if even one instrument changes mode, this constitutes a different SOOP

9 SOOP ingredients: Observations I The SOC s first goal is to coarsely assess the feasibility of the Science Activity Plan In order to do this, available resources Telemetry downlinked (not necessarily same as acquired) Power consumed... and constraints GAM, EMC requirements (TBC), Metis compatibility, communications rolls need to be respected. SOC therefore models them throughout the mission. At this level, resources are attached to coarse-grained Observations

10 Examples of Observations Modelled SPICE observations include: Composition Mapping, Dynamics, Spectral Atlas, In situ observations typically contain normal mode and a parameterised duration of burst mode per day Limb mode, CME Watch, 30"-wide Movie, 90 -wide Movie, Waves mode, Two-Exposure mode, Full Raster Scan Each observation has associated values for each resource Telemetry Power

11 SOOP ingredients: Observations II Each SOOP is scheduled with an assumed duration in SAP v0. This is obviously not final, but allows us to begin process of modelling, so that we can be ready for SAP v1 SOOPs need to be portable across the mission for: optimisation of the Mission-Level Plan; SWT decides science priorities SOC models feasibility responsiveness to wrinkles in the mission; reusability. Not every instrument is necessarily needed in a SOOP. SOOPs can run in parallel Instruments can make individual observations when not needed for the coordinated campaigns

12 SOOP naming convention Rather than adopting a previous schema, we use a mnemonic system which names SOOPs according to the system: I/R/L_FULL/SMALL/BOTH_L/M/Hres_L/M/Hcad_description In Situ (only) / Remote Sensing (only) / Linkage between the two SOOP focussed on FULL / SMALL FoV, or BOTH Low/Medium/High spatial resolution Low/Medium/High temporal cadence Lastly, a description to cover the main intent of the observations, as loosely as possible so not to exclude any of the intended subobjectives The name may not reflect exactly what comes to your mind when you see it for the first time, but it is indicative of the observations.

13 L_SMALL_HRES_HCAD_SlowWindConnection Instrument Mode Comments EUI Metis EUI/HRI Coronal hole mode (C) EUI/FSI Synoptic mode (S) (FSI) MAGTOP or GLOBAL for context & to link solar wind source regions to S/C HRI (C) at 1 min cadence FSI (S) throughout Only applicable if beyond ~0.5AU during target tracking PHI PHI_HRT_MODE_2 Regularly spaced HRT data at med- to hires. PHI LL magnetograms needed throughout SoloHI HI_SYN_NEAR SPICE SPICE_WIND_CONNECT* Dynamics & SPICE Composition Mapping. Raster area should be optimized to make sure open-closed field boundary is captured STIX STX_NORMAL not strictly needed for SOOP although context is appreciated EPD Close mode + Scheduled/triggered burst MAG Normal + Scheduled/triggered burst RPW normal + scheduled/triggered burst selective downlink useful SWA normal + scheduled/triggered burst

14 Mapping Objectives to the SOOP L_SMALL_HRES_HCAD_SlowWindConnection

15 How to build a mission-long SAP? SolO s (sub)objectives SOOPs 10 instruments, many modes Step 1 SOOP A SOOP B SOOP C EPD normal+burst EUI/HRI AR mode MAG Normal Metis GLOBAL PHI/HRT NOM 0 RPW normal+burst SOOP D Step 2 Strategy 10 years mission timeline B A A A D To be checked against mission constraints Step 3 Simulation

16 Step 2 SOOPS SCHEDULED IN MISSION TIMELINE

17 How We Built SAP v0 Eventually the SAP will contain a high level schedule of which SOOPs we expect to run when. Of course, this will depend on the trajectory we end up flying. However, we need a trajectory-independent framework that groups SOOPs in terms of their constraints and required opportunities e.g., Quadrature with Earth, High TM rate This is what we call the SAP Planning Strategy and what we (SWT + PS + SOC) will apply when filling a given trajectory with SOOPs and building the SAP. We ve written a first draft strategy and applied that to Option E to produce SAP v0. Right now, the best way to contribute to the SAP is to comment on the strategy.

18 SAP Planning Strategy / Default IS SOOP The following SOOP will run continuously: I_DEFAULT: scheduled throughout the mission. The in situ instruments will always contribute to this SOOP. They may contribute to other SOOPs at the same time.

19 SAP Planning Strategy / High res perihelia Objectives that need high resolution, high cadence RS observations at perihelion with good TM downlink. Different types of targets, mostly off-pointing. RS burst SOOP (R_SMALL_HRES_HCAD_Rsburst): Highest TM SOOP: x EID-A rate. Need good TM at perihelion or just after. 10 minutes (repeated several times when possible, for some objectives several hours are needed). EUI, PHI, SPICE, STIX (no SoloHI, no METIS). All triggers disabled. For some objectives (energetic particles) need of a few short bursts into a series of RS windows for probability reasons. This is the most demanding version of this SOOP. 5 MTPs identified (2 for the most demanding version): early years + one high latitude opportunity ( ).

20 SAP Planning Strategy / Earth-directed CMEs CME & blobs structure and propagation objectives. SoloHI & METIS required. Need SolO in quadrature and SoloHI looking towards Earth. 4 possibilities (+1 at 45 degrees separation angle).

21 SAP Planning Strategy / Slow Connectivity requiring Earth context for modeling pre-rsw. At solar minimum: Most favorable magnetic field configuration for these objectives. Early orbits: SolO close to the ecliptic. Full solar magnetic field configuration can be modeled if PHI observes the far side magnetic field and we combine with the Earth side magnetic field. The location of the HCS will determine the connected hemisphere. During the campaign, PHI keeps taking full disk magnetograms to update the magnetic field model. Improvement as Earth and SolO see overlapping longitude ranges. Plan early in the mission (solar minimum). Only 1 good orbit (2022/07/ /01/01) and 1 less optimal.

22 SAP Planning Strategy / Slow wind min 1/2 As the Sun becomes more active, the magnetic field modeling becomes more challenging. Rely more on Earth observations for a well-constrained model 4 days in advance. Proposed strategy: Start early but also plan later in the mission, towards solar maximum to explore other types of solar wind source regions. Due to more complicated and less reliable modeling, use pointing mosaics to establish the most likely connection point.

23 SAP Planning Strategy / Slow wind min 2/2 During later orbits, the concatenated perihelion + North windows will span a large range of latitudes over a short period of time (is this an asset or not?). Possibilities in 8-10 windows.

24 SAP Planning Strategy / Fast wind Mostly targeting at coronal holes. Low-latitude extended coronal hole would increase the chance of connection and possible to compare composition of low and fast wind streams: better in the declining phase. Fast scan through big range of latitudes (pole-to-pole opportunities). Best opportunity: 2026/01/ /07/01 Almost continuous observations from 5 May 19 June Pole to pole (31º) Perihelion at 0.3 AU. Declining phase. Best quadrant for context from Earth. Good telemetry. Other 3 possibilities. Polar coronal holes: multiple opportunities

25 SAP Planning Strategy / Concatenated RSW Objectives that need longer periods of continuous RS observations, typically in some sort of synoptic mode. 3 orbits are good candidates for a 20 days window + 4 days extension. For 5 other orbits we can have quasi-continuous RS observations from pole to pole (one from -21º to +21º, one from -31º to +31º and perihelion at 0.3AU).

26 SAP Planning Strategy / Low TM perihelia There are SOOPs that only need medium-low TM downlink. All these can be scheduled at outbound perihelia. 6 possibilities.

27 SAP Planning Strategy / Polar objectives There are 2 windows for detailed pole analysis with very good TM. Not included in SAP v0 (pending Obj. 4 discussions).

28 SAP Planning Strategy / SPP collaboration All objectives that would benefit from joint observations with SPP have been identified. All these objectives have already been scheduled in the current version of SAP. To be optimised at a later stage of the SAP (after launch) when SPP and SolO final trajectories will be known.

29 SAP Planning Strategy / Special cases Some objectives do not fit in any of the above categories. Special care has been taken for them. They are described in the SOOP strategy page. Please review!

30 The MTP as a unit of scheduling We will build the plan in ~six-month blocks. We call each block or planning period an MTP (Medium Term Plan). Long-Term and Medium-Term planning both cover the same six month MTPs, one just happens before the other. Note that not all MTPs are the same as an orbit, so not all MTPs have 3 RSWs (In Option E, some MTPs have 5 or 6) We choose a six-month planning period rather than an orbit since these are synchronised to the ESTRACK planning schedule It s hard to make a detailed plan when you don t know how many comms passes to request (or you have). The MTPs for Option E are described on SOC Public (here). NMP starts at MTP 05, EMP starts at MTP 13.

31 MTP Properties Example 1: MTP 06 Each MTP Page has an orbit plot like this: (Also available under Orbit Plots on SOC Public)

32 MTP Properties Example 1: MTP 06 Each MTP Page has an orbit plot like this: (Also available under Orbit Plots on SOC Public) RSWs Spacecraft position at MTP start

33 MTP Properties Example 1: MTP 06 Each MTP Page has an orbit plot like this: (Also available under Orbit Plots on SOC Public) GAM +7 Days GAM 31 Days GAM Bad data rate Good data rate

34 MTP Properties Example 1: MTP 06 Each MTP Page has an orbit plot like this: (Also available under Orbit Plots on SOC Public) Conjunction Safe Mode Comms blackout (if we go into safe mode here we loose comms)

35 MTP Properties Example 1: MTP 06 Each MTP page also has a table with details of the default RSWs that fall in that period. Note RSWs never span MTPs we finish an MTP early instead. The RSW table for the whole mission is available on SOC Public under SAP Pages. We have to move the North Window in this MTP since it falls within a GAM restriction period. We ve been conservative with the definitions

36 MTP Properties Example 2: MTP 15 Not all MTPs are created equal! (This one will be fun to plan )

37 Assigning SOOPs to MTPs The SAP strategy page is supposed to be trajectoryindependent. We wrote it by examining the types of opportunities available in the Option E trajectory (the problem would have been too abstract otherwise). So you ll see some reference to Option E MTPs there they re only examples. If the trajectory changes this page will stay the same. The actual SOOPs we think are suitable for each MTP are kept on the MTP pages. These will change with the trajectory If you disagree, please comment on the strategy page, unless you think an MTP is inconsistent with the strategy

38 Example - MTP 06 We start far from Earth with a low data rate, have to contend with a conjunction (which will make data return even worse), and have to move an RSW to avoid a GAM.

39 Example MTP 06 New proposal for RSwindow placement: We need to move RSW North to avoid the GAM We ve identified two options: 1. After the VGAM, to end 2021 or start 2022, i.e the very end of MTP06 or start MTP07. This option has extremely good TM but will be far from the Sun, e.g. ending around 0.8AU. 2. Between MTP06 south and perihelion windows. Depending on the science goal you may want to concatenate it to either of them, watch out for the poor data return and conjunction though! Trade off between data return and distance from the Sun (latitude not important this early in NMP). Kind of decision the SWT needs to make in the SAP.

40 Example - MTP 06 SOOP planning proposals I_DEFAULT outside of RSWs, L_IS_STIX on inside all RSWs RSW South: Magnetic field synoptics to construct Carrington maps including Earth data and SolO data: L_FULL_HRES_LCAD_MagnFieldConfig RSW Peri: Short period (~30mins) of: R_SMALL_HRES_HCAD_Rsburst Additionally, the South and Perihelion window can also be merged together and serve to address slow SW connection science goals: L_BOTH_MRES_MCAD_Farside_Connection L_SMALL_MRES_MCAD_Connection_Mosaic MTP06-North: to be started asap after GAM, i.e. 30 Nov 2021 running until 9 Dec 2021 (implies NO precursors). Solar distance range of 0.77AU to 0.82AU. To be decided by SWT whether this is worth pursuing (Too far out for SoloHI and Metis?).

41 Example MTP 06 Current model (SAP v0): RS windows at default locations MTP06_South: L_FULL_HRES_LCAD_MagnFieldConfig throughout RSW MTP06_Peri: L_BOTH_MRES_MCAD_Farside_Connection for 9 days & 30 mins R_SMALL_HRES_HCAD_RSburst at end of window MTP06_North: L_SMALL_MRES_MCAD_Connection_Mosaic (3hrs / day) combined with L_SMALL_HRES_HCAD_Fast_Wind I_DEFAULT outside of RSWs, L_IS_STIX on inside all RSWs For those MTPs where there are many possible SOOPs, we ve chosen something we think will work. We ve made sure all the SOOPs we re confident are already meaningful have been scheduled at least once during the NMP. This is the strawman v0 SAP we ve simulated to check the feasibility of the mission and develop our tools. Of course, this plan will change with your input!

42 How to build a mission-long SAP? SolO s (sub)objectives SOOPs 10 instruments, many modes Step 1 SOOP A SOOP B SOOP C EPD normal+burst EUI/HRI AR mode MAG Normal Metis GLOBAL PHI/HRT NOM 0 RPW normal+burst SOOP D Step 2 Strategy 10 years mission timeline B A A A D To be checked against mission constraints Step 3 Simulation

43 Step 3 SIMULATE EXAMPLE VERSION OF THE PLAN: SAP V0

44 Simulation of SAP v0 We chose one possible version of each MTP plan to construct what we call SAP v0 For each 6-month period, we chose one possible combination of SOOPs from the several options listed in the SAP pages. -> see bottom of each MTP page for the choices made SAP v0 is restricted to NMP only though MTP pages 5-21 contain suggested SOOPs for the whole mission duration No attempts made to fill all RS windows (only Obj 1-3 for now) We tried to schedule each SOOP at least once. Few exceptions that need higher latitude and thus EMP. It is clear that 1 SOOP instance will not necessarily fullfill all goals of that SOOP.

45 Simulation of SAP v0 This timeline of SOOPs, and associated instrument observations are modelled through the SOC planning software: Main mission timeline ( SAP timeline ) includes SOOP timelines SOOP timelines call observations for each of the participating instruments Instrument observations are (high-level) science campaigns, modelled with average power and datarate

46 Simulation of SAP v0 SolO s (sub)objectives SOOPs SOOP A SOOP_A.itl SOOP B SOOP_B.itl SOOP C SOOP_C.itl SOOP D SOOP_D.itl EPD normal+burst EUI/HRI AR mode MAG Normal Metis GLOBAL PHI/HRT NOM 0 RPW normal+burst calls calls 10 instruments, many modes EPD_observations.def EUI_observations.def MAG_observations.de METIS_observations.de + avg power + avg datarate 10 years mission timeline B A A A D SAP_OptionE.itl To be checked against mission constraints

47 Simulation Results General Overview SOUS-CHEF output: -- RS windows -- Orbital events -- MTP-periods -- SOOPs -- EPD -- EUI -- MAG -- Metis -- PHI -- RPW -- SoloHI -- SPICE -- STIX -- SWA

48 Simulation Results General Overview SOUS-CHEF output: 6-months period MTP7 -- RS windows -- Orbital events -- MTP-periods -- SOOPs -- EPD -- EUI -- MAG -- Metis -- PHI -- RPW -- SoloHI -- SPICE -- STIX -- SWA

49 Simulation Results General Overview SOUS-CHEF output: 1 Rswindow (partially filled) -- RS windows -- Orbital events -- MTP-periods -- SOOPs -- EPD -- EUI -- MAG -- Metis -- PHI -- RPW -- SoloHI -- SPICE -- STIX -- SWA

50 Simulation Results SSMM fill state Output planning software (EPS) for this partially filled plan:

51 Simulation Results Remote Sensing Stores Output planning software (EPS) for this partially filled plan:

52 Simulation Results In Situ Stores Output planning software (EPS) for this partially filled plan:

53 Simulation Results Power I

54 Simulation Results Power II

55 Simulation Results Conclusions With the current, partially filled plan, based on still preliminary information, we did not encounter any overruns and average power seems under control. So far so good!

56 4 CAVEATS: HOW TO (NOT) INTERPRET THIS PLAN

57 Caveats: how to (not) interpret this simulation I SAP v0 is not worth that much as a science plan yet! It still has many holes, may be oversimplified and is based on some unconfirmed assumptions It allows us (SOC) to build tools to support Mission Level Planning (and LTP) and to develop and test out optimisation strategies SOC is trying out this concept and presents SAP v0 to the SWT as a starting point for SAP v1.

58 Caveats: how to (not) interpret this simulation II Still, SAP v0 is driven by scientific planning reasoning, so it should not be completely ridiculous. BUT: This plan is very trajectory dependent. It has been built on Option E trajectory (Launch 30 sep 18) It is a very high-level plan, as required for MLP, but more details may be needed: SOOP durations typically modelled as n days No calibration campaigns or engineering activities RS windows are still at their default location, while some will need shifting (see suggestions on SAP pages) Instrument observations typically used with default (avg) data rates More important: Planning strategy is important to review: do you think this can work?

59 5 SAP OPTIMISATION OPTIONS

60 SAP Optimisation Options I SAP shall be a feasible operations plan, covering whole mission. Still, it may be revisited few times, mainly driven by failures. Mission Level Planning, i.e. SAP optimisation, continues from now to end of EMP. Optimisation options depend on where you are in the mission timeline: NOW - Pre-launch Mission Level Planning (MLP): High flexibility: Move around RSW Add extra communications passes (extra 19 passes/orbit not yet included in current simulation) Reschedule SOOPs and Adjust SOOP durations Tweak observation parameters Model TM Downlink Ratios (TDR): vary each instrument s allocation of downlink

61 SAP optimisation options: planning timeline ESTRACK 1 FECS 1 NMP MTP 1 TO MOC ESTRACK 2 ESTRACK 3 ESTRACK 4 CP 1 2 SOWG - LTP 1 SWT - MISSION LEVEL 2-n SOWG - MTP 1 SOWG - LTP 2 SWT - MISSION LEVEL 3-n SOWG - MTP SOWG - LTP 3 SWT - MISSION LEVEL 4-n + AS RUN 1 SOWG - MTP 3 SOWG - LTP 4 SWT - MISSION LEVEL 5-n + AS RUN 2 SOWG - MTP SOWG - LTP 5 FECS 2 MTP 2 TO MOC FECS 3 MTP 3 TO MOC FECS 4 MTP 4 TO MOC ESTRACK 5 FECS 5 3

62 SAP Optimisation Options II SWT meetings MLP during Cruise, NMP & EMP: These happen every 6 months, in Sep and Mar. This meeting will address: Preliminary evaluation LTP/MTP period that ended 3 months ago: Based on LL data: which campaigns achieved/failed?, lessons learned? Check SSMM fill state at end of period (-> model). No tweaking of LTP/MTP period starting in 3 months: LTP planning for this period already took place, IORs are being written Reduced flexibility for LTP/MTP period starting in 9 months: Move around Freeze RSW location now Add extra passes subject to the overall budget Reschedule Tweak planned SOOPs and Adjust SOOP durations Tweak observation parameters Tweak instrument TM allocations

63 SAP Optimisation Options II SWT meetings MLP during Cruise, NMP & EMP: These happen every 6 months, in Sep and Mar. Preliminary evaluation LTP/MTP period that ended 3 months ago: Based on LL data: which campaigns achieved/failed?, lessons learned? Check SSMM fill state at end of period (-> model). No tweaking of LTP/MTP period starting in 3 months: LTP planning for this period already took place, IORs are being written Reduced flexibility for LTP/MTP period starting in 9 months: Move around Freeze RSW location now Add extra passes subject to the overall budget Reschedule Tweak planned SOOPs and Adjust SOOP durations Tweak observation parameters Tweak instrument TM allocations Still available at upcoming LTP

64 SAP Optimisation Options II SWT meetings MLP during Cruise, NMP & EMP: These happen every 6 months, in Sep and Mar. Preliminary evaluation LTP/MTP period that ended 3 months ago: Based on LL data: which campaigns achieved/failed?, lessons learned? Check SSMM fill state at end of period (-> model). No tweaking of LTP/MTP period starting in 3 months: LTP planning for this period already took place, IORs are being written Reduced flexibility for LTP/MTP period starting in 9 months: Move around Freeze RSW location now Add extra passes subject to the overall budget Reschedule Tweak planned SOOPs and Adjust SOOP durations Tweak observation parameters Tweak instrument TM allocations Only option left from MTP onwards

65 6 WHAT NOW?

66 WHAT NOW? Please provide feedback on the SAP v0 and, most importantly, on the Planning strategy page the SOOP pages: we need 1 SOOP coordinator per SOOP to moderate the commenting process Use your accounts to add inline comments (by 21 Oct). SAP #4 meeting: October at MPS, Göttingen. January 2017: Full version including Obj. 4 released. SOWG (24-25 Jan): Planning exercise using SAP (IS E2E Test). April 2017: SAP v1 presented at SWT for signature.

67 Which parts do we want you to review? SolO s (sub)objectives SOOPs 10 instruments, many modes Step 1 SOOP A SOOP B SOOP C EPD normal+burst EUI/HRI AR mode MAG Normal Metis GLOBAL PHI/HRT NOM 0 RPW normal+burst SOOP D Step 2 Strategy 10 years mission timeline B A A A D To be checked against mission constraints Step 3 Simulation