software summary 1m.ellis - cm23 - harbin - 16th january 2009 four very good presentations that...

Software Summary

1M.Ellis - CM23 - Harbin - 16th January 2009

Four very good presentations that produced a lot of useful discussion:

Online Reconstruction TOF Reconstruction Database GRID

Did not hear about the control room UI as Tom has had to stop working on that.

Focus continues to be on the code needed for online reconstruction/analysis.

Will be re-starting the software phone meetings as weekly 30 minute calls, most likely afternoon UK time – contact me if you wish to attend and have preferences or times to avoid!

Online Reconstruction – D. Adey

Started by replicating Online Monitoring Histograms in G4MICE.

This tests the unpacker (common to both) and the G4MICE specific code that holds the hits.

TDCs working, fADCs almost working. GUI allows easy selection of histograms. Once fADCs are working and comparison with OM

complete, focus will move to use of actual reconstruction (e.g. TOF).

Reconstruction will result in points, tracks, emittance, etc which will also be stored as histograms with a similar GUI.

Expect a request from David for what should be shown!


Online Reconstruction – D. Adey


Select Channel by Name

Draw

TOF Reconstruction – M. Rayner

New applications in development (but already useful!): TofMonitor

Space point/time-of-flight/momentum reconstruction at a glance Are all the PMTs broken and how/correctly cabled?

TofCalibration Calibrating the TOFs for cable length and testing this calibration Plane-plane time-walk and station-station calibration in

development TofEmittance

Plot x-x’ and y-y’ trace space Calculate emittance

These are uploaded to G4MICE and easy to use Histograms automatically thrown to the screen and fill up as

you run How to run them:

./Executable cards.in datafiles– ./TofCalibration cards.in 885.000


TOF Reconstruction – M. Rayner


First MICE Muons!

Database – D. Forrest

See David’s talk for more technical details. Key points:

Development versions of the DB have been setup on heplnw17.

Currently awaiting a fix to a network problem and then will start testing access of the DB remotely through a G4MICE application.

Considering the implementation of an API as an interface between the DB and users (G4MICE, DAQ, Web, GRID, etc).

MICE Note 228 released after CM22. It is deliberately provocative, but so far only one

response (thanks JSG!!!).


Database – D. Forrest

Questions that still have no answers and some new questions:

What form will detector calibrations take (the TOF was discussed in the parallel session, but so far no news from CKOV, KL or EMR).

Will you want to query the database? If so, what kinds of information are you likely to want? As stated in past meetings, consider the kinds of

things you would like to do with the MICE data: What information do you think you will need? Where do you think you will get it from?

If you aren’t sure what the correct answer is to the second question, get in touch with us, because you may have discovered something that we have not considered!

Please read MICE Note 228 and comment!7M.Ellis - CM23 - Harbin - 16th January 2009

GRID – H. Nebrensky

10 UK Sites + Sofia support MICE. 9 UK Sites + RAL Tier 1 provide storage for data. Job submission: 2 each at Glasgow & RAL. Even though we don’t need to ask for resources yet, does

everyone know who their local point of contact is when the time comes? And how long does it take?

G4MICE is now in regular use (~1000 simulation jobs a day).

MICE Note on submitting jobs by D. Forrest coming soon. GRID interface to CASTOR at RAL has been deployed. Space unused – we currently have 1 TB of disk and 5 TB

tape. Won’t ask for more until we can actually use it. Long term request is for the same in disk and 100 TB tape.

https://www.gridpp.ac.uk/wiki/RAL_Tier1_CASTOR_planning Route any requests through Paul Kyberd.


GRID – H. Nebrensky

File Catalogue: Not enough time to go into this in detail. We need to agree on a consistent namespace for the file catalogue that

will allow us to store and retrieve files on GRID storage. Henry has proposed a concept that was discussed in the software

parallel session. If you are interested, please read his talk and get in touch with us. We will finalise this in the coming weeks.

Some more questions for the audience: What calibration data (other than that taken as part of normal MICE

physics data taking) will be taken? What metadata will be needed for analysis? (i.e. What kinds of things

will you like to be able to use to select a run or runs for a given analysis?

Momentum, step, emittance, MC or data, version of simulation, ...??? Does anyone have any preferences, views or suggestions as to where

this meta-data should be stored? If so, read Henry’s talk and contact us!

Henry’s conclusion: “My laptop battery is flat” is no longer an excuse for not getting some simulation/analysis done!


Schools and Workshops

So far, I have the impression that those people who have attended and completed the software schools have found them to be very useful.

I am happy to continue running them if there are more people who are interested in performing simulations and/or analysis of MICE data.

The software group plans to continue running informal software workshops (similar to the last one held at RAL when TOF1 arrived) to focus on specific objectives every couple of months.


Conclusion: Major Open Issues

Testing and Releases: We have not yet had a proper release cycle as originally planned. The lack of testing and regular incremental releases has cost us a lot of

time in the past few years. If I can get a volunteer to help me with this process, I think we can

make it work, which will be a big help to the software team.

Service Tasks: There are a lot of important tasks that need to be done in order to

support the end goal (i.e. Physics), however I am finding it increasingly difficult to find people who will do this work.

I think this is mostly because the vast majority of the software work is being done by a small set of students and post-docs, and their advisors/managers don’t want them “wasting time” on something that is not physics.

The problem is that without a lot of these things, the physics will never happen.

Mark’s results are an example of how it should work. He did a lot of important low level work that allowed him to write TOF reconstruction code which has produced the exciting results we have seen at this meeting. 11M.Ellis - CM23 - Harbin - 16th January 2009

software summary 1m.ellis - cm23 - harbin - 16th january 2009 four very good presentations that...

Documents