 |
 |
Hi Jeremy, I appreciate the idea of re-organizing the ECAL monitoring steering files. However, I think this is something that, before, has to be discussed in one of the hps-ecal meetings: what we used so far, even if not well organized, works, and before modifying it, we need clearly to define how and what. Best, Andrea On 02/05/2015 08:55 PM, McCormick, Jeremy I. wrote: > Hi, > > I'd like tocreate or identify steering configurations for the following ECAL monitoring stations. > > 1) Raw data - EcalRawDataMonitoring.lcsim > > This should look at the raw data collection from the LCIO file, which would include RawCalorimeterHit information and the supplementary mode 7 object if it exists. Running pedestal monitoring (strip chart?) should probably go here, too. > > 2) Window mode - EcalWindowModeMonitoring.lcsim > > This plots the window mode data e.g. from cosmic runs. > > 3) Reconstruction - EcalReconMonitoring.lcsim > > This should plot the results of the ECAL reconstruction e.g. information from the CalorimeterHit and Cluster collections. > > 4) Trigger - TriggerMonitoring.lcsim > > This should display the GTP cluster results for the event, as well as any useful event-based trigger diagnostic plots. > > 5) Event Display - EcalEventDisplay.lcsim (maybe??) > > This event display can tie into any of the data collections, including raw data, cal hits or clusters. This could be an alternate or supplementary config for either the raw data or reconstruction station. For instance, we could have an "EcalClusterEventDisplay.lcsim" for hooking the event display into the cluster collections, etc. > > 6) LED - EcalLedMonitoring.lcsim > > I believe there is an existing LED monitoring configuration, which we should check. I'd like to have access to some LED runs to test this. > > Can anyone identify for me which steering files already do some or all of these things? (I know some of them exist already, so I will look through the steering configurations myself as well.) > > If these don't exist and we decide that we want them, can we identify people to work on each of them? > > I think it is preferable to have specific, rather limited configurations for these different stations rather than "kitchen sink" style setups that include many different plots of different types of data. When there are too many plots being made, it becomes unwieldly to try and look at them all, and for performance purposes it is better to have a number of parallel stations rather than one which is showing all the plots from a single steering file. > > This all relates to the following JIRA task. > > https://jira.slac.stanford.edu/browse/HPSJAVA-415 > > If you want to discuss some of this in detail, feel free to comment on that item with your thoughts, rather than use email. > > Once we have these various configurations identified and created, I would like to start testing them on some of our existing (2014) datasets as I work on the monitoring app. This will help me not break stuff! > > Thanks. > > --Jeremy > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the HPS-SOFTWARE list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1