1 / 13

ITR 2003 DMT Sub-Project

ITR 2003 DMT Sub-Project. John G. Zweizig LIGO/Caltech. DMT Overview. DMT – Detector characterization platform in C++ Written for monitoring IFO state, sensitivity, noise, etc. Signal processing, detector characterization class libraries. Online use (in LIGO control room)

amberw
Download Presentation

ITR 2003 DMT Sub-Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITR 2003 DMT Sub-Project John G. Zweizig LIGO/Caltech

  2. DMT Overview • DMT – Detector characterization platform in C++ • Written for monitoring IFO state, sensitivity, noise, etc. • Signal processing, detector characterization class libraries. • Online use (in LIGO control room) • Run continuously on ~10 Solaris SMP nodes (reference platform) • Stream of current IFO data received directly from DAQ. • Real-time, low latency response • Operator feedback: alarms, IFO state, sensitivity, noise/transient summaries • Output: real-time triggers (transient descriptors), Statistics trends

  3. Online DMT Data Flow

  4. Growing Use – Offline Analysis • Offline analysis uses • Run “monitors” with different configurations on entire raw data samples. • Data quality investigations • Transient detection • Use detector specific codes in offline GW search pipelines. • Impediments to offline use • Linux installation difficult (no binary distribution, no reference platform). • Impacts development as well as universal use • No standard offline environment defined • Unable to use LSC computational clusters • Global data access and publication not provided • Sensitive data – administrative nightmare • Local job submission only • Single data stream input (multiple inputs useful for IFO correlations). • ITR2003 DMT sub-project will enable this use

  5. Offline DMT Data Flow

  6. ITR2003 Mission • Grid enable DMT • Improve portability • Interface to Globus tools and LDR • Condor enable • Develop remote submission capabilities • Install on LSC clusters • Without adversely affecting the primary DMT mission • Maintain Solaris compatibility • Transparent access to DAQ broadcast stream • Interface to ROOT Graphics • Operator feedback, Database Interfaces

  7. Participants • Erik Katsavounidis (MIT PI) • Lee Samuel Finn (PSU PI) • John G. Zweizig (Caltech) • Junwei Cao (MIT, ITR2003) • Anonymous Hire (PSU) • Part time hire (UWM) • 25% for deployment, other time as available

  8. Technical • Linux portability • Autoconfigure/automake • Rpm generation • Periodic build • Standardize offline runtime environment. • Decouple from CERN Root package • Data access transparency • Interface to directory / LDR • Running on the grid • Use Condor features (checkpointing, etc) • Process management • Remote submission

  9. Technical 2 • Maintaining clusters • Installation / maintenance • Usage prioritization. • Clusters at observatories & tier 2 centers. • Validation • Component tests for nightly build • Nuts ‘n Bolts • Multiple data streams • Rationalize dependencies (fftw-3, …) • Etc?

  10. Stakeholders • LSC • Extend DMT availability to LSC offline analysis. • Improve portability. • Formalize use of DMT on LSC Linux clusters • Enable remote submission. • Protect data access. • Grid community • Demonstrate gridification of an existing Scientific software package • Grid middleware use in real scientific applications allows feedback to grid community e.g. which tools/features are useful/needed • Productive readjustment of priorities, more useful middleware

  11. Plans (2004) • Improve portability & versioning of DMT software • Implement build procedure using autoconfigure, automake. • Automate periodic builds & tests of current version. • Build & maintain binary RPMs (APTs?) for LSC reference platform. • Define standard execution environment. • Interface DMT to grid utilities • Data access / publishing • User certification? • Verification • Build library of component tests for periodic verification. • Cluster support (MIT, PSU, UWM) • Installation

  12. Plans (2005) • Set up DMT to use Condor features • Disable message system (alarms, graphics) • Set up to run as “standard” Condor job • Remote submission architecture • Wrapper/supervisor? for condor jobs • Web interface for submission. • Cluster support (PSU, UWM, MIT)

  13. Plans (2006-7) • Continue development of remote submission architecture • Wrapper/supervisor? for condor jobs • Web interface for submission • Cluster support (MIT, PSU, UWM)

More Related