imap_processing.spice.repoint.get_repoint_data#
- imap_processing.spice.repoint.get_repoint_data() DataFrame#
Read repointing file from the configured location and return as dataframe.
Pointing and repointing nomenclature can be confusing. In this case, repoint is taken to mean a repoint maneuver. Thus, repoint_start and repoint_end are the times that bound when the spacecraft is performing a repointing maneuver. This is different from a pointing which is the time between repointing maneuvers.
The repoint table location is stored in the global variable _repoint_table_path in the imap_processing.spice.config module.
- Returns:
repoint_df – The repointing csv loaded into a pandas dataframe. The dataframe will contain the following columns:
repoint_start_sec_sclk: Starting MET seconds of repoint maneuver.
repoint_start_subsec_sclk: Starting MET microseconds of repoint maneuver.
repoint_start_met: Floating point MET of repoint maneuver start time. Derived from repoint_start_sec_sclk and repoint_start_subsec_sclk.
repoint_start_utc: UTC time of repoint maneuver start time.
repoint_end_sec_sclk: Ending MET seconds of repoint maneuver.
repoint_end_subsec_sclk: Ending MET microseconds of repoint maneuver.
repoint_end_met: Floating point MET of repoint maneuver end time. Derived from repoint_end_sec_sclk and repoint_end_subsec_sclk.
repoint_end_utc: UTC time of repoint maneuver end time.
repoint_id: Unique ID number of each repoint maneuver.
- Return type:
- Raises:
ValueError – If no path to a repoint-table has been set.