Документ взят из кэша поисковой машины. Адрес оригинального документа : http://zebu.uoregon.edu/~uochep/talks/talks03/G030633-00.pdf Дата изменения: Tue Oct 12 21:46:01 2004 Дата индексирования: Tue Oct 2 11:24:26 2012 Кодировка:

Status of Software by U. Oregon­
suspensionMon & GRB notification
Brian Stubbs, Rauha Rahkola, Ray Frey (U. Oregon)

LIGO-G030633-00-Z

UO S/W Status


suspensionMon: Overview
!

suspensionMon is a DMT monitor
" Began after S1 `heartbeat' incident on H1:SUS-ETMX_SENSOR_SIDE " First monitor to `beta-test' chInterface (see G020349-00-Z)

!

Currently functioning with log files & triggers
" Looks at _SENSOR_SIDE channels for large optics " Running with triggers since E10 (fixed a bug at the start of S3)

!

Future additional features:
" Minute trends (both online & offline access) " Alarms on DMT Alarm webpage " Monitor additional suspension channels (e.g. coils which are actuated during lock & acquisition)

LIGO-G030633-00-Z

UO S/W Status

LSC Meeting, Nov 10-13 Hanford

2


suspensionMon: How It Works
Detection Issue to detect ring-ups in suspensions for science mode, but also need to monitor out-of-lock state not be confused with lock acquisition process
!Should !Usually !Need

What suspensionMon Does on suspension channels in susceptible band (.2-20Hz) intains short-term (science mode) and long-term (out-oflock) thresholds condition on lockacquisition & transition states
!OSC !Ma !Threshholds

LIGO-G030633-00-Z

UO S/W Status

LSC Meeting, Nov 10-13 Hanford

3


suspensionMon: Example (S2 data)

! !

(see hugh's LHO e-log entry 4/11/2003) Excess power in 10-20Hz band Possibly initiated by earthquake and/or wind
UO S/W Status

LIGO-G030633-00-Z

LSC Meeting, Nov 10-13 Hanford

4


suspensionMon: Example (S3 data)

! !

Excess power in high-frequency regime (>3000Hz) Not detected by suspensionMon!

LIGO-G030633-00-Z

UO S/W Status

LSC Meeting, Nov 10-13 Hanford

5


Operator Notification of GRBs: Overview
!

Need a cooperative effort between Triggered Burst Search and control room operations
" To ensure that enough data is collected after GRB events " Example: GRB030329 (LLO off-line, giving LHO operators an opportunity to drop science mode for maintenance)

!

Provide near-real-time notification of GRB events in exchange for continued/extended science-mode operation
" Triggered Burst Search receives near-real-time notices from GCN (http://gcn.gsfc.nasa.gov/ ), about 0 ­ 3 per day " "Near-real-time" # anywhere from 0 ­ 30 minutes

!

Should be extendable to other event types in the future.
UO S/W Status

LIGO-G030633-00-Z

LSC Meeting, Nov 10-13 Hanford

6


Operator Notification of GRBs: How It Works
!

Part of GRB-event parsing Perl script
" Script sends GRB notice information into LDAS database " Can filter out test emails for "old" information

!

Sends notification to sites over TCP/IP
" Servers running at LHO ­ red; LLO ­ london " Perl/Tk script which listens on a pre-defined socket " Server sends acknowldegment response

!

Triggers EPICS alarm in control room
" Gives time remaining for data-collection period " Records in log file

!

Operator acknowledges alarm
" Alarm reset automatically
7

LIGO-G030633-00-Z

UO S/W Status

LSC Meeting, Nov 10-13 Hanford


Operator Notification of GRBs: Pipeline
Date: Thu, 8 May 2003 18:55:58 -0400 From: Bacodine To: sn@ligo.caltech.edu Subject: GCN/HETE_POSITION TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Thu 08 May 03 22:55:45 UT NOTICE_TYPE: HETE S/C_Alert TRIGGER_NUM: 2705, Seq_Num: 1 GRB_DATE: 12767 TJD; 128 DOY; 03/05/08 GRB_TIME: 82509.54 SOD {22:55:09.54} UT

TCP/IP

london (LLO server) red
!

(LHO server)

TCP/IP

Get event timestamps, type ! Set EPICS records ! Trigger EPICS alarm ! Write event to log file (continuously running)

event_type event_start "stand down" time acrux.ligo.caltech.edu (email handling / parsing)
! !

Check event time with current time Scrap test emails, emails which arrive too late, etc.
LIGO-G030633-00-Z UO S/W Status

BEEP!!

LSC Meeting, Nov 10-13 Hanford

8