check_chip_drops
¶
The check_chip_drops
script takes an OR list and checks all of the
obsids in it for potential chip-drop configurations, and reports if any
SIMODEs do not exist.
Setup SACGS:
> newgrp acisops
> setsacgs
**************************************
*** Welcome to the CXC Data System ***
**************************************
CIAO configuration is complete...
10.10 Thursday, June 03, 2021
bindir : /home/ascds/DS.release/bin
CALDB : 4.9.5
setting production environment for Mission Planning...
setting production environment for Proposal applications....
CXC Data System, version: 10.10 Thursday, June 03, 2021
Set up a directory to do your work in.
> cd SACGS/
> set myroot = check_drops_oct0421
> mkdir $myroot
> cd $myroot
Just for convenience, here’s the usage message for check_chip_drops
:
> check_chip_drops --help
usage: check_chip_drops [-h] [--prelim] myroot theweek
Check existence of chip-drop SIMODEs for a particular OR list.
positional arguments:
myroot The root name for the files produced.
theweek The week of the OR list to check.
optional arguments:
-h, --help show this help message and exit
--prelim If set, this is a preliminary schedule.
--orfile ORFILE Supply the full path to an OR list file. If not set,
this script will search for one in the correct directory.
Now we can run the check_chip_drops
script. We provide it the prefix
$myroot
we decided above, and the name of the week we want to check
the drops for (if you want to check chip drops on a preliminary schedule,
supply the optional --prelim
argument). It will prompt for your arcops
username and password, provide you a list of files in the OR list
directory corresponding to the given week, and prompt you to tell it which
one to use (it will suggest the one it thinks you should use, and will
choose that one if you simply hit “Enter”. After this, it will do all of
the work and print the list of obsids and potential drops to stdout and
to disk.
> check_chip_drops $myroot OCT0421
SQL Server Username: jzuhone
Password:
OR lists in /data/mpcrit1/mplogs/2021/OCT0421/input:
OCT0421_00.or 2021-09-15 18:56:03.268541
OCT0421_01.or 2021-09-15 19:18:25.561799
OCT0421_pool.or 2021-09-15 19:24:21.606317
OCT0421_CAT.or 2021-09-15 19:25:20.763580
OCT0421_lp.or 2021-09-15 19:26:37.786611
Please type the name of the OR list file listed above that you want to check [OCT0421_01.or]: OCT0421_01.or
...
Obsids without optional chips:
Obsid Current SIMODE
----- --------------
23861 TE_00828
24350 TE_00866
24351 TE_00866
Chip-drop modes for obsids with 1 optional chip:
Obsid # Drops Current SIMODE Drop SIMODE
----- ------- -------------- ----------
23630 1 TE_005C6 TE_00D00
24261 1 TE_007F2 TE_004A6
24307 1 TE_006CC TE_00D16
24338 1 TE_0046C TE_00458
24430 1 TE_0064C TE_006E6
24479 1 TE_0088E TE_008D0
24489 1 TE_0064C TE_006E6
24746 1 TE_00458 TE_006E6
24928 1 TE_00458 TE_006E6
24929 1 TE_00458 TE_006E6
26126 1 TE_0046C TE_0064C
All chip-drop modes for obsids with 1 optional chip exist.
Chip-drop modes for obsids with 2 optional chips:
Obsid # Drops Current SIMODE Drop SIMODE
----- ------- -------------- ----------
23630 2 TE_005C6 TE_00914
24261 2 TE_007F2 TE_0065A
24307 2 TE_006CC TE_0057A
24338 2 TE_0046C TE_006E6
24430 2 TE_0064C TE_00D58
24479 2 TE_0088E TE_00958
26126 2 TE_0046C TE_006E6
All chip-drop modes for obsids with 2 optional chips exist.
Chip-drop modes for obsids with 3 optional chips:
Obsid # Drops Current SIMODE Drop SIMODE
----- ------- -------------- ----------
24307 3 TE_006CC TE_00914
24430 3 TE_0064C TE_00D54
All chip-drop modes for obsids with 3 optional chips exist.
Chip-drop modes for obsids with 4 optional chips:
Obsid # Drops Current SIMODE Drop SIMODE
----- ------- -------------- ----------
24430 4 TE_0064C TE_00D4E
All chip-drop modes for obsids with 4 optional chips exist.
Optionally, one can supply the full path to the OR list file on the command line if you know where it is:
> check_chip_drops $myroot OCT0421 --orfile=/data/mpcrit1/mplogs/2021/OCT0421/input/OCT0421_01.or
which would result in the same output for this case.
Note
The following error or warning messages may be seen, and are benign:
mkdir: cannot create directory ‘/home/jzuhone/SACGS/ckpoint’: File exists
make: [setup] Error 1 (ignored)
mkdir: cannot create directory ‘/home/jzuhone/SACGS/sch’: File exists
make: [setup] Error 1 (ignored)
mkdir: cannot create directory ‘/home/jzuhone/SACGS/idp’: File exists
make: [setup] Error 1 (ignored)
stty: standard input: Inappropriate ioctl for device
rm: No match.
foreach: No match.
mkdir: cannot create directory ‘/data/acis-bak/cmdgen/sacgs/archive/’: File exists
make: [checkin_bak] Error 1 (ignored)
mkdir: cannot create directory ‘/data/acis/cmdgen/sacgs/archive/’: File exists
make: [checkin] Error 1 (ignored)