Backup launch date (oct. 2020) - conflict in KSC (Florida) and possibly in Vandamberg site (california) - Still in discussion
SOLO budget now 60% increased from adoption
RPW PY ANT HS and MLI hinge damaged by ADS - have to be changed. Third instrument after delivery (EUI, SIS, RPW) —> PIs are writing a letter to Cesar Garcia, Gunter Hasinger (ESA DS), Thomas Zurbuchen (NASA) to alert —> Meeting with Hasinger is requested during SOWG (Jan will go, Milan is not sure yet)
Sylvain Lodiot discussion about deployment (see next item below)
2.
Deployment operations (Milan, all):
New scenario of deplyments: ANT1—>IBOOM—>ANT2—>ANT3. Done in a single extended operation.
MOC wants no interaction with RPW team during the operations —> just run sequences timeline from the RPW team instructions (which have to be detailed in the RPW UM), even in case of failure (FDIR).
It is not a problem to run several config during depployment ops (in a predefined manner)
RPW-8 operation: RPW will request to be ON all the time during the NECP. RPW resource allocation could be problematic. Not communicated by MOC yet.
ROC: prepare timeline for this new scenario for the next ROB telecon
3.
Low rate configurations (Jan)
A proposal of Low rate configurations for commissioning sent by Jan before telecon (attached).
no objection received before telecon
THR mode note detailed, but THR normal config. with 50% less rate used (increasing integration time —> spec every 24 sec instead of 12 sec.). THR team approved - same for lowrate1 and 2
No objection received before teleconand proposal seems ok to all
Snapshot cadence should be coordinated with SWA and other instruments. To be discussed at SOWG / ISWG in January.
Jan: send a doodle poll for the next ROB telecon.
4.
BIAS sweeping tables:
Discussion of updating BIAS sweeping tables in flight.
Andris needs to ask how to retrieve the default Bias sweeping table value.
Andris: provide BIAS tables to Antonio/Xavier
Xavier: Plan a separate telecon to clarify Bias operation (possibility vs sequence)
5.
Science data validation procedures (Milan):
Two validation activities:
ROC pipeline validation (before launch, during comissioning)
Science data quality validation (continuous activity during operations):
Each team should validate their own part, but roles need to be assigned.
Validation plan should be defined for the next consortium meeting at Kiruna
Output of validation: quality flags
Action XB - prepare a first proposal for data validation workflow (deadline 21/12/2018 to sent it to ROB members)
Xavier: prepare a first proposal for data validation workflow (deadline 21/12/2018 to sent it to ROB members)
Xavier: send an email to the MADAWG about quality flag definition
6.
Next telecon: January 11, 2019 14:00 CET
7.
Commissioning:
What data is needed to validate the performance ? L2 data ? Success criteria for successful commisioning closure.
To be defined in preparation of the next consortium meeting (if possible). Lead by CNES (Eric L.).