Project

General

Profile

Kaon LT Meetings » GitHub_mtg_24jan10.txt

Garth Huber, 01/12/2024 06:36 PM

 
1
                 Jan 10/24 PionLT/KaonLT GitHub Meeting Notes
2
                 --------------------------------------------
3
                              (Notes by GH)
4

    
5
This was a special meeting to discuss the future structure of the
6
hallc_replay_lt software
7

    
8
Present
9
-------
10
Regina - Garth Huber, Ali Usman, Alicia Postuma, Nacer Hamdi, Nathan Heinrich,
11
   Vijay Kumar  
12
CUA - Richard Trotta, Casey Morean
13
FIU - Pete Markowitz
14

    
15
Preliminary item
16
----------------
17
- Richard found that for some of the newer scripts, you wil have to specify a
18
  more recent python version, i.e. 3.3.5 vs 2.2.1
19

    
20
hallc_replay_lt discussion
21
--------------------------
22
a) UTIL_BATCH script should be updated
23
- used by both pi/K analyses
24
  - should segregate analysis scripts similar to how they are done in
25
    hallc_replay, don't want changes by one experiment to affect another
26
  - also, different channels in same experiment (e.g. pi/K/p in KaonLT) need
27
    different filenames, not just one set of scripts for KaonLT and another for
28
    PionLT
29

    
30
- Ali: suggest to segregate codes to make codes easier to follow/understand
31

    
32
- Nathan: Production branch is 544 commits ahead of Master.  It would be good
33
  to update Master, then it would be easier to do the segregation
34

    
35
- Casey: we want Master to be the branch we point people too when they are
36
  starting analysis
37

    
38
- *ACTION NEEDED*: sych fork on Master right now
39
  - everyone should push to Master and update it
40

    
41

    
42
b) what to do with defunct/archived code?
43
- some defunct branches should be archived
44

    
45
- Nathan: old snapshots correspond to various milestones
46
  - no need to delete them, not sure if they're working now, but they were working
47
    at the time the snapshots were made
48

    
49
- Casey: suggest to archive to Mass Storage System (MSS), as otherwise the
50
  utility of the old snapshots is lost
51

    
52
- Richard: it would be good to get all your scripts working in a container and
53
  save it.  That way all essential information is preserved.
54

    
55
- Casey: suggests naming according to Release Number, and adding tags on which
56
  version number of other software it relies on
57
 - concerned that certain branches will disappear with time and then this
58
   information will be lost
59

    
60
c) Documentation
61
- Nacer: need a message on top of every file on what inputs and outputs are,
62
  what it does
63
- Richard has a useful emacs script that automatically puts author and date at
64
  the top of every new file.  But the essential comment info is empty and needs
65
  to be filled in later.
66

    
67
Summary of Action Items
68
-----------------------
69
1) ltsep_analysis_2022 should be merged with Master and labeled with release
70
   tags
71

    
72
2) remove symlinks, some are left over from online analysis
73
  - getting rid of things that don't matter makes it easier for new people
74
  - archive old software
75

    
76
3) need to go through scripts, find what's used now, and make sure they work
77
  for everyone
78

    
79

    
80
Next Meeting
81
------------
82
- the one thing that was not discussed was a task list, timeline for
83
  accomplishing these tasks
84
- GH suggests another meeting in about a month, after Nathan and Alicia return
85
  from JLab on Feb 8
86

    
87

    
88

    
89

    
90

    
(359-359/443)