Skip to content

plot-obs-timelines

plot-obs-timelines.sh: Wrapper script, makes plots of observations from a DRM

Usage:

  plot-obs-timelines.sh [-o TEMPLATE] [-j JSON] DRM

where:

 -o TEMPLATE  gives the explicit output file template
              must contain two %s's, such as timelines-%s.%s
              By default, this is deduced from Sandbox conventions
 -j JSON      gives the JSON script name
              By default, this is deduced from Sandbox conventions
 -D           signals to run python with the debugger on

This is a wrapper around (currently) two python plotter-scripts: plot-timeline.py plot-star-obs-trace.py The above scripts make per-run plots (one-plot-per-drm). Such plots are somewhat analogous to the movies, and to the keepout plots. But both of those take more time to run, so they are broken out separately.

The reason for wrapping these is to make a one-call interface for the Makefile to use (make obs-timeline is the target). Because we create more than one output file, a sentinel text file is created by this script upon successful exit, signaling that all files were made OK.

The star-planet config file (SPC) corresponding to a DRM is also needed, as is the JSON script. By default, these filenames are generated from the DRM filename (see "Conventions" below), but they can also be supplied.

Conventions: The SPC file will be deduced from the DRM filename by the called routines (not by this script). The script file (.json) is deduced from the DRM filename (directory component), but can be supplied explicitly with -j The image output name is generated from the DRM, but can be explicitly given. E.g.: drm = sims/HabEx_4m_TS_dmag26p0_20180206/drm/777.pkl spc = sims/HabEx_4m_TS_dmag26p0_20180206/spc/777.spc json = Scripts/HabEx_4m_TS_dmag26p0_20180206.json

turmon jul 2023