How to run DMT Loop Test via SeqInsert

In an engineering run, the actual dmt triggers are sent via a ligotools program SeqInsert via an http like process. This test exercises the method to make sure ldas is compatible with actual dmt process; the test objectives are the same as simulated DMT:

Ability of ldas to ingest data from external xml formatted by dmt process by retrieving xml from url, converting it into ilwd format and inserting the data into the database.

Account for all the data sent to ldas from dmt: at times there maybe errors obtaining the file from url, or there maybe due foreign key errors if the data is not inserted in sequence. To ensure data integrity some fine tuning maybe necessary for the test e.g extending http time out in the ligolwAPI when the system is very busy.

Continuous run of dmt alongside other LDAS jobs simulates real time situation.

The LDAS APIs affected by this test are:

managerAPI: directs processing of the insertion user commands to the ligolwAPI and metadataAPI and returns the user command status to the user.

ligolwAPI:
- Retrieves the data to be ingested from the specified url to ilwd object and sends the ilwd to the metadataAPI for insertion.
metadataAPI:
- insert the metadata ilwd data from ligolwAPI into the specified database.

Setup

Choose a directory to install the tests scripts.

rundmt.tcl starter and monitor script; install this script in directory one level above the dmt files.

           
        insertTrigsLoop.test
        - dmt driver script

        directory of dmt files  - download
		sample dmt files
		and untar and unzip the files into a subdiretory 'triggers2' 
		mkdir triggers2; cd triggers2; tar xvzf dmt-test.tar.gz
		Remove the tar ball (.gz file) from the directory since only xml files can be used.
	 
		SeqInsert - from ligotools

		

				
        
Note: The above files should be installed on your local platform which should also have ligotools
		installed already. 

		To setup the environment for ligotools, login on a sun workstation and
		enter : 
eval `/ligotools/bin/use_ligotools`
		Now cd to the scripts directory and run your test from this workstation..


        Running the test
		The test should be run from your local platform, and run in directory one level above scripts directory.

			
	
        Usage: rundmt.tcl [options] >& rundmt.log & 

        

            
                Option
                Description
            

                <site>
                ldas site [ dev | test | lho | llo | mit ]
					or <mycomputer>:10001
			

        

		
		

		
Test Verification:
		The test should be monitored initially to make sure data is flowing in a steady pace and that the insertions
		are successful impling that data is inserted in the correct sequence.
		

		Monitoring dmt
			All output from script SeqInsert is captured to stdout which can be redirected to a file at startup e.g. cit.log.

			A putMetaData user command is generated for each of the dmt files and sent to the managerAPI. The insertions
			can be monitored via cmonClient for the number of jobs and  the database insertions for the specified database. 
		
		
Analysis
			When all the xmls are sent to LDAS, the logs can be extracted via cmonClient Log page; enter the 
			gpstime ranges recorded in insertTrigs.log for logs in managerAPI, ligolwAPI and metadataAPI.
			Validate the following is true for successful insertions:

            
			

			Number of files finish by SeqInsert should trail closely to number of jobs submitted.
				 grep -c submit < insertTrigs log file > 
 grep -c finish < insertTrigs log file >  
			Jobs statistics page should report the number sent by SeqInsert.

			
Database statistics page should report the total number of insertions sent by SeqInsert.

			
Number of gds_triggers inserted in database = number of gds_triggers in xml files 
				use guild query 

				
select count(*) from gds_trigger where process_id in 
(select process_id from process where program
in ('glitchMon', 'PSLmon','LockLoss','BitTest','SegGener'))
			to confirm this is the case.
			Other records inserted include process and segments. Also confirm this number in the database is the
			same as in xml files. 

			Expected number of insertions per round with the current set of dmt files:

				Number of process records		= 		9 ( 1 BitTest 2 glitchMon 1 LockLoss 3 PSLmon 2 SegGener )

                    Number of gds_trigger records	=	34450

	                Number of segments records		=	  489

				
			
			Notes on SeqInsert:

			

			Check SeqInsert state by typing 'SeqInsert check'. Possible returns:
			
                                State is run   or 
				State is idle  or 
				State is error
            
			If state is idle or error, examine the dmt log for errors; the test has to be restarted.

            
To shutdown the test, type
            SeqInsert shutdown & 
            and kill off the tcl script.           	
            
			If there is a discrepancy search the logs for red balls to account for missing records.
			
Also examine the ldas database web page for the number of processes, segments and
			gds_triggers inserted to make sure they match the expected number.
			
			
If all the process and trigger data are inserted, the test passes. 
			If not, the test fails and the errors in the logs should account for all data received at LDAS.