DFS Departement Home Page Pipeline infrasturcture
	HOME INDEX SEARCH HELP NEWS

Testlog for DataOrganizer (DO) tests in dfs-4_7x

Introduction
Scope
The main requirements
List of testruns performed
Detailed information about the testcases

1. INTRODUCTION

1.1 PURPOSE

This document describes the effective results of the integration and validation tests performed on dfs-4_7x with serveral versions of the pilDataOrganizer DO

between 10/12/2003 and 9/5/03 .

1.2 APPLICABLE DOCUMENTS

[APD1] Testing the pipeline subsystem, internal docno dfs-vol02-19-001

[APD2] Testreport DO-1_12 in dfs-4_3, internal docno dfs-vol02-31-003

[APD3] Testreport DO-1_12 in dfs-4_3_1, internal docno dfs-vol02-31-004

[ADP4] DataOrganizer-1.13/14 in dfs-4_4, interanl docno dfs-vol02-31-009

[ADP5] DataOrganizer-1./14 in dfs-4_4, interanl docno dfs-vol02-31-013

[ADP6] DataOrganizer-1./14 in dfs-4_4_6, interanl docno dfs-vol02-31-016

1.3. REFERENCE DOCUMENTS

Not applicable

2. SCOPE

The DO receives data files from the dhsSubscribe, classifies them according to the instrument and generates reduction blocks RBs..

3. RECALL OF THE MAIN REQUIREMENTS TO BE TESTED

The main requirements to the DO are

• Starting the DO should be much faster, because of some changes in the source code itself and because of the use of a new version of the database MSQL

4. MEANS USED FOR TESTING

The testcases of this testreport were carried under the conditions described in chapter 1.
No special settings or configurations were necessary except running test-dfs.sh after a new DO release was installed.

5. CHRONOLOGY

Because the DO is tested fully automatically, all chronologic dependencies are coded directly in the testscript test-do.sh and therefore it is not necessary to repeat them here again

6. Testrun definition

7. Logging of the tests and currently open points

The following table contains all relevant informations about the test of the current version of ngamsIngest like

• problems which are still open from previous tests
• problems which arises newly in this version
• the testresults of new testcases developped for this version.

Testcases, which are not mentioned in this testlog, produce the same testresult as in the previous version.

The table is used to keep track and to have an overview over the open problems.

For additional informations about the testcases see the non-regression test script test-ngamsIngest.sh

General problems and infos
Testsuite 01: run_random collected data
Testsuite 02: Test the commandline interface
Testsuite 03: Test with SUSI data
Testsuite 04: Test with EMMI data
Testsuite 05: Test with SOFI data
Testsuite 06: Test with TCdata
Testsuite 07: Test with ISAACdata
Testsuite 08: Test with FORS1 data
Testsuite 09: Test classification with aritifical rules
Testsuite 10: Test with FORS2 data
Testsuite 11: Test with UVES data
Testsuite 12: Test with VIMOS data
Testsuite 13: Test with VINCI data
Testsuite 14: Test with NACO data
Testsuite 97: Test error situations
Testsuite 98: Test miscellaneous situations

Testrun	Description	status
	General
