First RPW switchingswitch-on and in-flight SFT (RPW-0)
A first "RPW-0" operation shall be planned at least 24h prior to the iBoom and ANT deployements.
This operation shall consist of switching-on the instrument and perform a in-flight SFT-like testto check the instrument behavior, in order to perform a first verification and ensure that the instrument is ready for the iBoom and ANT deployment operations.
The instrument timeline/configurations have to be detailedTBD from the CNES inputs
Jira
server
jira-lesia.obspm.fr JIRA
serverId
cb08a004-0694-3237-bcb1-3125e3ed9bc0
key
ROCOPE-162
. It should be similar to the SFT timeline (see As-run #3.doc for a SFT run).
The , but the operation should take around 1h20 1h30 max. (typical duration of a SFT test) and should be planned at least 24h before the beginning of the deployement operations (to let the time to the RPW team to analyze and validate the TM before deploy. ops.)
It might be required to follow the operation step-by-step, instead of doing it in one shot.
As a reminder, the iBoom and ANT depl. are planned during the LEOP phase (the 7 days after launch). IT MUST BE DISCUSSED WITH MOC IF THIS OPERATION CAN BE PLANNED PRIOR TO THE DEPLOY. OPS.
XB highlighted that the MAG team might ask to MOC for performing the same kind of operations before i-boom deployment. It may be useful to coordinate with MAG on this.
The first switch-on and SFT operation shall be added to the RPW_NECP.xlsx to be discussed with ESA at SOWG12
iBoom deployment (RPW-1)
RPW shall be switched-on/off 10 min. before/after the beginning of the deployment
A single instrument configuration might be enough to cover the needs.
A specific "iboom dep.deployment" configarutions should be enough to cover the needs. hence defined.
In all cases, we should minimize the number of TC to execute during the operation (i.e, number of config.)
No big issue highlighted for now with this operation
ANT deployment (RPW-2)
The details about how the RPW ANT will be deployed in-flight are still in discussion between RPW and ESA
RPW shall be switched-on/off 10 min. before/after the beginning of the deployments.
A single instrument configuration might be enough to cover the needs
A specific "ANT dep.deployment" configarutions should be enough to cover the needshence defined. Additionaly to spectral data, measuring waveforms at 256Hz should be envisaged.
In all cases, we should minimize the number of TC to execute during the operation (i.e, number of config.)
ANT calibration rolls
The ANT cal. rolls shall can only be planned in the first week of the NECP phase or and just after the EGAM (see slide 24 of the SOWG11_MLP_All.pdf presentation at SOWG11 ; available on the SOC Wiki public page)
RPW team will request MOC to perform this operation in both cases NECP NECP and EGAM.
The ANT roll should take 8h (min. 6h) per day and should be repeated at least 4 days (TBC) to increase the change of observing AKR
RPW team shall verify that the NECP first week and EGAM S/C configuration versus AKR visibility is exploitable to perform the effective ANT calibration. Action for Milan: see with Patchenko if he can provide information to conclude on this (i..e, AKR visibility, required S/C orbitography for ANT roll).
A specific "DF modeDirection-Finding" configuration will be used during ANT roll with the highest possible spectral resolution on TNR.
Ask for EMC quiet mode in S/C
The ANT cal. rolls operation shall be added to the RPW_NECP.xlsx to be discussed with ESA at SOWG12
SCM calibration operation
Specific measurements shall be done in the Earth mag. lobe to define SCM noise.
This has also to be done during the first week of NECP and EGAM. Xavier XB will check with Olga Alexandrova when exactly the S/C passes through the Earth lobe.
A priori, no operational constraint at S/C level, such as attitude change, is required
The only request is that RPW is ON in a specific "SCM cal. configuration" and EMC quiet mode is applied (TBC), when passing through the lobe. It has to be discussed with MOC.
A priori, no operational constraint such as attitude change is required
The SCM cal. operation shall be added to the RPW_NECP.xlsx to be discussed with ESA at SOWG12
In-flight inter-instrument interference campaign
EL has indicated that the EMC interference campaign on-ground should give a good baseline to prepare the in-flight interference campaign
XB asked about the possiblity of testing in-flight the SWA-6kV voltage risk for RPW (see also https://jira-lesia.obspm.fr/browse/ROCOPE-112) during this campaign? EL needs to discuss with SWA team (Fedorov) about this.
Input needs for this campaign will be provided by RPW CNES team
Timeline shall be discussed between ESA and IT.
1.RPW PAS filtering tune campaign
XB asked if this campaign should be a part of the in-flight inter-instrument interference campaign? For now, it has been decided to let these two campaigns separated.
Coordination with the SWA team is required. To be done by EL.
2.
EL has confirmed that the CNES is responsible of the RPW commissioning, until the end of the NECP.
New issue of the RPW_NECP.xlsx, updated by RPW team, shall be sent before to MOC (Jose-Luis Pellon-Bailon)
XB will start to modify and submit before the end of the week (i.e. ) a new version "RPW_NECP_V2.xlsx" to the RPW operations working group
RPW UM will be firstly updated by JMT and EL to include antenna inputs. A second update should be planned, if possible before the next SOWG12 on July 2018, in order to incude last inputs for RPW commissioning.
Moreover, a first rough estimation of the power consumption (in W) and data volume for each of the RPW commissioning activity (RPW-i) listed in "RPW_NECP_V2.xslx" file shall be given before the next SOWG12.
In all cases, it is important that the RPW team has enough information to argue during the