Difference between revisions of "Thursday, November 10, 4:00pm ETD"

From Hall A Wiki
Jump to: navigation, search
(New page: == Agenda == Presentations:<br><br> * Should we stop dividing our efforts between GEMC and mollersim? ** Are we ready to choose one, and if so, which? ** [https://userweb.jlab.org/~crowder...)
 
(Agenda)
 
(9 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
== Agenda ==
 
== Agenda ==
 
Presentations:<br><br>
 
Presentations:<br><br>
* Should we stop dividing our efforts between GEMC and mollersim?
+
* Updates to mollersim geometry (Juliette)
** Are we ready to choose one, and if so, which?
+
** rotated the phi-defining collimator so that there is a closed section to beam left
** [https://userweb.jlab.org/~crowder/moller_stuff/MOLLERSimMeeting_2011Mar24(1)-1.pdf Dustin's talk]
+
** modified field determination code to be somewhat general - can rotate the field easily now
 +
** coded the upstream torus in GDML (see [http://ace.phys.virginia.edu/MollerSpectrometer/202 elog 202])
 +
*** plan to also hard-code to maintain the ability to continue to use it - but I REALLY like the GDML
 +
*** will compare the results for hard-coded vs. GDML defined
 +
*** the GDML write from GEANT4 did NOT create tesselated volumes, but the parameterization is lost
 +
*** if we code directly in GDML it is really easy to parameterize things AND to modularize things (see [http://ace.phys.virginia.edu/MollerSpectrometer/205 elog 205])
 +
* Changing code to write volume numbers of sensitive volumes to root file - need a better way of identifying them?
 +
**    0-999 for actual detectors (possibly 0-99 for plane detectors and 100-999 for pieces quartz?, tracking?)
 +
** 1000-1999 for collimators
 +
** 2000-???? for coils
 +
*Incidentally, no luck with GEANT4 with GDML on windows - Mauri is working on a Fedora 15 package and I now have a Fedora 15 virtual machine
 
<br>
 
<br>
{| class="wikitable" style="text-align: left; width: 50%; height: 100px;"
 
|-
 
! scope="col" | Feature
 
! scope="col" | GEMC
 
! scope="col" | mollersim
 
|-
 
| nice GUI
 
| yes
 
| not yet
 
|-
 
| nice visualization (Qt)
 
| yes
 
| yes
 
|-
 
| geometry <br>(w/o recompile)
 
| yes - mysql DB, filled by PERL scripts
 
| yes, messengers or GDML
 
|-
 
| detector response
 
| yes
 
| want to customize?
 
|-
 
| ROOT output
 
| translate EVIO output, you have to write the bank configuration
 
| yes
 
|-
 
| ease of installation <br>(on jlab systems)
 
| RPM available, OSX available? DEB in the works
 
| not yet - necessary? possible?
 
|-
 
| maintenance
 
| wider range of users to test (find bugs, etc.)
 
| only collaboration using
 
|-
 
| control
 
| not really - have to coordinate with Mauri for changes, etc.
 
| yes
 
|}
 
 
<br><br>
 
 
 
* Collimator/field configuration comparison update (Sereres)
 
* Collimator/field configuration comparison update (Sereres)
* GEANT4 on windows (Juliette)
+
**[http://ace.phys.virginia.edu/MollerSpectrometer/208 Plots of asymmetries]
** works with OpenGL and HepRep Viewers
+
**[http://ace.phys.virginia.edu/MollerSpectrometer/206 target study]
** have installed Qt, Xerces, and ROOT -> need to set environment to run mollersim
+
**[http://ace.phys.virginia.edu/MollerSpectrometer/207 comparing moller, ep, inelastics]
* Qweak GEANT4 development/use is ramping up again (Wouter)
+
* Other items
+
** Meetings? 
+
*** Thursday at 2pm or 4pm depending on Qweak meeting time, in F224/225
+
*** no"major" simulation meeting (teleconference)
+
*** collaboration meeting in January
+
** [https://hallaweb.jlab.org/wiki/index.php/MOLLER_Simulations Other projects]
+
  
 
== Minutes ==
 
== Minutes ==

Latest revision as of 17:06, 10 November 2011

Agenda

Presentations:

  • Updates to mollersim geometry (Juliette)
    • rotated the phi-defining collimator so that there is a closed section to beam left
    • modified field determination code to be somewhat general - can rotate the field easily now
    • coded the upstream torus in GDML (see elog 202)
      • plan to also hard-code to maintain the ability to continue to use it - but I REALLY like the GDML
      • will compare the results for hard-coded vs. GDML defined
      • the GDML write from GEANT4 did NOT create tesselated volumes, but the parameterization is lost
      • if we code directly in GDML it is really easy to parameterize things AND to modularize things (see elog 205)
  • Changing code to write volume numbers of sensitive volumes to root file - need a better way of identifying them?
    • 0-999 for actual detectors (possibly 0-99 for plane detectors and 100-999 for pieces quartz?, tracking?)
    • 1000-1999 for collimators
    • 2000-???? for coils
  • Incidentally, no luck with GEANT4 with GDML on windows - Mauri is working on a Fedora 15 package and I now have a Fedora 15 virtual machine


Minutes



Return to Teleconferences
Return to MOLLER at 11 GeV E09-005