View source for Agendas for 12GeV software meetings

__FORCETOC__
[[category:12GeV Software]]
Call in using phone number 866-740-1260 with code 1150811. 

Login into www.readytalk.com to view presentations.

Meet biweekly every Tues at 1pm in B101.

Next meeting Apr 16th

== Apr 16th 2013 ==
*Notes from <i>Gabi</i>: hcana focal plane times and start time update.
** After further (quite a lot, unfortunately :() debugging I finally got <b>Engine</b> and <b>hcana</b> to <b>agree!</b> as you can see below (details below the figures):
[[Image:hodtest_hcana1.gif || hcana and engine comparison for HMS Hodoscope focal plane times (fptime)]]

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

[[Image:hodtest_hcana2_1.gif || 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 <b>0 (zero)</b> versus counting from <b>1 (one)</b> 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 <b>engine</b> and <b>hcana</b> calculations agree to at least six significant figures.
*** The reason for which the histograms above do not match 100% with one another is that <b>engine</b> and <b>hcana</b> 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 <b>"to-do"</b> list.
**** Also on the <b>"to-do"</b> list are computing <b>beta_notrack</b> (for cosmic ray rejection) - this should be straightforward, and implementing the <b>"actual" beta</b> 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. 
***[https://hallcweb.jlab.org/wiki/images/5/56/Hhodo_test_hcana.pdf  Focal plane times from HCANA]
***[https://hallcweb.jlab.org/wiki/images/8/83/Hhodo_test_engine.pdf Focal plane times from ENGINE]
**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.
[[Image:hcana_driftdist.png|200px]]

== 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 [http://csma31.csm.jmu.edu/physics/Niculegx/HallC++/hhodo.pos 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 ==
[http://hallaweb.jlab.org/data_reduc/AnaWork2012/ 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 ==
*[https://mailman.jlab.org/pipermail/hallcsw/2012-October/000047.html Summary] of the meeting.

== Sept 18th 2012 ==
*  [https://hallcweb.jlab.org/wiki/images/1/1d/JLab12GeVSoftwareComputingReviewFinal20120912.pdf Final report] of the 12 GeV Software review.


== 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 ==
[https://mailman.jlab.org/pipermail/hallcsw/2012-August/000038.html 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 ==
[https://hallcweb.jlab.org/wiki/images/e/ee/Shower_in_Hall_C%2B%2B_Analyzer.pdf Presentation] by Simon Zhamkochyan on his work on the shower detector in the C++ analyzer.
== June 12, 2012 ==
Short set of [https://userweb.jlab.org/~jones/shms/GIT.pptx slides] to introduce GIT , a version control software.

== May 29, 2012 ==
[https://mailman.jlab.org/pipermail/hallcsw/2012-June/000031.html Summary] of meeting

== May 15, 2012 ==
[https://hallcweb.jlab.org/wiki/index.php/Image:Hms_lg.pdf HMS calorimeter] software documentation

== May 1, 2012 ==
*[https://mailman.jlab.org/pipermail/hallcsw/2012-May/000027.html Summary] of meeting

== April 17, 2012 ==
* [[Image:Hms_calo_coding.pdf]] Vardan Tadevosyan's overview of HMS calorimeter software documentation.

== April 3, 2012 ==
*[https://hallcweb.jlab.org/wiki/images/7/71/SHMS_software_ja.pdf Slides] on the Analysis workflow by John Arrington for the 12 GeV software review.
*[https://hallcweb.jlab.org/wiki/images/1/12/RMP_HallC_software.pdf Draft] of a Research Management Plan for the Hall C 12 GeV Detector Software.
*[https://mailman.jlab.org/pipermail/hallcsw/2012-April/000021.html Summary] of meeting

== March 20, 2012 ==
* First draft of [https://hallcweb.jlab.org/wiki/images/b/b1/Software_milestones.pdf milestones] for the JLab Software Review. Send comments and corrections to Mark Jones (jones@jlab.org).
* [[Image:Software_Decoding.pdf]].  Discussion of building hit lists in Root analyzer by Steve Wood.
*[https://hallcweb.jlab.org/wiki/images/1/1b/Gn_hallc_software_03_20_2012.pdf 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.
* [https://mailman.jlab.org/pipermail/hallcsw/2012-March/000019.html Summary ] of meeting