Software/Monitoring Commissioning List

Hi, Matt.

I have some comments about some of these items.

"on/offline software integration" - This is not completely there yet, as there are, for instance, ECAL monitoring Drivers still using the old conditions system.  The SVT monitoring Drivers do not use the new conditions system at all.  And there is lots of user code that still does not use it.  As far as some of the primary software modules, like the reconstruction, this is now integrated fully.

"check & load conditions (ECal/SVT) into db" - I think this is probably a conflation of three different items.  It would probably be better to break this out into ECAL and SVT conditions.  Also, whether or not the conditions are loaded and the state of the procedures for doing this are separate.  In fact, there's now a command line tool which can be used to load conditions into the database from text files.  We have used this successfully for the ECAL, and it boils down to a one-line command on the console.  This has not been done for the SVT, where I understand an XML input format will be used.

"EVIOtoLCIO converter working" - Again, here you might want two separate items for ECAL and SVT.  This is working fine for raw mode data from the ECAL.  We will probably be able to quickly write the conversion for pulse mode once data is available.  I think this might not be done for some time for the SVT.

"MonitoringApp functional & performant" - I'm not sure about this one.  I'd need a better qualification of "performant" I think to say much about it.

"Monitoring Plots: ECAL" - My understanding is that most of these are not converted to use the new conditions system yet, and so this should not be considered complete.  Andrea might have more details there on the status of this.

"Monitoring Plots: SVT" - I'm not sure the JIRA item you listed there is exactly relevant.  There is a distinction in the framework between monitoring Drivers which generally just plot things, and subsystem monitoring components which can raise soft alarms/warnings.  You might want to make a "Subsystem Monitoring: SVT" item to track this separately.  As far as I know, this does not exist yet for ECAL either.

"Manual/shifters instructions for online monitoring" - You're right.  This is not fully documented.  There is a basic page just showing how to run it.  I will work on more complete documentation after a round of updates/changes to the app are completed in the near future.

Also, as discussed in the general meeting, please add an item about creating technical documentation on the full EVIO data format.

Thanks.