Data Store

General structure

The MOS-GFINDER Data Store is a file-based system composed of two identical-structure but distinct directories, which together contain both input “definitions” and output “opportunity” data.

• The application data directory (gfinder-data) contains the definitions data required for GFINDER to work with the JUICE mission and MAJIS instrument. In a multi-user environment (MOS JupyterHub), these data are shared across all users, in read-only access.

• The user data directory (data) contains opportunity data generated by the user. Optionally, it can contain user’s definitions data, which have precedence over application definitions data (only tested for opportunity definitions at the moment).

odf/

Directory containing all opportunity definition (ODF) files.

opportunities/

Directory containing opportunity data generated using GFINDER.

rois/

Directory containing the definitions of target surface region-of-interests (ROIs).

scenarios/

Directory containing mission scenarios (SPICE metakernels paths), and associated mission events.

Note

GFINDER application data are provided in a separate gfinder-data GitLab repository.

Opportunity Definitions (ODF)

Located in the odf/ directory of the application data directory, Opportunity Definition File (ODF) files are organised using the following structure:

The root directory contains the Observation Type ODF files ( or “observation opportunity definition files”), which are indexed in the Observation Types Index File, named observation_types.json file. Naming convention: [jsoc_observation_mnemonic].json.

common/

Directory containing common geometry and geometrical conditions definitions, which can be included in other observation opportunity definitions file. Naming convention, for example:

detector_geometry.json
majis_hr_conditions.json
majis_jup_disk_conditions.json
majis_sat_disk_conditions.json
majis_limb_conditions.json
sc_orientation_angles.json
subsc_point_geometry.json
target_disk_geometry.json

pointing/

Directory containing pointing geometry definitions, which can be included in other observation definitions file. Naming convention, for example:

juice_target_limb_scan.json
juice_target_limb_slew.json
juice_target_noa_mc.json
juice_target_npb_mc.json
juice_target_npo_scan.json
juice_target_npo_slew.json

deprecated/

Directory containing definitions that are ignored by GFINDER.

Note

In a multi-user environment, users can write and organise their own ODF files in the data/odf the way they want. They can write observation opportunity definitions (master ODFs) superseding existing ones, indexed in the gfinder-data/odf/observation_types.json file. However, they can’t write new ones. That is for keeping control and alignment with observation definitions defined within the JUICE SOC planning system.

Opportunities

Opportunity Directory

Opportunity File

Sequence GeoEvt File

Observation GeoEvt File(s)

Observation GeoJSON File(s)

Quaternion CSV File

Opportunity Definition File

Regions Of Interest (ROI)

Missions Scenarios

Missions Scenarios Index

mission_scenarios.json

Event files

Naming convention, eg: juice_crema_5_0_ops.csv