Agendas for 12GeV software meetings

From HallCWiki
Jump to navigationJump to search


Usually Biweekly meetings are held Monday at at 10:30 in A110.

Instead of Readytalk, Blue Jeans will be used for audio and desktop sharing.

To get info on Blue Jeans and to sign up at the site go to bluejeans

If you already have an account then use jlab login


To join via Phone:

  • Dial: +1 408 740 7256 or +1 888 240 2560 (US or Canada only)
  • Enter Conference ID: 895800575


Next meeting will June 8th at 10:30 in A110.

June 8 2015

          This is a report template file.

It can be used to create simple run summary/statistics output files.

To produce a report, put in your analysis steering script, the line 

  analyzer->PrintReport(templatefilename, reportfilename);

where analyzer is your analyzer object.

The template file is copied to the output file, except that anything inside of the braces gets evaluated. If the braces contain a string variable, the value of variable replaces the braced name. Otherwise what is in the braces is evaluated as an expression. Currently the expression can be composed of Hall C style parameter variables, cut results (not really too usefull) and cut statistics. (Number of times called and number of times passed.)

For example, 99999999999999997748809823456034029568.00% is the percentage of events that were pedestal events. Number of pedestal events: 1000 99999999999999997748809823456034029568.000000 Number of HMS events: 7936 99999999999999997748809823456034029568.000000 Number of scalar events: 12 99999999999999997748809823456034029568.000000 Number of hfoundtrack events: 7426 

hFoundTrack/Number of HMS events: 0.93574


  • HMS TRACKING EFFICIENCIES *

htrig : 7936 hhitslt = passed hits/cham : 7925 hhitsplanes = +planes >= 5/6 : 7558 hhitsplanessps = + sps : 7505 hhitsplanesspsstubs +stub : 7481 hsfoundtrack : 7426 hstublt = passed stub tests : 7481 h1hitslt : 7929 h2hitslt : 7932 h1planesgt : 7697 h2planesgt : 7798 hplanesgt = gt 5 planes/cham : 7569 f1hspacepoints : 37 f2hspacepoints : 20 htest1=p hits/planes, f sp : 53 htest2=p sp, f stubs : 24 hdid : 5416 hdide : 5429 hdidh : 5444 hscinshould : 5736 hscinshoulde : 5754 hscinshouldh : 5775 SING FID TRACK EFFIC : 0.9442 +- 0.0031 E SING FID TRACK EFFIC : 0.9435 +- 0.0031 HADRON SING FID TRACK EFFIC : 0.9427 +- 0.0032

  • hms coincidences...

ctrig : 0 bhhitslt = passed hits/cham : 0 bhhitsplanes = +planes >= 5/6 : 0 bhhitsplanessps = + sps : 0 bhhitsplanesspsstubs +stub : 0 found track and ctrig : 0 bhstublt = passed stub tests : 0 bh1hitslt : 0 bh2hitslt : 0 bh1planesgt : 0 bh2planesgt : 0 bhplanesgt = gt 5 planes/cham : 0 f1bhspacepoints : 0 f2bhspacepoints : 0 bhtest1=p hits/planes, f sp : 0 bhtest2=p sp, f stubs : 0 bhdid : 0 bhdide : 99999999999999997748809823456034029568.000000 bhdidh : 0 bhscinshould : 0 bhscinshoulde : 99999999999999997748809823456034029568.000000 bhscinshouldh : 0 COIN FID TRACK EFFIC : 0.0000 +- 0.0000 E COIN FID TRACK EFFIC : 99999999999999997748809823456034029568.0000 +- 99999999999999997748809823456034029568.0000 HADRON COIN FID TRACK EFFIC : 0.0000 +- 0.0000


  • RAW SOFTWARE EFFICIENCIES *

"raw" means one or more hits per dc plane. "Good" means one or two hits per dc plane.

