Difference between revisions of "July 1, 2009 Software"

From GlueXWiki
Jump to: navigation, search
(Minutes)
Line 44: Line 44:
 
==Removing 2-GB-file-size limit==
 
==Removing 2-GB-file-size limit==
  
David led us through his [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00922.html email message] describing the change to the make system to fix the limitation on HDGeant output file size. The change was done by adding the switch in one place in one file.
+
David led us through his [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00922.html email message] describing the change to the make system to fix the [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00918.html limitation on HDGeant output file size]. The change was done by adding the switch in one place in one file.
  
 +
==DRootGeom changes--multi-threading and ROOT==
 +
David showed some (link???) slides describing the problem and options for dealing with thread safety and the DRootGeom class. There are still some kinks to work out with the table method. More on this next meeting.
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00923.html DRootGeom changes--multi-threading and ROOT] ([[Media:20090701_material_map.pdf|Slides]]): David
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00923.html DRootGeom changes--multi-threading and ROOT] ([[Media:20090701_material_map.pdf|Slides]]): David
 +
 +
==Magnetic Field Documentation Webpage==
 +
 +
David led us through the issues documented on this page. He will note on the page the appropriate use of the -z0??? switch. (AA???)
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00926.html Magnetic Field Documentation Webpage]: David
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00926.html Magnetic Field Documentation Webpage]: David
 +
 +
==Proposed changes to mcsmear==
 +
 +
We discussed the issues raised in the recent email discussion about an intermediate stage between HDGeant and reconstruction that would add random detector effects and create appropriate HDDM output. Matt pointed out that the structure of the smeared hits is in some cases much different than the structure of the hits coming out of HDGeant. For example the BCAL hits have the energy deposited in a module as they come out of HDGeant, but not the detector response at each end. There is no place in the data model for this information at present.
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00925.html Proposed changes to mcsmear]: David
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00925.html Proposed changes to mcsmear]: David
# Group disk usage (work and cache for that matter): all
+
 
 +
==Hall D Unix groups==
 +
Elliott led us through his proposal for re-arranging our set of Unix groups at JLab. We agreed that he should go ahead and implement this with IT Division. Eugene noted that the newgrp command can be used to create a new shell with the default group of one's choice. Elliott also mentioned that the directory mode bits can be set to insure that all files created in that directory belong to same group.
 
# [[Hall D Unix groups discussion]]: Elliott
 
# [[Hall D Unix groups discussion]]: Elliott
 +
 +
==Tracking removed from HDGeant==
 +
 +
David led us through his email announcing this change. This means that we are now running with the straight-line approximation within a straw for calculating the drift distance in the CDC. This error is small compared with our position resolution.
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00927.html Tracking removed from HDGeant]: David
 
# [http://www.jlab.org/ccc/mail_archives/HALLD/halld-offline/msg00927.html Tracking removed from HDGeant]: David
 +
 +
==Action Item Review==
 +
 +
Sascha suggested that someone fix the (link???) not-a-number problem in the BCAL cluster code.
 +
 +
Mark will go through (list???) the list and mark done items as done. Next time we will discuss the (link???) task list.
 
# [[Action Items From Hall-D Software Meetings | Action item]] review
 
# [[Action Items From Hall-D Software Meetings | Action item]] review
 +
 +
==Item left for next time==
 +
# Group disk usage (work and cache for that matter): all
  
 
===notes===
 
===notes===
Line 62: Line 87:
 
calibration registration with source code
 
calibration registration with source code
 
   
 
   
david will take lead mcsmear  
+
david will take lead mcsmear
 
+
blake in cluster, negative
+

Revision as of 10:22, 2 July 2009

Location

The meeting will be at 2:00 pm in CEBAF Center F326/327.

Telephone

To connect by telephone:

  1. dial:
    • 800-377-8846 : US
    • 888-276-7715 : Canada
    • 302-709-8424 : International
  2. enter participant code: 39527048# (remember the "#")

Video Conferencing

A) ESNet: 8542553
B) EVO: meeting link

Agenda

  1. Review minutes from June 17, 2009 Software meeting
  2. Announcements
    • Anyone have any?
  3. Work disk: Mark
  4. Software tag policy--when to modify the tag: Mark
  5. Removing 2-GB-file-size limit (makefile changes): David
  6. DRootGeom changes--multi-threading and ROOT (Slides): David
  7. Magnetic Field Documentation Webpage: David
  8. Proposed changes to mcsmear: David
  9. Group disk usage (work and cache for that matter): all
  10. Hall D Unix groups discussion: Elliott
  11. Tracking removed from HDGeant: David
  12. Action item review

Minutes

Work disk

Mark shared what he has learned recently about the new work disk quota system at the Lab.

Software tag policy--when to modify the tag

Mark led the discussion. From time to time, we are tempted to modify a tagged release when a bug fix is found, post-tagging. What to do depends on balancing the desire to have a tag have a time-independent meaning and the desire to fix something that is broken when that fix requires only a very small change. So far we have left this to the judgment of the person maintaining the tag. There was a consensus on continuing with this practice.

Removing 2-GB-file-size limit

David led us through his email message describing the change to the make system to fix the limitation on HDGeant output file size. The change was done by adding the switch in one place in one file.

DRootGeom changes--multi-threading and ROOT

David showed some (link???) slides describing the problem and options for dealing with thread safety and the DRootGeom class. There are still some kinks to work out with the table method. More on this next meeting.

  1. DRootGeom changes--multi-threading and ROOT (Slides): David

Magnetic Field Documentation Webpage

David led us through the issues documented on this page. He will note on the page the appropriate use of the -z0??? switch. (AA???)

  1. Magnetic Field Documentation Webpage: David

Proposed changes to mcsmear

We discussed the issues raised in the recent email discussion about an intermediate stage between HDGeant and reconstruction that would add random detector effects and create appropriate HDDM output. Matt pointed out that the structure of the smeared hits is in some cases much different than the structure of the hits coming out of HDGeant. For example the BCAL hits have the energy deposited in a module as they come out of HDGeant, but not the detector response at each end. There is no place in the data model for this information at present.

  1. Proposed changes to mcsmear: David

Hall D Unix groups

Elliott led us through his proposal for re-arranging our set of Unix groups at JLab. We agreed that he should go ahead and implement this with IT Division. Eugene noted that the newgrp command can be used to create a new shell with the default group of one's choice. Elliott also mentioned that the directory mode bits can be set to insure that all files created in that directory belong to same group.

  1. Hall D Unix groups discussion: Elliott

Tracking removed from HDGeant

David led us through his email announcing this change. This means that we are now running with the straight-line approximation within a straw for calculating the drift distance in the CDC. This error is small compared with our position resolution.

  1. Tracking removed from HDGeant: David

Action Item Review

Sascha suggested that someone fix the (link???) not-a-number problem in the BCAL cluster code.

Mark will go through (list???) the list and mark done items as done. Next time we will discuss the (link???) task list.

  1. Action item review

Item left for next time

  1. Group disk usage (work and cache for that matter): all

notes

new hdparsim efficiencies with new releases recompile even if not changes drootgeom? dave will look at this

announcement: root offline howto serialize , future meeting item, elliott calibration registration with source code

david will take lead mcsmear