check_orlist¶
The check_orlist script performs all of the steps needed to generate
the .smte file for performing an OR list review, whether LTS, preliminary
schedule, or final. In particular, it generates a list of the OR list files
which are in the correct directory for the week in question, and prompts the
user to pick the correct one. It also suggests a name for the .smte file
to write, as well as text for the email which is to be sent out. It prints
the contents of the .smte file to the screen. It also dumps log files for
various parts of the output for later inspection.
Checking a LTS or Final OR List¶
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
Navigate to the correct directory for the week you want to review (create it if necessary):
> cd $SGPROD/data/orlists/2021
> set theweek = SEP2021
> mkdir $theweek # if necessary
> cd $theweek
Just for convenience, here’s the usage message for check_orlist:
> check_orlist --help
usage: check_orlist [-h] [--prelim] theweek
Check an OR list.
positional arguments:
theweek The week to check.
optional arguments:
-h, --help show this help message and exit
--prelim If set, this is a preliminary schedule.
Now we can run the check_orlist script with the load week as the only
required argument. It will find out which directory to look for the OR list
in and provide you a list of files with timestamps, prompting you to choose
the correct one. It will also suggest which one it thinks is correct, if you
hit “Enter” it will automatically use that one:
> check_orlist $theweek
OR lists in /data/mpcrit1/mplogs/2021/SEP2021/input:
SEP2021_00.or 2021-09-01 11:47:55.011970
SEP2021_01.or 2021-09-01 13:03:39.085643
SEP2021_pool.or 2021-09-01 13:12:56.813755
SEP2021_CAT.or 2021-09-01 13:14:53.522320
SEP2021_lp.or 2021-09-01 13:16:21.955225
SEP2021_02.or 2021-09-07 12:13:17.939334
SEP2021_03.or 2021-09-07 15:45:36.156888
SEP2021_04.or 2021-09-13 14:30:39.473136
Please type the name of the OR list file listed above that you want to check [SEP2021_04.or]: SEP2021_04.or
After you’ve provided the OR list, it will check the current directory for .smte
files. Based on the ones which exist (if any), it will suggest a name for the one you’re
about to create (and that will be the default if you hit “Enter”), but you can name it
whatever you want.
Using OR list /data/mpcrit1/mplogs/2021/SEP2021/input/SEP2021_04.or.
SEP2021_00.smte 2021-09-07 19:39:12.093107
SEP2021_01.smte 2021-09-13 13:22:47.988725
I suggest using SEP2021_02.smte for the SMTE file.
These are the existing SMTE files. Please type the new one you want to write: SEP2021_02.smte
Will write SEP2021_02.smte.
After you’ve specified the .smte file you want to generate, the script tells
you what or2simodes call it’s planning to generate, and then prompts you for
your arcops username and password. It then finishes the process, making the appropriate
symlink to the *_current.smte file, and then provides suggested text for the email
to be sent out (only for convenience). It will also print the contents of or2simodes.warn
and the SMTE file to the screen.
Running or2simodes -o /data/mpcrit1/mplogs/2021/SEP2021/input/SEP2021_04.or -s /data/acis/cmdgen/sacgs/data/orlists/2021/SEP2021/SEP2021_02.smte.
SQL Server Username: jzuhone
Password:
stty: standard input: Inappropriate ioctl for device
...
See warnings in or2simodes.warn
Symlinking SEP2021_02.smte to SEP2021_current.smte.
Contents of or2simodes.warn:
Obsid 23497: 6 chips and pitch 150 to 151 - dropped chip mode should be available.
4 chips, no grating and 128 subarray. Wrong chipset?
Suggested text for email:
The table of ACIS SI_modes and parameters can be found here:
/data/acis/cmdgen/sacgs/data/orlists/2021/SEP2021/SEP2021_current.smte
and is appended below.
# For subarrays, start row is given in internal ACIS coordinates; add
# one before entering into Obscat.
# Exposure time other than 3.2 sec is given inside parentheses.
# Alternating exposures are given as a triplet in brackets:
# [5, .2, 1.6] is duty cycle 5, primary exp 0.2 sec, secondary 1.6 seconds
# 'w' indicates presence of a spatial window filter.
# Except where indicated, the energy filter has range 13keV,
# with lower limits 0.24 keV for ACIS-S, 0.36 keV for ACIS-I.
# Under 'changed', Y means an SI mode update since extraction,
# 'P' a potential dropped chip candidate,
# 'D' a successful chip drop reflected in extraction,
# and '?' that the obsid is awaiting signoff.
obsid si_mode old si_mode changed notes
----- -------- ----------- ------- -----
23321 TE_0065E TE_0065E - TOI-193, ACIS-S, VF S3, sub 256 @ 384, (0.8)
23764 TE_0065A TE_0065A D SDSS J145623.35+2145, ACIS-S, VF I3+S2-S4, (3.1)
23839 TE_00A5A TE_00A5A - PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
24272 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
24273 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
24300 TE_00914 TE_00914 D PKS 0023-26, ACIS-S, VF S3, (3)
24301 TE_00914 TE_00914 D PKS 0023-26, ACIS-S, VF S3, (3)
24303 TE_00A5A TE_00A5A - PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
24494 TE_00758 TE_00758 - PSR J1849-0001, ACIS-I, VF I0-I3+S3, (3.1), filter 0.36, 12keV
24516 TE_008FC TE_008FC - EXO 0748-676, ACIS-S, F S3, sub 128 @ 448, (0.4)
24806 TE_00CD6 TE_00CD6 - PKS 1150+497, ACIS-S, VF S1-S4, sub 128 @ 448, (0.6)
24807 TE_00CD6 TE_00CD6 - PKS 1150+497, ACIS-S, VF S1-S4, sub 128 @ 448, (0.6)
25061 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
26130 TE_00914 TE_00914 ? MCGp01m57m016_s2, ACIS-S, VF S3, (3)
26131 TE_0091A TE_0091A ? BD+22 4409, ACIS-S, VF S3, sub 128 @ 448, (0.4)
26132 TE_0091A TE_0091A ? 2MASS J23350028+0136, ACIS-S, VF S3, sub 128 @ 448, (0.4)
26133 TE_00914 TE_00914 ? 2RXS J000608.1+09425, ACIS-S, VF S3, (3)
26134 TE_00A5A TE_00A5A ? PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
Note
Warnings such as "stty: standard input: Inappropriate ioctl for device" are benign.
Checking a Preliminary Schedule¶
The steps for checking a preliminary schedule are identical to the above, except
that you must provide the --prelim flag to the check_orlist executable.
> 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
Navigate to the correct directory for the week you want to review (create it if necessary):
> cd $SGPROD/data/orlists/2021
> set theweek = SEP2021
> cd $theweek
Just for convenience, here’s the usage message for check_orlist:
> check_orlist --help
usage: check_orlist [-h] [--prelim] theweek
Check an OR list.
positional arguments:
theweek The week to check.
optional arguments:
-h, --help show this help message and exit
--prelim If set, this is a preliminary schedule.
Now we can run the check_orlist script with the load week as the only
required argument, but add the --prelim flag because this is a preliminary
schedule. It will find out which directory to look for the OR list
in and provide you a list of files with timestamps, prompting you to choose
the correct one. It will also suggest which one it thinks is correct, if you
hit “Enter” it will automatically use that one:
> check_orlist --prelim $theweek
OR lists in /data/mpcrit1/mplogs/2021/SEP2021/pre_scheduled:
asreturned_SEP2021_SOT.or 2021-09-13 12:07:37.498357
SEP2021_SOT.or 2021-09-13 12:07:37.567354
Please type the name of the OR list file listed above that you want to check: SEP2021_SOT.or
After you’ve provided the OR list, it will check the current directory for .smte
files. Based on the ones which exist (if any), it will suggest a name for the one you’re
about to create (and that will be the default if you hit “Enter”), but you can name it
whatever you want.
Using OR list /data/mpcrit1/mplogs/2021/SEP2021/pre_scheduled/SEP2021_SOT.or.
SEP2021_00.smte 2021-09-07 19:39:12.093107
I suggest using SEP2021_01.smte for the SMTE file.
These are the existing SMTE files. Please type the new one you want to write [SEP2021_01.smte]: SEP2021_01.smte
Will write SEP2021_01.smte.
After you’ve specified the .smte file you want to generate, the script tells
you what or2simodes call it’s planning to generate, and then prompts you for
your arcops username and password. It then makes the appropriate symlink to the
*_current.smte file, and then provides suggested text for the email to be sent
out (only for convenience). It will also print the contents of or2simodes.warn
and the SMTE file to the screen.
Running or2simodes -o /data/mpcrit1/mplogs/2021/SEP2021/pre_scheduled/SEP2021_SOT.or -s /data/acis/cmdgen/sacgs/data/orlists/2021/SEP2021/SEP2021_01.smte.
SQL Server Username: jzuhone
Password:
Symlinking SEP2021_01.smte to SEP2021_current.smte.
Contents of or2simodes.warn:
Obsid 23497: 6 chips and pitch 150 to 151 - dropped chip mode should be available.
4 chips, no grating and 128 subarray. Wrong chipset?
Suggested text for email:
The table of ACIS SI_modes and parameters can be found here:
/data/acis/cmdgen/sacgs/data/orlists/2021/SEP2021/SEP2021_current.smte
and is appended below.
# For subarrays, start row is given in internal ACIS coordinates; add
# one before entering into Obscat.
# Exposure time other than 3.2 sec is given inside parentheses.
# Alternating exposures are given as a triplet in brackets:
# [5, .2, 1.6] is duty cycle 5, primary exp 0.2 sec, secondary 1.6 seconds
# 'w' indicates presence of a spatial window filter.
# Except where indicated, the energy filter has range 13keV,
# with lower limits 0.24 keV for ACIS-S, 0.36 keV for ACIS-I.
# Under 'changed', Y means an SI mode update since extraction,
# 'P' a potential dropped chip candidate,
# 'D' a successful chip drop reflected in extraction,
# and '?' that the obsid is awaiting signoff.
obsid si_mode old si_mode changed notes
----- -------- ----------- ------- -----
23321 TE_0065E TE_0065E - TOI-193, ACIS-S, VF S3, sub 256 @ 384, (0.8)
23764 TE_0065A TE_0065A D SDSS J145623.35+2145, ACIS-S, VF I3+S2-S4, (3.1)
23839 TE_00A5A TE_00A5A - PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
24272 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
24273 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
24300 TE_00914 TE_00914 D PKS 0023-26, ACIS-S, VF S3, (3)
24301 TE_00914 TE_00914 D PKS 0023-26, ACIS-S, VF S3, (3)
24303 TE_00A5A TE_00A5A - PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
24494 TE_00758 TE_00758 - PSR J1849-0001, ACIS-I, VF I0-I3+S3, (3.1), filter 0.36,12keV
24516 TE_008FC TE_008FC - EXO 0748-676, ACIS-S, F S3, sub 128 @ 448, (0.4)
24806 TE_00CD6 TE_00CD6 - PKS 1150+497, ACIS-S, VF S1-S4, sub 128 @ 448, (0.6)
24807 TE_00CD6 TE_00CD6 - PKS 1150+497, ACIS-S, VF S1-S4, sub 128 @ 448, (0.6)
25061 TE_0065A TE_0065A - SNR 0519-69.0, ACIS-S, VF I3+S2-S4, (3.1)
26130 TE_00914 TE_00914 ? MCGp01m57m016_s2, ACIS-S, VF S3, (3)
26131 TE_0091A TE_0091A ? BD+22 4409, ACIS-S, VF S3, sub 128 @ 448, (0.4)
26132 TE_0091A TE_0091A ? 2MASS J23350028+0136, ACIS-S, VF S3, sub 128 @ 448, (0.4)
26133 TE_00914 TE_00914 ? 2RXS J000608.1+09425, ACIS-S, VF S3, (3)
26134 TE_00A5A TE_00A5A ? PKS 0023-26, ACIS-S, VF I3+S2-S3, (3.1)
Lastly, since this is a preliminary schedule, the ECS SIMODEs plot must be generated and the
ECS SIMODEs checked. The script will find the appropriate possible files for the ACIS
FP model data and the CTI report in the appropriate directory, and print them to
screen. Following this, you will be prompted to choose an ACIS FP file and a CTI report
file, with defaults suggested if you simply hit “Enter” (in most cases there will be only
one file for each, but if there is more than one preliminary schedule there may be multiples).
After you provide these, the script will copy these files to the current directory and
call the Generate_ECS_Plot.py script to generate the plot:
Generating the ECS SIMODEs plot.
Focal plane files in /proj/web-icxc/htdocs/mp/mplogs/2021/SEP2021/thermal:
SEP2021_ACISFP_prelim.txt 2021-12-08 15:37:03.366399
CTI files in /proj/web-icxc/htdocs/mp/mplogs/2021/SEP2021/thermal:
SEP2021_CTI_Report_prelim.txt 2021-12-08 15:37:03.366399
Please type the name of the FP file listed above that you want to use [SEP2021_ACISFP_prelim.txt]:
Please type the name of the CTI file listed above that you want to use [SEP2021_CTI_Report_prelim.txt]:
Preparing the plot for load week: SEP2021
Thermal Text File Selected is: SEP21_ACISFP_prelim.txt
CTI REPORT Text File Selected is: SEP21_CTI_Report_prelim.txt
Saving plot to: ./SEP2021_ECS_SI_modes.png
Note
Warnings such as "stty: standard input: Inappropriate ioctl for device" are benign.