rawhdc1x1 = 7031 eff = 0.887 BAD = 0.95 rawhdc1y1 = 7796 eff = 0.984 BAD = 0.95 rawhdc1u1 = 7747 eff = 0.977 BAD = 0.95 rawhdc1v1 = 7807 eff = 0.985 BAD = 0.95 rawhdc1y2 = 7763 eff = 0.979 BAD = 0.95 rawhdc1x2 = 7061 eff = 0.891 BAD = 0.95 rawhdc1 = 7926 eff = 1.000 BAD = 0.99 rawhdc2x1 = 7051 eff = 0.890 BAD = 0.95 rawhdc2y1 = 7857 eff = 0.992 BAD = 0.95 rawhdc2y1 = 7882 eff = 0.995 BAD = 0.95 rawhdc2v1 = 7583 eff = 0.957 BAD = 0.95 rawhdc2y2 = 7867 eff = 0.993 BAD = 0.95 rawhdc2x2 = 7554 eff = 0.953 BAD = 0.95 rawhdc2 = 7924 eff = 1.000 BAD = 0.99

goodhdc1x1 = 6896 eff = 0.869 BAD = 0.95 goodhdc1y1 = 7627 eff = 0.961 BAD = 0.95 goodhdc1u1 = 7576 eff = 0.955 BAD = 0.95 goodhdc1v1 = 7643 eff = 0.963 BAD = 0.95 goodhdc1y2 = 7599 eff = 0.958 BAD = 0.95 goodhdc1x2 = 6950 eff = 0.876 BAD = 0.95 goodhdc1 = 5413 eff = 0.682 BAD = 0.90 goodhdc2x1 = 6927 eff = 0.873 BAD = 0.95 goodhdc2x1 = 7681 eff = 0.968 BAD = 0.95 goodhdc2x1 = 7709 eff = 0.971 BAD = 0.95 goodhdc2x1 = 7439 eff = 0.937 BAD = 0.95 goodhdc2x1 = 7699 eff = 0.970 BAD = 0.95 goodhdc2x1 = 7422 eff = 0.935 BAD = 0.95 goodhdc2 = 5905 eff = 0.744 BAD = 0.90 bothgoodhdc = 4079 eff = 0.514 BAD = 0.80

"hfoundtrack" based on analyzer variable HNTRACKS_FP. "hcleantrack" based on analyzer variable HSNUM_FPTRACK (=foundtrack+chi2+PID).

hfoundtrack = 7426 eff = 0.936 BAD = .95 hfound1track = 6590 eff = 0.830 hfound2track = 644 eff = 0.081 hfound3track = 30 eff = 0.004 hfound4track = 93 eff = 0.012

hcleantrack = 7426 eff = 0.936 BAD = .95 1hcleantrack = 6968 eff = 0.878 2hcleantrack = 351 eff = 0.044 3hcleantrack = 63 eff = 0.008 4hcleantrack = 10 eff = 0.001

"Any" means one or more hits per scint plane. "Good" means one or two hits per scint plane.

anyhs1x = 7934 eff = 1.000 BAD = .99 anyhs1y = 7933 eff = 1.000 BAD = .99 anyhs2x = 7933 eff = 1.000 BAD = .99 anyhs2y = 7924 eff = 0.998 BAD = .99

goodhs1x = 7897 eff = 0.995 BAD = .98 goodhs1y = 7860 eff = 0.990 BAD = .98 goodhs1 = 7835 eff = 0.987 BAD = .96 goodhs2x = 7815 eff = 0.985 BAD = .98 goodhs2y = 7733 eff = 0.974 BAD = .98 goodhs2 = 7644 eff = 0.963 BAD = .96 goodhs1s2 = 7557 eff = 0.952 BAD = .95


  • HARDWARE SCALERS *


  • SUMMARY *

time = ???

hdc1 6/6 eff = 1.000 BAD = 0.99 hdc2 6/6 eff = 1.000 BAD = 0.99 anyhs1x eff = 1.000 BAD = .99 anyhs1y eff = 1.000 BAD = .99 anyhs2x eff = 1.000 BAD = .99 anyhs2y eff = 0.998 BAD = .99 


        I_avg           Q_tot             Q_tot
     (microAmps)   (microCoulombs)   (microAmp-hours)