021129 HP	- "ipip fors1-2.3.1" ==> on wu0pl (HP 11.0) fors1-2.3.1 is compiled and installed without errors	ok
021129 RH7.3	- "ipip fors1-2.3.1" ==> compilation error in poly.cc. The compiler GCC 3.2 delivered with VLT APR2003 failed with segmentation fault	NOGO
021129 HP	- "ipip fors2-2.3.1" ==> on wu0pl (HP 11.0) fors2-2.3.1 is compiled and installed without errors	ok
021129 RH7.3	- "ipip fors2-2.3.1" ==> compilation error in poly.cc. The compiler GCC 3.2 delivered with VLT APR2003 failed with segmentation fault	NOGO
021129 HP/RH7.3	- "ipip uves-1.6.1" ==> installation without errors	ok
021129 HP11/RH7.3	- "ipip isaac-3.5" ==> installation without errors	ok
021129 HP11/RH7.3	- "ipip naco-1.1" ==> installation without errors	ok
021129 HP11/RH7.3	- "ipip vimos-0.7" ==> installation without errors	ok
021129 HP11/RH7.3	- "ipip vinci-1.9.0" ==> installation without errors	ok
021205, HP	==> Version RBS-1_11 is used ==> Midas 02SEP is used	ok ok
021205, HP	==> dpclient is not delivered because of problems in SAS library ==> dpmkspace is not delivered because of problems in SAS library ==> dppacker is not delivered because of problems in SAS library	nogo nogo nogo
021205, HP	==> ngamsIngestControl is new ==> start-ngamsIngest is new ==> watchdog-ngamsIngest si new	ok ok ok
021205, HP	Conclusion	???
	DFS-DOTest-01_random
010825	01-001: mixed EMMI/SUSI/SOFI ==> no appropriate calibration data found	->GM
020424	Conclusion	GO with sideeffects
	DFS-DOTest-02_cmdLine
020511	02-044: vimos pipeline was not installed properly	->GM
020511	02-055: vimos pipeline was not installed properly	->GM
020511	Conclusion	GO with sideeffects
	DFS-DOTest-03_susi
	DFS-DOTest-04_emmi
	DFS-DOTest-05_sofi
????	- Keyword DET.EXP.NO is not defined in the dictionaries brought from LaSilla, but it is used in some sofi testfiles	->GM
010402	Logfile not used as referencefile
????	Conclusions	????
	DFS-DOTest-06_tc
	DFS-DOTest-07_isaac
020424	07-008: ISAAC frames with fitsFactory:
020430	==> DO creates RBs for some product files	->GM
	07-009: ISAAC with TPL ID 'ISAACSW_img_obs_AutoJitteroffset”
020430	==> all files are classified as JITTER_OBJ, but half of them are “SKY” frames	->GM
	07-014: recipe img_jitter
020430	==> all file are lassified as JITTER_OBJ, but half of them are “SKY” frames. Reason is the wrong length of keyword TPL.ID (see SPR DFS00560 and DFS01019)	NOGO
020829	Conclusion	GO with sideeffects
	DFS-DOTest-08_fors1
010327	08-014: - No appropriate MASTER_SKY_FLAT_IMG could be found	->GM
020829	Conclusion	GO with sideeffects
	DFS-DOTest-09_classification
010327	09-001: Test fits file can be classified", no rule for single frame", no rule for EoT frame ==> frames cannot be classified anymore. RBs with load_ima are generated	->GM
010429	09-003: fors.bdd not delivered ==> DO dies with core dump	->MP
981204	09-010: last frameis missing; new frame is not processed (unknown instrument) ==> The EndOfTemplate event is not detected (DFS00423)	NOGO
981204	09-011: One frame in the middle is missing; an error or warining should be detected ==> Error or warining is not detected (DFS00463)	NOGO
010215	09-018b: akd-file does not exist ==> DO should ignore this file, but it terminates DFS00625)	NOGO
030430	09-018c: pdd-file does not exist ==> DO terminates without any error/warning or core dump	NOGO
030430	09-027: complex rule for rawframe in bdd-file ==> Testcase has to be checked against the test oal	->GM
030430	Conclusions	GO with sideeffects
	DFS-DOTest-10_fors2
020424	General:
020424	==> The message to create the 2nd osttable should be different from the message of the 1st ostTable.	->MP
020523	10-016: NEW: Files from different instruments arrive (FORS2 -->UVES -->FORS2)
020829	Conclusion	GO
	DFS-DOTest-11_uves
	11-006: test all rawframe and calframe definitions with FitsFactory
