View observation definition

This is a multi-purpose mode that can be used on any science target for any 2D mapping, and meridional or zonal rasters. This mode will also be used for calibration purposes (e.g. pointing). The number of rows and columns and the stepsize of the raster map is adaptable to the target angular size. Jupiter: Investigation of the global and regional stratospheric composition and temperature of Jupiter, and pointing calibration. For 2D maps, meridional scans and zonal scans, two CTS spectra are recorded every 60 seconds over 10000 channels (16 bits coding). Moon monitoring: Investigation of the spatial distribution of Galilean moons atmospheric species (+ monitoring), and calibration. Two CTS spectra are recorded every 60 seconds over 210 channels (16 bits coding). Flybys: Mapping of Galilean Moons’ surface properties and atmospheric composition, temperature, and winds. Two CTS spectra are recorded every 30 seconds over 210 channels (16 bits coding).




Jupiter: Scheduling: d1–d3 for pointing calibration and global maps, d1/d2 for meridional scan, d1 for zonal scan. Repetition: TBD. Moon monitoring: when Galilean moons are well-resolved (angular diameter >2mrad). Flyby: This mode will be continuously used during phase IV, and phases I and III of the flybys between 12hrs and 6hrs from CA. GCO-500: this mode will be used in configuration (1) continuously for 5 orbits (i.e. 16-hrs) and then cycled equally with SWI_MOON_LIMB_SCAN_PS, SWI_MOON_LIMB_STARE_PS, and SWI_MOON_NADIR_STARE_PS. Scheduling and repetition of configuration (2) is still TBD.
any rule that is used to schedule the observation: repetition rules, continuous (plasma instruments), one-off, every orbit, every day, etc
conditions that make the observation not possible (e.g. thruster firing)