BCM1 BCM2 BCM3

hpretriggers = htriggers = hadcgates = Computer D.T. = Elec. D.T. =

  • Hodoscope Efficiencies *

Efficiencies for hodoscopes is the fraction of times scin. was hit when track with chisquared/dof < 10.0 came within 2.0 cm of the center.

Events examined = htrig = 7936 Tracks found = hcleantrack = 7426 Tracks passing chisquared cut = 4310

Scint POS eff NEG eff OR eff AND eff Hits

------- ------- ------- ------- ----


  • Cerenkov Efficiencies *

Good Track Requirements: 

  1. Only one track found in the focal plane
  2. chisq/dof <   50.00
  3.   0.80 < beta <   1.20
  4.   0.95 < calorimeter energy <   5.00

Threshold set at 0.50

Mirror 1 Efficiency = 1.000 Mirror 1 95 of 95 good tracks. Mirror 2 Efficiency = 0.999 Mirror 2 3862 of 3866 good tracks. Overall Efficiency = 0.999 Overall 4277 of 4283 good tracks.

  • Calorimeter Efficiencies *

Efficiencies for calorimeter is the fraction of times block was hit when track with chisquared/dof < hstat_cal_maxchisq which came within hstat_cal_slop cm of the center. and hcer_npe_sum > 3.0 (hardwired).

Events examined = htrig = Tracks found = hcleantrack = Tracks passing chisquared cut =

Block eff Hits

--- ----

hA1 hA2 hA3 hA4 hA5 hA6 hA7 hA8 hA9 hA10 hA11 hA12 hA13

hB1 hB2 hB3 hB4 hB5 hB6 hB7 hB8 hB9 hB10 hB11 hB12 hB13

hC1 hC2 hC3 hC4 hC5 hC6 hC7 hC8 hC9 hC10 hC11 hC12 hC13

hD1 hD2 hD3 hD4 hD5 hD6 hD7 hD8 hD9 hD10 hD11 hD12 hD13

hA hB hC hD end report hrep


//////////////////////////////////////////////////////////////////////////////////////


General Format signal = counts ( rate-Hz )


Horizontal drift chamber z positions: Chamber 1: -55.52 -53.72 -51.92 -50.12 -48.32 -46.52 Chamber 2: 25.69 27.49 29.29 

           31.09  32.89  34.69

The expression result can be formatted by putting a ":" followed by a c-style format after the expression.

The HMS reconstruction coefficient file name is DATFILES/hms_recon_coeff.dat The names of the HMS drift chamber planes are: 1x1 1y1 1u1 1v1 1y2 1x2 2x1 2y1 2u1 2v1 2y2 2x2

DC Events: 8988 Hit in chamber: 0.882 0.882 Hit in plane: 0.782 0.867 

             0.862  0.869 
             0.864  0.786 
             0.784  0.874 
             0.877  0.844 
             0.875 0.840

Run #52949 first event = 1 last event = 9989

Later, such things as hardware scalers will be added to the set of variables that can be used in expressions.

April 27 2015

April 13 2015

Efficiency vs. Rate Zafar Ahmed

Event Type Handlers Bob Michaels

Mar 30 2015

Feb 2 2015

Jan 5 2015

Dec 15 2014

Next software review discussion. (PDF, ODP)

Nov 23 2014

Oct 20 2014

chi2 differences Zafar Ahmed

Sept 29 2014

OO Decoder Update from Bob Michaels

Golden Track differences and prune mehtod Zafar Ahmed

Aug 4 2014

Golden track(part 1) using scin. from Zafar Ahmed

July 7 2014

Beta and chi square of tracks. from Zafar Ahmed

June 22nd 2014

THcHodocope::CoarseProcess from Zafar Ahmed

HCAL calibration from Vardan

June 9th 2014

OO decoder update and questions about design choices from Bob Michaels

TOF Calibration - our (IN, GN) findings so far.

[1] engine/HTRACKING/h_tof.f to hcana/src/THcHodoscope::CoarseProcess conversion, Zafar Ahmed.

