https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-1160 Instrument control development <p>The stabilityTests.sh, etc. scripts are currently in ics_iicActor, and need to be moved to a more dynamic repository, the new <tt>pfs_obs_scripts</tt>.</p> <p>I will check that out into <tt>/software/devel/pfs/pfs_obs_scripts</tt> and populate it there.</p> <p>Will also point the crontab to call the relocated scripts, maybe with some <tt>/software/ics_launch/run_obs_script</tt> bouncer.</p> INSTRM-1160

Move existing cron-called scripts to pfs_obs_scripts/bin

Task Normal Done Done cloomis cloomis SPS Thu, 14 Jan 2021 20:34:48 +0000 Fri, 14 Jan 2022 20:42:06 +0000 Mon, 1 Feb 2021 23:18:14 +0000 ics_iicActor 0 1 <p>One top-level script: <tt>callOpsScript.sh scriptName <span class="error">&#91;args&#93;</span></tt>, which simply calls <tt>scriptName args</tt> with output redirected to <tt>/data/logs/scripts/$scriptName/YYYY-MM-DD.log</tt>. </p> <p>Moved stabilityTest.sh over from ics_iicActor; added possible masterDarks.sh. Both untested because of whatever acquisition is happening now.</p> <p>Checked out to <tt>/software/devel/pfs/pfs_ops_scripts/</tt> and <tt>eups declare --current</tt> there. I made tags for code changes, but none really needed for script additions and changes: each call is prepended by a <tt>git describe</tt> to the log.</p> <p>crontab lines are a bit clumsy due to the length of the path; we might want to add some sugar, or bounce through a <tt>/software/ics_launch/bin</tt> script to do the setup and call:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>#1 2-23 * * * /software/devel/pfs/pfs_ops_scripts/bin/callOpsScript.sh stabilityTest.sh #1 0 * * * /software/devel/pfs/pfs_ops_scripts/bin/callOpsScript.sh masterDarks.sh </pre> </div></div> <p>Oh, the package is <tt>pfs_ops_scripts</tt>, not <tt>pfs_obs_scripts</tt>.</p> <p>This was a new repo for this, so I thoughtlessly put the work on master.</p> <p>The ops scripts themselves are in the <tt>scripts/</tt> directory, and should be called via the <tt>bin/callOpsScript.sh</tt> wrapper. See the last comment, or the pfs crontab.</p> Development Rank 0|02qppq:c