010227	- No appropriate MASTER_BIAS_BLUE could be found	->GM
010227	- SCIENCE_BLUE: No appropriate MASTER_FLAT_BLUE could be found	->GM
010227	- SCIENCE_SLICER_BLUE: No appropriate MASTER_FLAT_BLUE could be found	->GM
010227	- STANDARD_BLUE: No appropriate MASTER_FLAT_BLUE could be found	->GM
020424	==> Rule FIBER_ORDER_FLAT_OZPOZ not detected problably problem with fitsFactory	->GM
020424	==> Rule FIBER_ORDER_FLAT_SIMCAL not detected. Problably problem with fitsFactory.	->GM
020424	Conclusions	GO with sideeffects
	DFS-DOTest-12_vimos
020516	12-001: NEW, test 'wrong value in keyword INSTRUME' --> fits file is rejected, a corresponding error message is sent	ok
020516	12-002: NEW, test correct value 'VIMOS' in keyword INSTRUME ==> Instrument value is accepted	ok
020516	12-003: NEW, Test invalid value 'xxx VIMOS yyy' ==> Instrument value is rejected	ok
	DFS-DOTest-13_vinci
020516	13-001: NEW, test 'wrong value in keyword INSTRUME' --> fits file is rejected, a corresponding error message is sent	ok
020516	13-002: NEW, test correct value 'VINCI' in keyword INSTRUME ==> fits file could not be classified ==> solved in testrun 020516	ok
020516	13-003: NEW, test 'wrong value UVE in keyword INSTRUME' --> fits file is rejected, a corresponding error message is sent	ok
020516	13-004: NEW, Test invalid value 'xxx VINCI yyy' ==> Instrument value is rejected	ok
020516	13-005: NEW, Test valid value 'VINCI yyy' ==> Instrument value is accepted as VICNI	ok
020514	13-006: NEW, test all rules with fitsFactory ==> Keyword ISS.CONF.INPUT12 has wrong format (string instead of integer)	->CS
	DFS-DOTest-14_naco
	General:
020511	the following keyword used in fits headers but not defined in dictionaries - INS.SOFW.OPSMODE - INS.XFLIP - INS.CWLEN - INS.TEMP.FPI - INS.TEMP.DET - INS.FPI.LAMBDA - INS.FPI.Z - INS>FPI.Y - INS>FPI.X - INS.PRES-MON.PRESi - INS.PRES-MON.NAMEi - INS.BFOCUS - INS.FOCUS.ENC - INS.TADC.TYPE - INS.TADC.WLENGTH - INS.TADC.PHINF - INS.TADC.ZDIST - INS.ADCi.POS - INS.GRP.ID - INS.GRP.NAME - INS.GRP.NO - INS.GRP.TYPE - DET.FRAM.NO - DET.FRAM.UTC - DET.FRAM.TYPE - DET.EXP.UTC - DET.IRACE.SEQCONT - DET.IRACE.ADCi.NAME - DET.IRACE.ADCi.HEADER - DET.IRACE.ADCi.ENABLE - DET.IRACE.ADCi.DELAY - DET.IRACE.ADCi.FILTERi - DET.VOLT1.CLKHINMi - DET.VOLT1.CLKLONMi - DET.VOLT1.CLKLOi - DET.VOLT1.CLKHIi - DET.VOLT1.DCNMi - DET.VOLT1.DCi - OCS.SOS.INS.MODE ==> check testcase 98-004 if the keyword are defined in dictionaries	->YJ
020521	14-001: NEW, test, that wrong value in keyword INSTRUME is rejected	ok
	DFS-DOTest-97_errors
010225	97-012: Calibration file has zero length - This situation happens at Paranal in April 2000 ==> DO still dies with coredump (DFS00675)	->MP
020424	Conclusion	GO
	DFS-DOTest-98_misc
	98-005: test the man pages
020424	==> The man page for pilDataOrganizer is not uptodate	->MP
	98-007: Test sequence of file processing
020424	==> The EotSignal last raw frame is not detected, if the next frame has an unknown/uninitiated instrument (DFS00408)	->MP
020424	Conclusion	GO with sideeffects

Send comments to <gmekiffe@eso.org> Last modified: Fri, May 9, 2003 6:21 PM ->