Event Filtering
Jump to navigation
Jump to search
Events can be filtered by the MIDAS logger (mlogger) into different saved files based on the Event ID or the Trigger Mask (see MIDAS Event Structure). They are specified in the Frontend Equipment List of an event.
To filter events in this way, it is necessary to set up the required number of logging Channels. By default, only one logging channel is created.
Event selection for each of the logging channels can be done by specifying the Event ID key and/or the Trigger mask key
Use the Filename key to specify the path and/or filename for each logging channel.
[deap@ladd07 src]$ odbedit [local:deap:R]/>cd logger [local:deap:R]/Logger>ls Data dir /data7/deap/scratch Message file midas.log Write data n Auto restart n ODB Dump y ODB Dump File run%05d.odb Auto restart delay 0 Tape message y Channels SQL Run duration 0 Next subrun n Subrun duration 0 History [local:deap:R]/Logger>cd Channels/ [local:deap:R]Channels>ls 0
[local:deap:R]Channels>copy 0 1 <<< Duplication of channel 0 to channel 1
[local:deap:R]Channels>cd 1/settings [local:deap:R]Settings>ls Active y Type Disk Filename run%05d.mid.gz Format MIDAS Compression 1 ODB dump y Log messages 0 Buffer SYSTEM Event ID -1 Trigger mask -1 Event limit 0 Byte limit 0 Subrun Byte limit 0 Tape capacity 0 Subdir format Current filename run00102.mid.gz
[local:deap:R]Settings>set "Event ID" 2 <<< Change the logging condition [local:deap:R]Settings>set Filename runid2%05d.mid.gz <<< Change the destination logging file name
[local:deap:R]Settings>ls Active y Type Disk Filename runid2%05d.mid.gz Format MIDAS Compression 1 ODB dump y Log messages 0 Buffer SYSTEM Event ID 2 Trigger mask -1 Event limit 0 Byte limit 0 Subrun Byte limit 0 Tape capacity 0 Subdir format Current filename run00102.mid.gz
Finally, restart the logger.