...
- David: Identify the location for adding xml so that beamspot histograms are displayed in online monitoring.
- /moncfg/beamspot on the P1 central file server
- Philippe+Rainer: Take the example of an existing xml file and tweak it to show some distributions from our vertex algorithm.
- See: OhpNexus User Guide
- All: Play with the xml to see how much information can be extracted, e.g., mean, truncated mean, RMS, error on mean.
- Philippe: Contact Davide Caforio about DIP interface. Find out what else is needed to transmit beamspot parameters.
- Instructions for publishing data are here: Publishing via DIP
- Rainer+Philippe: Create a PVSS project for the beam spot and understand how to store and retrieve extracted parameters.## Some information here: Archiving in PVSS
- No more need for this, as the PVSS interface and project will be handled by Central DCS
- Rainer+Philippe: Check out the track impact parameter algorithm and run it in athena. Look throught the histograms it produces and compare with the vertex algorithm.
- David: Identify the set of histograms from the vertex algorithm that will be common with the impact-parameter algorithm. Encapsulate in a python class/method that can be executed from either algorithm.
- David: Instantiate a second instance of the vertex algorithm with different parameters in the same job and make sure that the method produces two distinct sets. of histograms for both the algorithm-specific part as well as for the common part.
- David+Rainer: Follow up with Tomasz on how the per-lumi-block histograms are stored, in particular, on a path with the correct run number and under the /EXPRESS folder.
- David+Rainer: Do a low-level check on how the gatherer handles statistics. Verify that the individual contributions add up correctly, including event weights and errors.
- Rainer: Further discuss the pROS redistribution scheme with Benedetto, Per, Hans-Peter.
...