Difference between revisions of "Simulation Meeting February 28 2019 10AM ET"
From Moller Wiki
Line 18: | Line 18: | ||
==Attendance:== | ==Attendance:== | ||
− | Attendance: | + | Attendance: Rakitha, Ciprian, Sakib, Juliette, Dustin, Cameron, Chandan, Wouter, Kent |
==Minutes== | ==Minutes== | ||
− | * | + | * Making GDML implementation guideline by Ciprian |
+ | ** Using nested volumes for regions and sub-regions | ||
+ | ** suggestions for variables and naming conventions. | ||
+ | ** Always run dos2unix on your files before committing a new file if you are on a windows OS | ||
+ | ** If you use tabs convert tabs to spaces in your editor | ||
+ | ** Use G4 materials as the first choice using G4_materialname | ||
+ | ** Use keep-out regions for each subvolume | ||
+ | ** Ciprian and Juliette implementing the beam pipe. The discussion is how to implement separately in different sub-regions. The hybrid area vacuum or He needs to finalized that way we may be able to use single sub volume for the beam pipe. | ||
+ | ** There is no beam pipe going through two magnets due to the vacuum within the magnets. | ||
+ | ** Create a directory for each daughter region and keep GDML files only in that region on the directory. | ||
+ | * Updates on Simulation development in general | ||
+ | ** Beam pipe implementation is in accordance to GMDL guideline we agreed - Ciprian | ||
+ | ** Shielding implementation is in accordance to GMDL guideline we agreed - Rakitha | ||
+ | ** Master and develop branches should work by simply checking out from GIT. New versions for master will be released every 3 months. Develop will have new features but not agreed on final versions so it may have some issues. The master branch is the working version for anyone to use. | ||
+ | ** Working on geometry development branch where geometry is tracked independently but we are not there yet. | ||
+ | ** Even with geometry is tracked independently master branch will have it's own releaser of geometry tagged to it. | ||
+ | ** GIT tracking for geometry and code updates | ||
+ | ** use the wiki page for general information on each sub systems and who is in charge, and where to find further information | ||
+ | |||
+ | |||
<br><br> Return to [[Simulation_Meetings | Simulation Meetings]] | <br><br> Return to [[Simulation_Meetings | Simulation Meetings]] | ||
<br> Return to [[Main_Page|Main Page]] | <br> Return to [[Main_Page|Main Page]] |
Revision as of 16:26, 28 February 2019
Back to Main Page >> Simulation Meetings
previous meeting << >> following meeting
Contents
[hide]Task List Summary
- Simulation tasks Task List by Dustin
- Simulation tasks Task List by Rakitha
- Main detector simulation tasks Task List by Michael
Agenda
- remoll GDML implementation/standards: Ciprian docDB434 or
- Simulation software updates
- Radiation shielding update from meeting with JLab
Attendance:
Attendance: Rakitha, Ciprian, Sakib, Juliette, Dustin, Cameron, Chandan, Wouter, Kent
Minutes
- Making GDML implementation guideline by Ciprian
- Using nested volumes for regions and sub-regions
- suggestions for variables and naming conventions.
- Always run dos2unix on your files before committing a new file if you are on a windows OS
- If you use tabs convert tabs to spaces in your editor
- Use G4 materials as the first choice using G4_materialname
- Use keep-out regions for each subvolume
- Ciprian and Juliette implementing the beam pipe. The discussion is how to implement separately in different sub-regions. The hybrid area vacuum or He needs to finalized that way we may be able to use single sub volume for the beam pipe.
- There is no beam pipe going through two magnets due to the vacuum within the magnets.
- Create a directory for each daughter region and keep GDML files only in that region on the directory.
- Updates on Simulation development in general
- Beam pipe implementation is in accordance to GMDL guideline we agreed - Ciprian
- Shielding implementation is in accordance to GMDL guideline we agreed - Rakitha
- Master and develop branches should work by simply checking out from GIT. New versions for master will be released every 3 months. Develop will have new features but not agreed on final versions so it may have some issues. The master branch is the working version for anyone to use.
- Working on geometry development branch where geometry is tracked independently but we are not there yet.
- Even with geometry is tracked independently master branch will have it's own releaser of geometry tagged to it.
- GIT tracking for geometry and code updates
- use the wiki page for general information on each sub systems and who is in charge, and where to find further information
Return to Simulation Meetings
Return to Main Page