Changes between Version 28 and Version 29 of PublicPages/MayallZbandLegacy/NotesforObservers/MosBot
- Timestamp:
- Feb 7, 2017 1:02:39 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicPages/MayallZbandLegacy/NotesforObservers/MosBot
v28 v29 20 20 the mayall-2 display. You don't need to read any of the output it 21 21 produces, but you should check periodically that it is still running; 22 the code is under development and some bugs remain. If mosbot crashes, 22 the code is under development and some bugs remain. 23 24 If mosbot crashes, 23 25 please report it! If you can copy-and-paste the last page or two of log output, or at 24 26 the very least note the exposure number when the crash occurred, this will make … … 39 41 * when a new image appears: 40 42 * measures sky, seeing, and transparency from the image 41 * decides which pass number to observe in the upcoming exposures 43 * decides which pass number to observe in the upcoming exposures (by looking for 'forcepass*' files, or based on conditions) 42 44 * computes exposure times for the upcoming exposures 43 45 * overwrites the mini scripts for these upcoming exposures … … 69 71 == During the night == 70 72 71 === To Restrict to Pass 2 and/or 3===73 === Use The Force === 72 74 73 If, say, the weather has worsened and is highly variable, then you can force Mosbot to always choose a given 74 pass for upcoming exposures by creating files: 75 By default, Mosbot will choose which pass to do (ie, which of the three plan files to select tiles from) based on the conditions. However, this can result in long slews as it switches between passes. Therefore, observers are encouraged to *use the force* -- to tell the Mosbot which pass it should be doing. 76 77 Do this by creating a file in the directory `~/exec/mosbot`. Files are checked in this order: 78 79 * `~/exec/mosbot/forcepass1` -- tiles from the first JSON file (pass1.json) will be scheduled 80 * `~/exec/mosbot/forcepass2` -- tiles from the second JSON file (pass2.json) will be scheduled 81 * `~/exec/mosbot/forcepass3` -- tiles from the third JSON file (pass3.json) will be scheduled 82 * `~/exec/mosbot/nopass1` -- tiles from the second or third JSON files will be selected, based on conditions. 83 84 These files can be created using the `touch` command: 75 85 {{{ 76 86 touch ~/exec/mosbot/forcepass2 77 87 }}} 78 or 79 {{{ 80 touch ~/exec/mosbot/forcepass3 81 }}} 88 and be sure to `rm` the other `forcepass` files! 82 89 83 OR, if you want to forbid pass 1, but allow Mosbot to choose between pass 2 or 3, you can create the file: 84 {{{ 85 touch ~/exec/mosbot/nopass1 86 }}} 90 NOTE that Mosbot will *delete* the `forcepass?` and `nopass1` files every time it is started up, so if you have to restart it, be sure to re-create the `forcepass` file for your chosen pass! 87 91 88 These files are NOT deleted by the `tonight.sh` script or by Mosbot,89 and will remain in effect until you delete them!90 92 91 93 Note that it is Mosbot that pays attention to these files (not