Actions
GEOM240613¶
24 June at 15.00 BST
- Geometry (Ryan Bayes)
- Geometry Verification (Stefania Ricciardi)
- Absorbers (Pavel Snopok)
- CAD Models (Jason Tarrant)
- Detector Groups: Tracker (Chris Heidt?)
- Magnets (Victoria Blackmore, others?)
- AOB
Discussion Items from Previous (i.e. Collaboration) Meetings¶
- What are the priorities for geometry development?
- How do we include the survey information?
- Does the list of members need to be redefined?
- How does (should) the MAUS geometry interact with the g4beamline geometry?
Actions from Previous Meeting¶
- Jason - to refine CAD models in beam acceptance region (He windows, flanges, etc..)
- STANDS
- Ryan - solve problen in traslation GDML->MAUS Modules
- DONE further optimization may be needed
- ACTION: Ryan to upload Jason's CAD model to DB to have a first version of STEP IV geometry in a MAUS release.
Diffuser and cooling channel in two separate CAD files to be merged.- STANDS
- ACTION: Stefania to check how much time/particle/s with CAD geometry on RAL Tier2 (Matt reports 2.8 s/particle on his laptop)
- STANDS Stefania checked that legacy files give 2.7s/muon with STEP IV on TIER2 PPD machines
- ACTION translate TOF (from legacy files updated by Durga), DIFFUSER (CAD files from Jason) geometry to gdml and store to DB (Ryan)
- STANDS - integrated legacy geometries, but positioning of TRACKERS, DIFFUSER, and ABSORBERS still needed
- ACTION: Integrate Absorber (MAUS Modules) by Pavel in new geometry and store to DB (Ryan)
- NEW
- ACTION: FIX tracker GDML files - problem in translation to MAUS Modules (Ryan and Chris H.)
- STANDS
- ACTION: Improving TRACKER Geometry description - fibres outside fiducial region (Heidt)
- STANDS
- ACTION: GEANT4 warning messages when geometry from CAD import is used (Ryan)
- DONE - removed from upgrade to g4.9.5
- ACTION: Produce geometry documentation for code developers and pass information to Ryan (Matt)
- IN PROGRESS
- ACTION: Victoria Blackmore to implement magnet field map interface (Victoria)
- STANDS
Phone etc¶
Dial-in numbers¶
- UK: 0844 4 73 73 73
- Switzerland: 0848 560 347
- US: 1 415 363 0833 (or 1 646 652 0772)
- Italy: 0821 230 749
- Others listed below
- Skype +49 1803 001 178
PIN: 746868 (PIMUNU)
International Dial in numbers¶
- UK: 0844 4 73 73 73
- Austria 0820 4000 1502
- Belgium 070 35 98 66
- France 0821 230 749
- Germany 01803 001 177
- Ireland 0818 270 007
- Italy 848 391 819
- Netherlands 0870 001 909
- Poland 0801 003 533
- South Africa 087 550 0375
- Spain 902 885 318
- Sweden 0939 2066 300
- Switzerland 0848 560 347
- United States 1 415 363 0833 (or 1 646 652 0772)
- Skype +49 1803 001 178
- World +44 844 580 0555
Chris Rogers Notes¶
- Wrap up from CM
- Maria Leonova is in charge of G4BL
- Likely that we will not get running in June 2014, hence magnetic fields should have higher priority than tracker
- Survey and geometry
- There was some discussion on survey, clarified below
- Engineering elements integration
- Jason to get survey points from surveyor
- Jason to provide CAD drawing for each "engineering" element with survey points marked on it
- Jason places engineering CAD in overall survey
- Physics elements integration (e.g. detectors)
- Jason to get survey points from surveyor
- Detector group is responsible for providing data on relationship of sensitive detectors to survey points
- Where detectors are overconstrained, Ryan is to provide code which makes a best fit and throws an exception if the fit is out-of-range
- Presumably physics group is responsible for providing data on fit range (i.e. SciFi maybe wants ~ 500 microns; TOF maybe wants ~ 1 mm; ckov wants ~ 1 cm... etc)
- Ryan is to define MiceModule/GDML schema to which detector groups should interface
- G4BL job
- Two sample use cases were identified
- User wants to run G4BL on his laptop (and possibly interface directly to MAUS)
- User wants to pull down a pre-existing data set from e.g. config db and interface with MAUS
- Propose writing a MAUS mapper that takes empty spills and fills with dataset
- Note #990
- Then make three different executables, in the spirit of
bin/simulate_mice.py
- An exe that uses MapPyBeamMaker to generate an input from a g4bl "beam" file and fires the rest of the MC
- An exe that fires g4bl and does nothing
- An exe that fires g4bl, brings g4bl into the full MC and then goes from there.
- Two sample use cases were identified
Actions¶
- Jason - to refine CAD models in beam acceptance region (He windows, flanges, etc..)
- DONE
- Ryan - solve problen in traslation GDML->MAUS Modules
- DONE further optimization may be needed
- ACTION: Ryan to upload Jason's CAD model to DB to have a first version of STEP IV geometry in a MAUS release.
Diffuser and cooling channel in two separate CAD files to be merged.- STANDS
- ACTION: Stefania to check how much time/particle/s with CAD geometry on RAL Tier2 (Matt reports 2.8 s/particle on his laptop)
- STANDS Stefania checked that legacy files give 2.7s/muon with STEP IV on TIER2 PPD machines
- ACTION translate TOF (from legacy files updated by Durga), DIFFUSER (CAD files from Jason) geometry to gdml and store to DB (Ryan)
- STANDS - integrated legacy geometries, but positioning of TRACKERS, DIFFUSER, and ABSORBERS still needed
- ACTION: Integrate Absorber (MAUS Modules) by Pavel in new geometry and store to DB (Ryan)
- NEW
- ACTION: FIX tracker GDML files - problem in translation to MAUS Modules (Ryan and Chris H.)
- STANDS
- ACTION: Improving TRACKER Geometry description - fibres outside fiducial region (Heidt)
- STANDS
- ACTION: GEANT4 warning messages when geometry from CAD import is used (Ryan)
- DONE - removed from upgrade to g4.9.5
- ACTION: Produce geometry documentation for code developers and pass information to Ryan (Matt)
- REJECTED - Matt has long since left
- ACTION: Victoria Blackmore to implement magnet field map interface (Victoria)
- STANDS
Updated by Rogers, Chris over 10 years ago ยท 5 revisions