Online Analysis Integration and Development
Project Coordinators
Stuart Anderson (sba at ligo.caltech.edu)
Patrick Brady (patrick at gravity.phys.uwm.edu)
Mailing Lists
- daswg Discussions are of broad impact
- daswg-online Discussions specific to the online analysis architecture and implementation
Documentation
- Online analysis infrastructure at the observatories
- Setup of the BOSS databases
- Segment database documentation
Open tasks
This is a list of things that need to be accomplished in order to have an online analysis engine which is robust and flexible. There will need to be some detailed planning of each item, but this should get us started. Follow the links below for technical documentation - contributors should please add documentation and notes early and often to keep the rest of the team informed:
- Online analysis HOWTO (Who?)
- E11 FAQ (answers to question about E11 online analysis and access to the data)
- Discover science mode
(Who?)
- Document existing DMT method
- Document the file format used
- Document method for flagging good hardware injections
- Document how seqInsert is set up
- LSCsegFind tool
- RDS Generation (Greg and Who)
- Under the web interface
- Which levels to generate and publish
- Ask Isabella to develop the list of channels
- Which levels are and needed?
- Insure that the duration of each frame file is appropriate
- Generate and discover calibration data (Who)
- Document the frame format
- How to publish this data for use by the search codes
- Generate calibrated data (Who)
- Standalone code
- Publication of the frame files
- Movement and publishing data for LDR(Who)
- Document observatory config
- What do we have? Document.
- What do we need?
- Diskcache and data discovery
- Movement and publishing data for cluster (Who)
- Document observatory config
- What do we have? Document.
- What do we need?
- Module to establish availability to job daemon
- Onasys (Kipp Cannon and Brian Moe)
- Queries data discovery tools.
- Calls upon user-supplied program (eg. python script, sh script, Intercal program, etc.) to generate DAGs as needed.
- Maintains a database of job status (running, failed, etc.).
- Provides alarms
- Each running analysis uses its own daemon.
- Tools to publish "archival data products" (Who)
- Publication script
- Movement script
- Only documented data products will be archived
- Tools to access "archival data products" (Who)
- Retrieval
- Visualization
- Reference Server Machines
- Linux O/S
- Document machine build
- Document site specific config
- LSC Data Grid Server installed (DOE Certificate Based)
- Secure web server installed (DOE Certificate Based)
- Will need to "see" data sets (requirements to be established)
- Notification protocol (XXX)
- RSS Feeds?
- To trigger follow-up coincident/coherent analysis
- To trigger manual follow-up
- Software stack preparation/integration/testing/release (Who)
- Software stack deployment/testing
Contributors
Stuart Anderson
Christine Barker (LHO admin)
Patrick Brady
Duncan Brown (LALApps/LJM and inspiral)
Kipp Cannon (LALApps/LJM and burst)
Junwei Cao (DMT and burst)
Scott Koranda (Grid computing guru)
Greg Mendell (LHO LDAS admin and pulsar)
Brian Moe (Software engineer)
Keith Riles
Shannon Roddy (LLO admin)
Xavier Siemens (Calibration and pulsar)
Igor Yakushin (LLO admin and burst)
John Zweizig (DMT and burst)