Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Discuss about the RPW_NECP.xlsx (see attached items below) file content to be delivered to MOC before  

...

Attendees


  • Xavier Bonnin@@mentionnez une personne pour l'ajouter en tant que participant et elle sera notifiée


Agenda

  1. Content of the RPW_NECP.xlsx
  2. Action-items and planning
  3. Next operation telecon
  4. AOB

...

TimeItemWhoNotes
  1. First RPW switching-on (RPW-0)
  • A first "RPW-0" operation shall be planned prior to the iBoom and ANT deployements.
  • This operation shall consist of switching-on the instrument and perform a SFT-like test to check the instrument behavior.
Details
  • The instrument timeline/configurations have to be
defined
  • detailed
    Jira
    serverjira-lesia.obspm.fr JIRA
    serverIdcb08a004-0694-3237-bcb1-3125e3ed9bc0
    keyROCOPE-162
    , but the operation should take around 1h20 (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
first switching-on)
  • TM before deploy. ops.)
  • It might be required to follow the operation step-by-step, instead of doing it in one shot.
  • As a
remider
  • 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.

  1. iBoom deployment (RPW-1)

  • RPW shall be switched-on/off 10 min. before/after the beginning of the deployment
  • A specific "iboom dep." configarutions should be enough to cover the needs.
  • 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

  1. 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 specific "ANT dep." configarutions should be enough to cover the needs.
  • In all cases, we should minimize the number of TC to execute during the operation (i.e, number of config.)

  1. ANT calibration rolls

  • The ANT cal. rolls shall be planned in the first week of the NECP phase or 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  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 mode" will be used during ANT roll with the highest 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

  1. 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 will check with Olga when exactly the S/C passes through the Earth lobe.
  • The only request is that RPW is ON 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

Action items

  •  

Attached items