Changes between Version 28 and Version 29 of HetProcedures/RA/ocd
- Timestamp:
- Nov 26, 2019 4:43:37 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HetProcedures/RA/ocd
v28 v29 17 17 * If you want to save a log for engineering purposes try the following: 18 18 {{{ocd run --config ~/ocd/ocd.cfg |& tee logs/OCDlog_YYYYMMDD_X.txt}}} where the X is the test number; note that this produces a pretty big log so keeping to a single track is probably a good idea and gzipping it before e-mailling it is also a good idea. 19 20 == Starting OCD === 21 19 22 * Then to allow OCD to select hetdex fields you need to execute {{{ ocd allow_hetdex --config ~/ocd/ocd.cfg start }}} 20 23 * To check last selected by OCD target use command in ocd subdirectory … … 22 25 * To see what autoschedule is planning, use command in ocd subdirectory 23 26 {{{ tail -f logs/OCDlog_YYYYMMDD_X.txt | grep Autoschedule }}} 24 * To stop auto hetdex fields running run {{{ ocd allow_hetdex --config ~/ocd/ocd.cfg stop }}}25 27 26 == Running a shot == 28 == Stopping OCD === 29 30 * To stop OCD from choosing any additioal fields run {{{ ocd allow_hetdex --config ~/ocd/ocd.cfg stop }}} 31 * Note that this does not affect the current shot in progress. 32 33 == Aborting OCD === 34 * To abort the current shot *and* stop OCD from choosing any additioal fields run {{{ ocd allow_hetdex --config ~/ocd/ocd.cfg abort }}} 35 * This (should) completely and quickly stop OCD more gracefully (needs to be tested) 36 * OCD will still be running after an "abort", and you can "start" it again if needed. 37 38 39 40 41 == Running a shot manually == 27 42 28 43 … … 36 51 where the 0 is the Az indicator (E=0,W=1), 15 15 15 is the exposure time for exp01, exp02, exp03 and 1001 will be the observation number. 37 52 38 == Running autoschedule ==53 == Running autoschedule manually == 39 54 40 55 Looks at the shot list and for a given JD tries to pick all targets that should be observed after that JD for that night.