ttitle ON and is the following 456 characters: left '_________' right '_________________' skip 1 right '|proc: ' SBMTKSUM ' |' center ' software user manual: evprnn ' left '|Site: |' skip 1 format a7 right '|vers: 1 |' left '|' presite '|' skip 1 right '|page: ' sql.pno ' |' center ' ' left '|user: |' skip 1 format a9 right '|date: ' today '|' left '|' format a7 sql.user '|' skip 1 left '|_______|' right '|_______________|' skip 1 center ' ' center ' ' _________ _________________ |Site: | software user manual: evprnn |proc: SBMTKSUM | |UNH | |vers: 1 | |user: | |page: 1 | |SBM_RO | |date: 18-MAR-98| |_______| |_______________| NAME ==== EVPRNN SUBSYSTEM ========= IFC In-Flight Calibration ENG Engineering Processing EVP Event Processing IFC In-Flight Calibration IFC In-Flight Calibration IFC In-Flight Calibration USH User Shell EVP Event Processing SKY Skymap Generation VERSION ======= 14 TITLE ===== Event Processing with Neural Net Option PURPOSE ======= EVP Task EVPRNN =============== The EVP task EVPRNN (EVent PRocessing with Neural Net option) is designed to provide for processing of raw events or partially- processed events. These events can be processed with either the conventional event location maps (which use a traditional list-search algorithm) or with the neural net location maps. In the case of neural net map location, then the energy homogeneity corrections are also applied to each event. The resulting processed event (EVP) files are required for further analysis in subsequent COMPASS subsystems. CONTROL PARAMETERS ================== Selection Set Id for Input Identifier for the selection set which acts on input data. This selection set will act on data as it is read in from either a REM or an EHR datafile. If the input datafile is of type REM, then this selection set must be of type REM. If the input dataset is of type EHR, then this selection set must be of type EHR. Only events which pass this selection set will entered into the event processing buffer. Events which fail this selection set will, however, be tabulated in the summary table (ESR) statistics. Selection Set Id for Processing Identifier for the selection set which determines whether or not an event will be processed. Events which fail this selection set will be written to the event history file (EHR) if the event history file is requested by the user, but they will not be processed. If the input datafile is of type REM, then this selection set must be of type REM. If the input dataset is of type EHR, then this selection set must be of type EHR. Selection Set Id for EVP output Identifier for selection set for output to processed event (EVP) file. Only events which pass this selection set will be written to the EVP file, if an EVP file is requested by the user. This selection set must be of type EHR. Start time and end time: The time interval for which events are to be processed. The time interval is expressed in standard COMPASS format, i.e., in the form: {MJD1:TICKS1,MJD2:TICKS2). If time is {0:0,99999:0), then the validity interval of the first and last dataset(s) will be used. Event class id (1-7): This specifies the class of events to be processed. EVPRNN can process only one class of events at a time. The event class as used here corresponds to that define by the ENG subsystem in creating the REM data : /n/ CLASS EVENT TYPE NOTES ---- ---------- --------------------------------------------- 1 GAMMA-0 These are gamma events which do not satisfy the criteria for either GAMMA-1, GAMMA-2 or GAMMA-3 2 GAMMA-1 Optimum gamma events, defined as having proper pulse height ratio between D1 and D2, proper pulse shape in D1 and forward TOF. 3 GAMMA-2 Events which do not satsify the criteria for GAMMA-1 events, but do satisfy somewhat relaxed event selection criteria. These criteria can b set by command. 4 GAMMA-3 Gamma events which do not satisfy either the GAMMA-1 or GAMMA-2 criteria. 5 CAL-1,2,3 Co-60 calibration events. CAL-1 events trigger only D1. CAL-2 events trigger only D2. CAL-3 events trigger both D1 and D2. 6 CAL-4 LED events with no corresponding veto signal. 7 CAL-5 LED events with corresponding veto signal. _________ _________________ |Site: | software user manual: evprnn |proc: SBMTKSUM | |UNH | |vers: 1 | |user: | |page: 2 | |SBM_RO | |date: 18-MAR-98| |_______| |_______________| CONTROL PARAMETERS ================== Is it calibration data (Y/N)? Y indicates that the data to be processed is calibration data. In this case, the incorporation of orbit/aspect data (OAD) is bypassed, since this data does not exist for calibration data. An answer of FALSE indicates that the data to be processed is flight data and that orbit/aspect data (OAD) should be incorporated into the event processing. Event Energy Conversions? (Y/N) A Y/N value to indicate whether the raw PMT values for each event should be converted into energy values, incorporating the specified CP1/CP2 datasets. Locate Events in D1? (Y/N) A Y/N value to indicate whether D1 event location should be performed for each processed event. Locate Events in D2? (Y/N) A Y/N value to indicate whether D2 event location should be performed for each processed event Neural Event Location? (Y/N) A Y/N value to indicate whether the event location process is to be executed with the use of neural net location maps. A value of Y indicates that the neural net (NL3) maps are to be used. A value of N indicates that the conventional (MML) maps are to be used. Scatter Angle Calculations? (Y/N) A Y/N value to indicate whether the final event processing is to be done for each event. The final event processing includes the calculation of the event scatter angle (phi-bar) along with the calculation of the event scatter direction in both COMPTEL coordinates and in galactic cordinates. Event Classification? (Y/N) A Y/N value to indicate whether each event should be classified according to the classifications listed in the specified Classification Table (CLT). If selected, then each event will be assigned an eight-character label according to the first selection set in the CLT which is satisfied by this event. Write history events to a file? (Y/N) A Y/N value to indicate whether or not an event history (EHR) file is to be created. A history file contains all of the raw, intermediate and final event parameters for each event. The history file can also be used as input to EVP so that the user can select (for example) that certain processing steps can be repeated on a given data set. Alternatively, the user may use the history data to process only the first few steps for each event and then, at some later point in time, complete the processing for those events. Because the EHR file contains all of the information about each event, it requires more disk space than the standard EVP file. Write processed events to a file? (Y/N) A Y/N value used to indicate whether a processed event (EVP) file is to be created. This file contains all of the final processed information about each event. Reject negative PMEs? (Y/N) A Y/N value used to indicate whether events with negative PME values (i.e., energy-corrected PMT signals) should be rejected. If such events are not rejected, then negative PME values are set to a value of 1 Kev for event location. (Negative PME values fall outside the range of the neural net learning experience and hence cannot be used for accurate event location.) Rejection is the ONLY action if the location uses the conventional algorithm (MML maps). So N would have no effect. Short log output? (Y/N) A Y/N value used to indicate whether the Fault Tables and individual events with faults should be omitted from the log output. Summary tables and rejected event tables for this job are still in the log (TEM) file. INPUT DATASETS ============== CLT Classification set identifier Optional INPUT dataset for the classification table (datatype CLT). If classification is requested (i.e. "Y") then, this must be non-blank. A classification table is an editable list of up to 20 names (8 characters long) and associated selection sets. If event classification is specified by the user, each event is checked using the selection sets specified in the classification table. The selection sets are accessed sequentially, starting at the first one in the clasification table. As soon as the event passes one of those selection sets, it is assigned the name (via the CLASS field in the EVP event message) associated with that selection set. *-* Input dataset (REM or EHR) Key INPUT dataset or list of datasets. This identifier defines either the file containing raw events (REM) or history events (EHR) which are to be processed. EVPRNN can accept either the raw (REM) events or partially-processed (EHR) events as input for processing. TIM TIM time interval selections Optional INPUT dataset identifier. If this is blank, all events pass in. TIM dataset(s) are an editable file of time intervals and a key _________ _________________ |Site: | software user manual: evprnn |proc: SBMTKSUM | |UNH | |vers: 1 | |user: | |page: 3 | |SBM_RO | |date: 18-MAR-98| |_______| |_______________| INPUT DATASETS ============== TIM TIM time interval selections word YES or NO to indicate whether events in the interval are kept or discarded. CP1 D1 Correction coeffs dataset Optional INPUT dataset or list of datasets of type CP1 for the D1 event conversion parameters. This must be non-blank if convert to energy is "Y" These data (provided by IFC) include the coefficients required to convert D1 pulseheight values into equivalent energy values (in keV) and also the coefficients required to correct the raw PSD values. CP2 D2 Correction coeffs dataset Optional INPUT dataset or list of datasets of type CP2 for the D2 event conversion parameters. This must be non-blank if convert to energy is "Y" These data (provided by IFC) include the coefficients required to convert D2 pulseheight values into equivalent energy values (in keV) and also the coefficients required to correct the raw TOF values. CR1 CR12 input dataset Optional INPUT dataset or list of datasets of type CR1 for the D1 PMT resolution parameters. This must be non-blank if D1 location is requested and neural event location is "N". In the case of conventional (MML) event location, these parameters are required in the D1 event location process. These data are not required for neural event location. CR2 CR2 input dataset Optional INPUT dataset or list of datasets of type CR2 for the D2 PMT resolution parameters. This must be non-blank if D2 location is requested and neural event location is "N". In the case of conventional (MML) event location, these parameters are required in the D2 event location process. These data are not required for neural event loaction. HKD HKD input dataset/list Input HKD dataset or list to use for TOF corrections ISD ISD input dataset/list Input ISD dataset or list. Used to do TOF corrections. TCF TCF input dataset Input TCF dataset or list. Used to do TOF corrections. FPM FPM input dataset Input FPM dataset. Used to do TOF corrections. TCC TCC input dataset Input TCC dataset or list. Used to do TOF corrections. MML Id for conventional map list Optional INPUT list identifier. This may be blank if neural event location is "Y" or if D1 and D2 location is "N". This is the list identifier for 21 conventional location maps (type MML). The first seven maps in the list correspond to D1 modules 1-7 (position numbers 1-7). The remaining members of the list correspond to D2 modules 1-14 (position numbers 8-21). NL3 Id for neural location map list Optional INPUT list identifier. This may be blank if neural event location is "N" or if D1 and D2 location is "N". This identifier is for the neural net event location maps (type NL3). If there are only two members in this list, then the first member will be used for all D1 modules and the second member will be used for all D2 modules. Otherwise, there must be 21 members in the list, with each list member corresponding to a specific module (as with the MML list). MHT Id of homogeneity tables list Optional INPUT list identifier. This may be blank if neural event _________ _________________ |Site: | software user manual: evprnn |proc: SBMTKSUM | |UNH | |vers: 1 | |user: | |page: 4 | |SBM_RO | |date: 18-MAR-98| |_______| |_______________| INPUT DATASETS ============== MHT Id of homogeneity tables list location is "N" or if D1 and D2 location is "N". This list identifier is for the homogeneity correction tables (type MHT). If there are only two members in this list, then the first member will be used for all D1 modules and the second member will be used for all D2 modules. Otherwise, there must be 21 members in the list, with each list member corresponding to a specific module (as with the MML list). OAD Orbit/aspect dataset Optional INPUT set identifier (dataset or list of datasets) for orbit/aspect data (type OAD). This can be blank if calibration data is "Y" or calculate scatter angles is "N". OAD is the information regarding the GRO location and aspect which is required for determining the scatter direction of each event in various coordinate systems. It also contains information on the position of the Earth"s horizon, which is used for determing the earth horizon angle for each event. MCT Coordinate conversion table Optional INPUT dataset identifier. This may be blank if neural event location is "N" or if D1 and D2 location is "N". This is the identifier for the Module Conversion Table (MCT). This datafile contains information about the location and orientation of each of COMPTEL"s 21 detector modules. This information is used by EVPRNN in order to make use of one module"s reference datasets (NL3 or MHT, for example) when processing events from another module. OUTPUT DATASETS =============== EHR Output history dataset The OUTPUT dataset identifier for the event history (EHR) file. This identifier is assigned by the USH, but may not actually be used, depending on whether or not the user elects to create an EHR file. ESR Summary table OUTPUT dataset identifier for the event summary table (ESR), which is provided by the User Shell. This datafile is always created. The data contained in this file summarizes the event processing performed by this task. Some of this information is duplicated in the log file (TEM) EVP Output processed dataset The OUTPUT dataset identifier for the processed event (EVP) file. This identifier is assigned by the USH, but may not actuall be used, depending on whether or not the user elects to create an EVP file. PARENT TASKS - in JOB ============== ======= IFCTIM IFCJP4 IFCTIM IFCJP4 ENGCTR ENGUNH ENGCTR ENGUNH IFCTIM ENGUNH IFCTIM ENGUNH IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCJR1 IFCTIM IFCJR1 IFCTIM IFCJR1 IFCTIM IFCJR1 IFCTIM IFCJR1 IFCTIM IFCJR1 IFCTIM IFCJR1 IFCTIM USHBIG IFCTIM USHBIG ENGCTR SKYRBR ENGCTR SKYRBR ENGCTR SKYRBR _________ _________________ |Site: | software user manual: evprnn |proc: SBMTKSUM | |UNH | |vers: 1 | |user: | |page: 5 | |SBM_RO | |date: 18-MAR-98| |_______| |_______________| PARENT TASKS - in JOB ============== ======= ENGCTR SKYRBR DAUGHTER TASKS - in JOB ================ ======= IFCENG IFCJP4 DDMCHK EVPCHK DDMCHK EVPCHK DDMCHK EVPCHK IFCENG IFCJR1 DDMCHK IFCJR1 DDMCHK IFCJR1 DDMCHK IFCJR1 DDMCHK IFCJR1 DDMCHK IFCJR1 DDMCHK IFCJR1 IFCENG USHBIG DDMCHK USHBIG DDMCHK USHBIG DDMCHK USHBIG SRCRBR SKYRBR ADJUNCT DATASETS INPUT ====================== *-* CLT FPM MCT TCC TCF