Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2017-11-28 16:21:31
Size: 87
Editor: EnzoTapia
Comment:
Revision 7 as of 2019-04-17 11:22:46
Size: 3925
Editor: MarkBarton
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Link to the aLigo Guardian Introduction Link to the aLigo Guardian Introduction:

[[https://dcc.ligo.org/public/0111/G1400016/007/guardian-introduction.pdf|aLigo Guardian]].

[[http://klog.icrr.u-tokyo.ac.jp/osl/?r=906|first start guardian klog:906]]

== Guardian System-Level Installation ==
`/kagra/apps/guardian/bin` has shell scripts guardctrl etc.

`/kagra/apps/guardian/bin/guardian` ends up running guardian in `/kagra/apps/guardian/lib/python2.7/site-packages/guardian`.

== Type B ==

The main Python scripts for the VIS Guardians, including Type B, live in `/opt/rtcds/userapps/release/vis/k1/guardian`. `TYPEB.py` is the main file - `VIS_BS.py`, `VIS_SR2.py`, `VIS_SR3.py` and `VIS_SRM.py` are one-line programs which simply load it. (They could also point to test versions of `TYPEB.py`, e.g., `TYPE_MB.py`.)

`TYPEB.py` adds `/opt/rtcds/userapps/release/vis/k1/scripts/` to the path, making available support packages including `burt.py`, `vistools.py` etc.

The Guardian makes use of various snapshot files in directories as follows. These are modified by commands in the `Take/Restore Snapshot` pop-up menu on the `VIS_CUST_TYPEB_OVERVIEW.adl` screen. The examples below are for BS, but apply equally to other Type B with obvious substitutions (BS->SR2/SR3/SRM and bs->sr2/sr3/srm).
When a model is run, the system looks for safe.snap files in 
 * `/opt/rtcds/kamioka/k1/target/k1visbst/k1visbstepics/burt`   # for the top model
 * `/opt/rtcds/kamioka/k1/target/k1visbsp/k1visbspepics/burt`   # for the payload model
These are symbolic links to the following files in the SVN-controlled userapps area:
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_safe.snap`   # for the top model
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_safe.snap`   # for the payload model
The Take Payload Model Safe Snapshot and Take Top Model Safe Snapshot menu items create these snapshots using the request files automatically generated when the models are compiled:
 * `/opt/rtcds/kamioka/k1/target/k1visbst/k1visbstepics/autoBurt.req`   # for the top model
 * `/opt/rtcds/kamioka/k1/target/k1visbsp/k1visbspepics/autoBurt.req`   # for the payload model
The Restore Safe Snapshots menu item restores both of the above .snap files at once. (The previous system had the two autoBurt.req files backed up into a single .snap file, but this was not good for making symbolic links, or for the newly introduced SDF system.)
I broke the system for making Guardian-related snaps into three sections, for IP, GAS and ALIGN/MISALIGN.
The IP setpoint is managed with the menu items Take IP Setpoints Snapshot and Restore IP Setpoints Snapshot, which use the files
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_IP.req`   # note "t" for the top model
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_IP.snap`   
The GAS setpoints are managed with the menu items Take GAS Setpoints Snapshot and Restore GAS Setpoints Snapshot, which use the files
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_GAS.req`   # note "t" for the top model
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_GAS.snap`   
The ALIGN setpoints are managed with the menu items Take Align Setpoints Snapshot and Restore Align Setpoints Snapshot, which use the files
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.req`   # note "p" for the payload model
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.snap`   
The MISALIGN setpoints are managed with the menu items Take Misalign Setpoints Snapshot and Restore Misalign Setpoints Snapshot, which use the files
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.req`   # note "p" for the payload model, and plain "align" - this is the same file as above.
 * `/opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_misalign.snap`  

KAGRA VIS Operations Manual - Guardian

Link to the aLigo Guardian Introduction:

aLigo Guardian.

first start guardian klog:906

Guardian System-Level Installation

/kagra/apps/guardian/bin has shell scripts guardctrl etc.

/kagra/apps/guardian/bin/guardian ends up running guardian in /kagra/apps/guardian/lib/python2.7/site-packages/guardian.

Type B

The main Python scripts for the VIS Guardians, including Type B, live in /opt/rtcds/userapps/release/vis/k1/guardian. TYPEB.py is the main file - VIS_BS.py, VIS_SR2.py, VIS_SR3.py and VIS_SRM.py are one-line programs which simply load it. (They could also point to test versions of TYPEB.py, e.g., TYPE_MB.py.)

TYPEB.py adds /opt/rtcds/userapps/release/vis/k1/scripts/ to the path, making available support packages including burt.py, vistools.py etc.

The Guardian makes use of various snapshot files in directories as follows. These are modified by commands in the Take/Restore Snapshot pop-up menu on the VIS_CUST_TYPEB_OVERVIEW.adl screen. The examples below are for BS, but apply equally to other Type B with obvious substitutions (BS->SR2/SR3/SRM and bs->sr2/sr3/srm). When a model is run, the system looks for safe.snap files in 

  • /opt/rtcds/kamioka/k1/target/k1visbst/k1visbstepics/burt   # for the top model

  • /opt/rtcds/kamioka/k1/target/k1visbsp/k1visbspepics/burt   # for the payload model

These are symbolic links to the following files in the SVN-controlled userapps area:

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_safe.snap   # for the top model

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_safe.snap   # for the payload model

The Take Payload Model Safe Snapshot and Take Top Model Safe Snapshot menu items create these snapshots using the request files automatically generated when the models are compiled:

  • /opt/rtcds/kamioka/k1/target/k1visbst/k1visbstepics/autoBurt.req   # for the top model

  • /opt/rtcds/kamioka/k1/target/k1visbsp/k1visbspepics/autoBurt.req   # for the payload model

The Restore Safe Snapshots menu item restores both of the above .snap files at once. (The previous system had the two autoBurt.req files backed up into a single .snap file, but this was not good for making symbolic links, or for the newly introduced SDF system.) I broke the system for making Guardian-related snaps into three sections, for IP, GAS and ALIGN/MISALIGN. The IP setpoint is managed with the menu items Take IP Setpoints Snapshot and Restore IP Setpoints Snapshot, which use the files

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_IP.req   # note "t" for the top model

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_IP.snap   

The GAS setpoints are managed with the menu items Take GAS Setpoints Snapshot and Restore GAS Setpoints Snapshot, which use the files

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_GAS.req   # note "t" for the top model

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbst_GAS.snap   

The ALIGN setpoints are managed with the menu items Take Align Setpoints Snapshot and Restore Align Setpoints Snapshot, which use the files

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.req   # note "p" for the payload model

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.snap   

The MISALIGN setpoints are managed with the menu items Take Misalign Setpoints Snapshot and Restore Misalign Setpoints Snapshot, which use the files

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_align.req   # note "p" for the payload model, and plain "align" - this is the same file as above.

  • /opt/rtcds/userapps/release/vis/k1/burtfiles/k1visbsp_misalign.snap  

KAGRA/Subgroups/VIS/OpsManual/Guardian (last edited 2019-04-17 12:17:22 by MarkBarton)