Because of intial reduced telemetry, an onboard algorithm for detecting IP shocks and retrieve their high cadency data has been developed by the RPW team (see instrument paper, DETECTION mode is described in section 4.2.2 and technical note for details about algorithm triggering). This algorithm uses internal, non fully calibrated MAG, SWA & RPW data. When those are not available, false detection may occur. This pages summarizes the type of events which have been detected by RPW and for which we might have 13-min of high cadence and high quality RPW data.

Table shows :

• centered time of the supposed shock. Data have been acquired 13min around this time.
• possible event type : This classification is done manually by Olga Alexandrova and might contain errors.
  — Fast shocks : correlated magnetic field and density discontinuities
  — Slow shocks : anticorrelated magnetic field and density discontinuities
  — Pressure balance event : anticorrelated magnetic field and density without discontinuity and no velocity jump.
  — Others : no clear classification
  — Unidentified : not yet classified by RPW team
• status of high cadency data retrieval :
  — "Yes" : more than 80% of high cadency RPW data have been retrieved,
  — "Partially" : less than 80%of high cadency RPW data have been retrieved,
  — "No" : no high telemetry data have been downloaded on ground (due to telemetry constraints) but regular data are available;
• summary plot link displaying parameters used onboard in automatic detection algorithm such as magnetic field from MAG, proton density and velocity from SWA. Those plots show the uncalibrated data used by RPW onboard to trigger.

If you see any mistake, please let Olga Alexandrova knows.

High cadency data might have been retrieved on ground (if available, see column "Retrieved") and will be available on Solar Orbiter Archive.
Regular data are always available during all this events evenso high cadency data are not. See also MAG and SWA data for multi-instrument study.

Export in csv is possible for all the events (no classification can be made before export). The export takes 1-2 minutes.