dataPipeline loop test

Test Objectives

Repeat runs of paced dataPipeline jobs with multi DSOs is used to

Check integrity of ldas for processing jobs in a production-like environment
Check for API memory leaks and memory corruption, operation of threads
Measurement of ldas performance

APIs affected by this test

All APIs are exercised via a dataPipeline command.

Setup

ligotools package is required for running this test. Check that it is mounted

Install the following tests script in a directory on the ldas system
- pipeloop.all - driver scrpt to bring up all pipeline looping scripts and update the configuration file of each loop

S3 raw frame files or S3 RDS L1 data must be mounted on ldas system and known to diskcacheAPI:


        There is a built in check for dc mean test. The test passes if the value is equal to the expexcted limit
        of -2.2270608572370152e-03.
        
        
Test Execution
        
		cd <your scripts directory>
		
        Usage: pipeloop.all <site> 

        
e.g.

            pipeloop.all dev 
        
        
        set the time interval between pipelines
        

            wait.tcl <NN> seconds
            e.g. > wait.tcl 30
            35398 - 7.5
            35391 - 7.5
            35392 - 30.0
            35397 - 30.0
            35399 - 30.0
            35390 - 30.0
            35394 - 30.0
            35396 - 30.0
            35393 - 30.0
            35395 - 30.0

        
        will send out a dataPipeline every 30 seconds and a dcmean and getMetaData job every 7.5 secs.        
		

		
Test Validation:
        
        All jobs should pass 

        
The stackslide DSO and the waveburst DSO sometimes will run into an error at the DSO
        e.g. 
        09/13/04-06:01:28.6: RECV: Subject: LDAS-DEV32082910 error! mpi::newJobCallback: {Rank 1 failed with error message: 
        ( conditionData function ):  Level 1: $Id: dataPipeline.html,v 1.4 2004/10/26 17:33:21 mlei Exp $      
        Status code 24: Some requested input BLK data is missing        function LALConditionData, file StackSlide.c, line 916 }
        
        09/11/04-10:38:26.2: RECV: Subject: LDAS-DEV31963558 error! mpi::newJobCallback: {
        Rank 2 failed with error message: ( applySearch function ):  Level 1: $Id       Status code -1: Recursive error   
        function LALApplySearch, file Search.c, line 1075 
        Level 2: $Id   Status code -1: Recursive error         function LALSlaveWaveburst
        Search, file Search.c, line 210  Level 3: $Id   Status code 101: cannot open /dso-
        test/waveburst/usertag/timeinterval/etg         function LALOutputWaveburst, file 
        Output.c, line 1037 }

        
        
        dcmean.log should show PASS for this test.
        e.g. 
        09/16/04-14:25:47.4: SEND: LDAS-DEV32303751 (1.2.9)
        09/16/04-14:25:54.8: SEND: LDAS-DEV32303758 (1.2.9)
        09/16/04-14:25:55.9: RECV: Subject: LDAS-DEV32303746 results Your results: mean.ilwd can be found at: 
            http://131.215.115.248/ldas_outgoing/jobs/LDAS-DEV_3230/LDAS-DEV32303746
        09/16/04-14:25:58.0: PASS: LDAS-DEV32303746
        09/16/04-14:26:01.5: RECV: Subject: LDAS-DEV32303751 results Your results: mean.ilwd can be found at:  
            http://131.215.115.248/ldas_outgoing/jobs/LDAS-DEV_3230/LDAS-DEV32303751
        09/16/04-14:26:02.4: SEND: LDAS-DEV32303763 (1.2.9)
        09/16/04-14:26:03.5: PASS: LDAS-DEV32303751