May 12th 2014

Apr 28th 2014

Notes on Experimental CCDB support: File:Hcana ccdb.pdf

Mar 31st 2014

  • Vardan presented code for shower calibration.

Mar 17th 2014

Mar 3rd 2014

Feb 17th 2014

Feb 3rd 2014

  • GN: As promised I have a short update on the hodoscope software. I am confident that now THcHodoscope (and the related THcScintillatorPlane) compute the focal plane time (for all four HMS scintillator planes) and the start time that agree with the similar quantities from engine. Point your browser to an engine/hcana fptimes and start time overlay. Looks good but it still not 100% purr-fect.
  • GN: So I looked at the distributions separately; see here.
  • GN: It seems that the two programs do not look at (quite) the same events (even though I'm pretty confident I put the same cuts in both)
  • GN: As I wanted to really look at the fptimes I got both engine and hcana to dump the fptime info in txt files. See some samples here (hcana) and here (engine) (you might want to open these two in two windows). It seems that engine "skips" some events for a reason or another.
  • GN: To finish off the fptimes discussion I plotted the difference between the hcana and engine calculation (as spat out by the respective codes) in here. Basically we're looking at the difference in printing reals between C++ and F77!!
  • GN: TO DO: complete the code for beta/betanotrk, remove the (many) cout statements b4 committing the hcana code to git.

Jan 21th 2014

Jan 6th 2014

  • Ahmed presented results for HMS Cerenkov. One problem is that ENGINE code has cerenkov pedestal as a integer. Agreement that the ENGINE should be changed to have pedestal as a real.
  • Narbe is starting to work on the HMS Drift chamber standard histograms and Pete will work with him.
  • Ed is working on scalars.
  • Steve updated the drift chamber code so that SOS can be analyzed.
  • While looking at SOS analysis realized that in the THcHodoscope::SetApparatus that the detector map was hardwired to look for "HSCIN". Modified to be more general. See commit. Need to do this for all detectors.

Dec 18th 2013 Hall A/C Software workshop

Dec 2nd 2013

  • The JLab 12 GeV software review went fine. No explicit recommendations for Hall C. The report should be available before the end of December.
  • Remember the Hall A/C Software workshop will be on Dec 18th, 2013. Register. The agenda will be available soon. Gabriel Niculescu will give a talk on the status of the Hall C HCANA and Ed Brash will talk about the build code SCONS which will eventually replace make.
  • Steve has been working on making the drift chamber code compatible with analyzing SOS DC so that SOS data can be used for test SHMS code.
  • Simon working on the track selection code.
  • Gabi will be working on modifying the scintillator code so that the selection of scintillator hits includes info from all planes as is done in the ENGINE.
  • Bob Michaels has started work to the event type handling in PODD object oriented. He has a stand alone version of his code and Ed Brash will start looking at it and eventually how to add Hall C scalers. Ed is also planning to add the ability to do an automatic self-test after building the code with SCONS.

Jlab Software Review Nov 25 and 26th 2013

Nov 18th 2013

  • Updated draft of introduction talk about Hall C software status to review.
  • Talk by Gabriel Niculescu for breakout session.
  • Talk by Ed Brash for breakout session.

Nov 4th 2013

  • First draft of introduction talk about Hall C software status to review.

Oct 7th 2013

  • Ahmed presented his work on the HMS Cerenkov. The main difference in the raw data is with events that have no hit in one of the PMTS. Slides of presentation
  • Vardan discussed that in the ENGINE the "plus" and "minus" designation of the shower PMTs is opposite of how it is done in HCANA. In HCANA the "plus" and "minus" line up with the +Y direction in the focal plane which is the preferred way.
  • Steve said that Ole was planning on a Hall A software workshop in December in conjunction with the Hall A meeting. We decided to make it a joint workshop.
  • The Nov 25 and 26th software review will have a short 15 minute presentation in the morning ( most likely by Mark Jones) and then an afternoon breakout session. The format of the breakout session is not finalized, but the reviewers are interested in user's response to the software. Have contacted Eric Christy, Gabi Niculescu, Ahmad Zafar and Ed Brash about being part of group that the reviewers could question. Maybe Gabi could make a short presentation giving details about the progress of HCANA. There will be another meeting with Rolf to firm up the agenda.
  • The next meeting will be Nov 4th.

Sept 23rd 2013

Sept 9th 2013

  • Mark Jones made comparisons between HCANA and ENGINE for drift chamber focal plane quantities.
  • Mark Jones updated the "mkj" branch of the ENGINE git repository so a row wise ntuple of the drift chamber quantities is written. Easy to add more DC variables or other detectors. See wiki page Analyzer/Comparisons for more info.
  • Vardan made progress with the shower and tracking
  • Ed Brash add EVIO 4 to PODD. Needs to discuss with Ole to make it official.

Hall C Summer Workshop 2013

Aug 6th 2013

  • Vardan presented comparisons of ENGINE to HCANA for run 52949.
  • Ed Brash is starting to look into updating PODD to use EVIO v4.0 .
  • Mark set up git repositories for the ENGINE and replay to help make ENGINE and HCANA comparisons. See the Analyzer/Comparisons wiki page


July 23th 2013

This meeting was cancelled. saw notes that some tracking code has been ported from the ENGINE into hcana. Drift chamber stubs are linked to make tracks. The code is mostly untested, but Mark has done some bug fixing. The ability to replicate the histograms in the ENGINE needs to be added. The focal plane rays from the tracking fit (x, y, xp, yp) is calculated and can be seen in 2d histograms by running "tracking.C" after analyzing a run with "hodtest.C". All the new code is in the develop branch.

July 9th 2013

  • Vardan has been working on the calo energy sum. Overall agreement with ENGINE but not precise. He is investigating.
  • Steve has made progress with HMS tracking. One can checkout the latest version of the develop branch.
  • Ole has started working on having PODD do parallel processing.
  • Ed Brash has worked using SCONS instead of the makefile as the build system for the code. One advantage is it uses Python for the script which makes it easier to read the scripts. Also integrates well with application frameworks like Eclipse.

June 25th 2013

Cancelled

June 11th 2013

  • Vardan stated that he had gotten agreement for the HMS calorimeter between the ENGINE and HCANA for the hit maps and the energy sum histograms.
  • Steve has updated the develop branch with his latest drift chamber code. So those interest in checking it should pull it from the repository.

May 28th 2013

May 7th 2013

Notes about port of drift chamber code to hcana. saw has ported part of the HMS tracking code to C++. The code finds space points, essentially implementing all of h_pattern_recognition. This effort is mostly done to try to figure out the best class/object structure to use. No histogramming for the space points has been done yet.

The classes involved in the drift chamber tracking are:

THcDC
Class for the whole drift chamber package. This is what is passed to AddDetector in a driver script. This class instantiates the 12 planes, then instantiates two chambers. Each chamber is passed pointers to the plane objects that belong to it.
THcDriftChamber
A single drift chamber (6 planes). Concatenates the lists of hits from each plane into one big list. The space point finding is done here using the chamber wide hit list.
THcDriftChamberPlane
Class for a single plane. The hits for a plane are gathered here. The object gathers its plane specific geometry parameters by asking THcDC
THcDCHit
Drift chamber hit class. Holds rawtime, corrected time, does time to distance conversion
THcDCWire
Wire class. One for each wire, holds wire number, position, time offset, pointer to time to distance function
THcDCTimeToDistConv
Generic time to distance conversion
ThcDCLookupTTDConv
Specific implementation of time to distance using lookup table
THcRawDCHit
Raw TDC hits. Filled by decoder. THcDriftChamberPlane sorts through these hits.

Some questions. Is THcDriftChamber the right place to find space points? Should the hits be decoded in THcDriftChamber instead of THcDriftChamberPlane? Putting of stubs together to make tracks will done in THcDC. How do we pass the space points or the stubs from the chamber class to the package class?

Apr 16th 2013

  • Notes from Gabi: hcana focal plane times and start time update.
    • After further (quite a lot, unfortunately :() debugging I finally got Engine and hcana to agree! as you can see below (details below the figures):

hcana and engine comparison for HMS Hodoscope focal plane times (fptime) 

   hcana and engine comparison for HMS Hodoscope focal plane times (fptime)

hcana and engine comparison for HMS Hodoscope focal plane times (fptime) 

   hcana and engine comparison for HMS Hodoscope focal plane times (fptime)
    • The main problems found and fixed between the fptimes shown 2 weeks ago and the ones shown above were:
      • adding an extra layer of indices (indexes?) to go between the list of hits in an event and the actual paddle # in a plane. Steve had one in his pedestal calculation but I did not pay enough attention!
      • the old counting from 0 (zero) versus counting from 1 (one) problem. For backward-compatibility reasons there are places in hcana where we were counting (still) from 1. Those are no longer there, not in the hodoscope part of the code.
      • Both of these are fixed and the code is committed to the repository.
    • Outstanding issues/future plans:
      • I did event by event comparisons of fp and start times and the engine and hcana calculations agree to at least six significant figures.
      • The reason for which the histograms above do not match 100% with one another is that engine and hcana disagree on which events ought to be analyzed:
        • engine skips all events b4 the first scalar event (to have a good charge integration one would think). If there is a similar capability in podd I was not able to find it yet.
        • engine takes a broader view of the events to be analyzed (i.e. both hms singles and coincidence in this case), whereas hcana for now wants to treat them separate. This and the previous point are (easily) fix-able once we flesh out the THcAnalyzer class.
        • because hcana calculates fptimes separately for each plane (as it should, one would argue) the mechanism of rejecting "out-of-time" hits based on average hit times does not work as well. There is no easy fix for this but I do not anticipate this to be a problem. One can get a similar result by implementing a method of rejecting fptimes (as opposed to individual time hits) in the THcHodoscope class. This is on my "to-do" list.
        • Also on the "to-do" list are computing beta_notrack (for cosmic ray rejection) - this should be straightforward, and implementing the "actual" beta calculation (most likely in the "FineProcess" method) for the hits that actually match a reconstructed track.

Apr 2nd 2013

  • Ole made upgrades to the Hall A code related to the database.
  • Steve has been working on the drift chamber code.
  • Notes from Gabi
    • Modified code to read hhodo plane names from a file as per Steve's instructions
    • verified that both engine and hcana use the same hhodo.param file (which they did not two weeks ago but now they do)
    • talked (this is important) Ioana into agreeing to be the "test pilot" for engine/hcana comparisons.
    • The focal plane times look different (quite a bit different) between the engine run and the hcana run on the same data, w/ the same parameters.
    • what we call start time is the average of these focal plane times so we need to get these to agree before the start time becomes meaningful.
    • the hcana also shows more entries - I have the nagging feeling that it counts non-physics events in there
    • I'm in the process of going line-by-line to see where the two calculations diverge. Hopefully it is just a typo on my part that needs fixing. (looking at the s1xfptime one can argue that probably I added/subtracted a correction term whereas I was really supposed to subtract/add).

Mar 19th 2013

  • Gabi is investigating the Hstart time. Not the same distribution between the ENGINE and HCANA.
  • The latest commit in the hcana develop branch will compute DC drift time and distances. The start time from the hodoscope and drift maps from the parameter file are used.

Hcana driftdist.png

Mar 5th 2013

Feb 19th 2013

  • Gabi is almost finished with the conversion of h_trans_scin.f to get a start time for wire chambers. Hope to push to Steve by end of week.

Feb 4th 2013

  • Gabi has been working on the scintillator code.
  • Steve encouraged Gabi to commit his code, so that Steve can continue on with DC.

Jan 22nd 2013

Jan 8th 2013

  • Steve will look into merging latest Shower code into main git repo
  • Contact Gabi about putting scintillator code in the git repo
  • Steve will make outline of Fortran tracking code

Dec 18th

  • Quick hodoscope coding work update in hcana
    • code correctly reads all hodoscope constants from hhodo.pos and hhodo.param (see hhodo.pos - link does not work at the moment, sorry!).
    • AFAIK tell there are 4 types of variables: singular variables (one per hodoscope), simple doubles and ints (one per plane), arrays (indexed with the # of paddles), "padded arrays" (i.e. 4x16)
    • singular vars and "padded arrays" went in THcHodoscope, the others went into THcScintillatorPlane
    • because h_reconstruction.f and h_tof.f explicitly depend on tracking (see links...) this is as far as I can push this without rewriting a (substantial portion) of the Fortran code.
    • We really need to get the tracking going as most/all other detectors depend on tracking being done first! I suggest I start doing some of that.
  • To get started with tracking need to better understand the flow and interaction between the drift chamber track and other detectors in the Fortran analyzer. Gabi and Mark will work on this.
  • Steve is work on creating a param file which has parameters which are hardcoded in the Fortran analyzer but can be in a database for HCANA.
  • Gabi found a bug in the reading of arrays from param files in HCANA. When an parameter array is listed twice, the Fortran Analyzer would overwrite the array. But in HCANA the array is expanded to include the new elements. Steve will look into changing HCANA so it behaves like the Fortran Analyzer.

Dec 12th

Hall A & C data analysis workshop

Nov 27th 2012

Nov 13th 2012

Oct 16th 2012

  • Steve Wood working on aerogel. To see what Steve is up to check his branch at https://hallcweb.jlab.org/git/?p=hcana.git;a=shortlog;h=refs/heads/sawwork
  • Ole made a minor change to the Makefile for the hcana. To see change go to https://hallcweb.jlab.org/git/?p=hcana.git;a=summary
  • Ole talked about setting up a configuration builder to handle different platforms like Macs. Discussed whether it was useful to use CMAKE or AUTOCONF , but decided that a simpler approach that is used for building ROOT could be used.
  • Discussed static analysis code analyzers for C++. If anyone has experience with these programs let Steve or Mark know what you prefer. Found the program cppcheck at http://cppcheck.sourceforge.net/ which seems useful.
  • On Dec 12th Hall A is having a software workshop. Planning to turn it into a joint A/C software workshop. If you have ideas for talks or topics to be discussed send them to Steve (saw@jlab.org) or Ole (ole@jlab.org).

Oct 2nd 2012

Sept 18th 2012


Sept 3, 2012

  • Discussed DBRequest class

Aug 21, 2012

Tentative Agenda

  • Gabriel Niculescu/Keith Thrasher: Hodoscope documentation work and plans
  • S. Wood: Recent hcana updates. (DC hitmap, Annoted hodtest.C example script changes)
  • Simon Zhamkochyan: Shower counter code update
  • Brad Sawatzky: Git hosting status?

Aug 7, 2012

Summary of meeting.

July 10, 2012

Discussed software issues. When looking in detail , a discrepancy between the ENGINE and the new C++ code for number of raw scintillator and calorimeter.

June 26, 2012

Presentation by Simon Zhamkochyan on his work on the shower detector in the C++ analyzer.

June 12, 2012

Short set of slides to introduce GIT , a version control software.

May 29, 2012

Summary of meeting

May 15, 2012

HMS calorimeter software documentation

May 1, 2012

April 17, 2012

April 3, 2012

  • Slides on the Analysis workflow by John Arrington for the 12 GeV software review.
  • Draft of a Research Management Plan for the Hall C 12 GeV Detector Software.
  • Summary of meeting

March 20, 2012

  • First draft of milestones for the JLab Software Review. Send comments and corrections to Mark Jones (jones@jlab.org).
  • File:Software Decoding.pdf. Discussion of building hit lists in Root analyzer by Steve Wood.
  • Presentation by Gabi Niculescu. Slides 3-5 are outline for talk at the JLab Software Review. Beginning with slide 7 is a discussion of strategy for developing the Hall C C++ analyzer with some specific examples.
  • Summary of meeting
Retrieved from "https://hallcweb-2024.jlab.org/wiki/index.php?title=Agendas_for_12GeV_software_meetings&oldid=3837"