Project

General

Profile

What Lynn does » History » Version 44

Joe Boyd, 11/13/2019 04:57 PM

1 1 Lynn Garren
h1. What Lynn does
2 1 Lynn Garren
3 30 Lynn Garren
{{TOC}}
4 16 Lynn Garren
5 40 Joe Boyd
h2. Build "third party" ups products as needed for art and larsoft 
6 40 Joe Boyd
7 44 Joe Boyd
8 43 Joe Boyd
@For immediate term using old methods Chris Green will have to take care of this,  Jim A should be the one to tell these people this but in the future using SPACK here are some examples of people that could maybe take these pieces
9 40 Joe Boyd
10 40 Joe Boyd
  * ROOT: Philippe / Physics and Data Simulation.
11 40 Joe Boyd
  * GENIE: Robert Hatcher / Neutrino Simulation.
12 40 Joe Boyd
  * GEANT4: Krzysztof / Physics and Detector Simulation.
13 40 Joe Boyd
  * PostGresQL, Psycopg,  SQLite, MySQL, MariaDB: Scientific Database Applications.
14 40 Joe Boyd
  * nucondb, ifbeam, ifdhc, ifdh-art, etc. (and unique dependencies): Compute
15 40 Joe Boyd
    Services Tools.
16 1 Lynn Garren
  * PyTorch, libtorch, TensorFlow, Eigen, Caffe (legacy): Algorithms for
17 1 Lynn Garren
    Reconstruction and Analysis.@
18 42 Joe Boyd
19 7 Lynn Garren
* We have a [[build-framework:|defined procedure]] that uses a number of scriptlets found in the ssibuildshims product.
20 5 Lynn Garren
* Each product has a tiny redmine repository for the build and bootstrap scripts.
21 9 Lynn Garren
** Scripts include autobuild.sh, bootstrap.sh, build_xxx.sh, and usually ups/xxx.table, where xxx is the product name.
22 9 Lynn Garren
** We sometimes need patch files.
23 9 Lynn Garren
** Other scripts are occasionally included, such as bootstrap_datasets.sh for geant4.
24 10 Lynn Garren
** We tag these repositories with the product version.
25 5 Lynn Garren
* To ensure reproducible builds, we only build from tagged releases.  In rare cases, we use a commit hash.
26 1 Lynn Garren
* We require that the source code be captured in a source code tarball for reproducible builds.
27 6 Lynn Garren
* We bootstrap and run local test builds for the supported compiler options.  This is a rapid turnaround development step.
28 14 Lynn Garren
** Whenever possible, we run unit tests as part of the build procedure and require that these tests pass.
29 6 Lynn Garren
* Once everything looks good, the source code tarball is uploaded to SciSoft.
30 12 Lynn Garren
* Also provide help to people attempting to make their own ups products.
31 5 Lynn Garren
32 34 Joe Boyd
h2.  Build art releases after they are tagged. (SciSoft team would take this over)
33 1 Lynn Garren
34 1 Lynn Garren
* Kyle sends around an email to the SciSoft Team when a release is tagged.
35 1 Lynn Garren
* Update information in build-framework/CMakeLists.txt
36 1 Lynn Garren
** There are multiple branches for different product configurations
37 1 Lynn Garren
* Run cmake to get the new build configuration files.
38 1 Lynn Garren
* Check the new config files.
39 1 Lynn Garren
** Always compare against the previous release.
40 3 Lynn Garren
* If they are OK, use copyToSciSoft to install ONLY the appropriate build configuration files on SciSoft.  There are html files for each release that also need to be installed.
41 1 Lynn Garren
** canvas
42 1 Lynn Garren
** art
43 1 Lynn Garren
** gallery
44 1 Lynn Garren
** critic
45 1 Lynn Garren
* Start a Jenkins build
46 1 Lynn Garren
** https://buildmaster.fnal.gov/buildmaster/view/Art/job/critic-all/
47 1 Lynn Garren
** The build needs two iterations.  First for python 2 (the LABEL field is empty) and then a second pass with LABEL set to py3.
48 2 Lynn Garren
* Sometimes there are problems with the build.
49 2 Lynn Garren
** Investigate and fix.
50 2 Lynn Garren
** A local test build is sometimes helpful, depending on the problem.
51 2 Lynn Garren
* Once the build has completed successfully, download the tarballs locally and then upload them to SciSoft.
52 2 Lynn Garren
** Work in an empty directory
53 2 Lynn Garren
** copyFromJenkins -N -q c2 -q c7 -q e17 -q e19 critic-all
54 2 Lynn Garren
** copyToSciSoft *
55 4 Lynn Garren
56 35 Joe Boyd
h2. Update other products to use the appropriate release of art (SciSoft team or experiments, see bullet notes)
57 12 Lynn Garren
58 37 Erica Snider
* artdaq_core (This should go to the artdaq group -- Eric Flumerfelt)
59 12 Lynn Garren
** Owned by the artdaq group
60 12 Lynn Garren
** This product is designed to build against several different releases of art, as reflected in the generated table file.
61 12 Lynn Garren
** If the head of develop matches the latest tag, then use git flow to tag against the head of develop.  Otherwise make a release branch against the latest tag and edit product deps.
62 12 Lynn Garren
** We only edit ups/product_deps to make a new release.
63 37 Erica Snider
* ifdh_art (SciSoft)
64 12 Lynn Garren
** This is the ifdh service developed by Marc Mengel at the request of the art team.
65 12 Lynn Garren
** ifdh_art can build against several different releases of art.
66 12 Lynn Garren
** ifdh_art is updated when libwda or ifdhc is updated or if it needs to recognize a new release of art.
67 37 Erica Snider
* nutools (Robert Hatcher?)
68 12 Lynn Garren
** This product is owned by NOvA
69 12 Lynn Garren
** However, larsoft uses it extensively and sometimes makes contributions to the code.
70 22 Lynn Garren
** Any changes beyond those required by a new release of art, genie, or geant4 must be approved.
71 12 Lynn Garren
72 36 Joe Boyd
h2. Build mu distributions ( mu2e should take this over)
73 11 Lynn Garren
74 11 Lynn Garren
* The mu distribution is basically an art distribution with a few additional products.
75 12 Lynn Garren
* The distribution is built when requested.
76 11 Lynn Garren
* Found on a branch of build-framework
77 11 Lynn Garren
78 39 Joe Boyd
h2. Build nutools releases and the nu or nulite distributions. (Erica will talk to Laura Fields about Robert Hatcher doing this)
79 1 Lynn Garren
80 1 Lynn Garren
* Both NOvA and LArSoft can drive the need for a new release of nutools.
81 11 Lynn Garren
** NOvA uses the full nu distribution.
82 11 Lynn Garren
** LArSoft now uses the nulite distribution which ignores packages that are NOvA specific.
83 29 Lynn Garren
* nutools has been split into modular components.
84 29 Lynn Garren
** This was a staged deployment.  As of nutools v3_05_00, only the CRY interface remains in nutools.
85 29 Lynn Garren
** The nutools suite now contains nusimdata, nugen, nug4, nuevdb, nurandom, and nutools.
86 29 Lynn Garren
** The build configure scripts are now generated from templates in nutools/bundle.
87 11 Lynn Garren
88 32 Joe Boyd
h2. LArSoft release management (SciSoft team plus experiment activity on patch releases)
89 28 Joe Boyd
90 29 Lynn Garren
* Note that the move to github and pull requests will change this workflow.
91 1 Lynn Garren
* Advise and collect information for each weekly release.
92 22 Lynn Garren
** I am often the first point of contact for code changes.
93 22 Lynn Garren
** Sometimes push back about proposed changes.
94 12 Lynn Garren
* Send notices that the release is about to start.
95 12 Lynn Garren
* Make a test build with larsoft and all the experiment code.
96 12 Lynn Garren
** From long experience, if there is more than one set of feature branches to merge, each set must be tested sequentially.
97 12 Lynn Garren
** While this could be done via CI, it is currently more efficient to test on woof.  Especially since overlapping feature branches must sometimes be tested.
98 12 Lynn Garren
** We do encourage anyone submitting a feature branch to run the CI themselves.
99 12 Lynn Garren
* We work on a temporary release branch.
100 12 Lynn Garren
* Once the tests are complete and successful, update the release versions for those packages which will be changing and then tag.
101 12 Lynn Garren
* The tag is merged with master, but not with develop. 
102 12 Lynn Garren
** Merging with develop before the tagged release is available on cvmfs causes all kinds of problems. 
103 12 Lynn Garren
* Build on Jenkins.  Sometimes we find problems during this step.  We move the tag if necessary when resolving problems.
104 12 Lynn Garren
* Once the build is complete, we finalize the release.
105 12 Lynn Garren
** pull the tarballs from Jenkins and upload them to SciSoft
106 12 Lynn Garren
** install the release on cvmfs
107 12 Lynn Garren
** For macOS building, we install the c2 build on /grid/fermiapp/products/larsoft
108 12 Lynn Garren
** make a cross package tag
109 12 Lynn Garren
** make release notes
110 12 Lynn Garren
** final merge with develop
111 12 Lynn Garren
** send an announcement
112 12 Lynn Garren
* The procedure is described in detail at [[larsoft:How_to_tag_and_build_a_LArSoft_vx_yy_zz_release]]
113 12 Lynn Garren
** Although it is tempting to take shortcuts, the procedure is designed to allow the release manager to recover from various problems that may arise.  Taking shortcuts removes those safeguards.
114 13 Lynn Garren
115 32 Joe Boyd
h2.  support various infrastructure products (SciSoft team)
116 15 Lynn Garren
117 15 Lynn Garren
* cetbuildtools and mrb
118 15 Lynn Garren
** both products were originally developed by me, but have significant contributions from others
119 15 Lynn Garren
** We have provided cetmodules for use within spack and are contemplating a move across the board from cetbuildtools to cetmodules.  Details need to be considered.
120 15 Lynn Garren
* larreltools
121 1 Lynn Garren
** Replaces laradmin
122 16 Lynn Garren
** Contains scripts used to build regular and patch releases of larsoft
123 15 Lynn Garren
* larutils
124 15 Lynn Garren
** The larsoft build scripts used on Jenkins reside in larutils
125 15 Lynn Garren
* artutilscripts
126 15 Lynn Garren
** The build scripts used when building art, nutools, etc. on Jenkins reside in artutilscripts. 
127 18 Lynn Garren
** This is also where buildFW, pullProducts, copyFromJenkins, copyToSciSoft, etc. are found.
128 15 Lynn Garren
* laradmin
129 15 Lynn Garren
** This is now only of archival interest
130 15 Lynn Garren
** It contains the record of various larsoft migrations.
131 15 Lynn Garren
132 21 Lynn Garren
h2. SciSoft
133 21 Lynn Garren
134 21 Lynn Garren
* approve requests for read-write access
135 21 Lynn Garren
** The possibility exists for someone to accidentally remove or overwrite products.
136 21 Lynn Garren
** For this reason, we use nfs4 groups to limit read-write access to necessary directories.
137 21 Lynn Garren
** Some members of the SciSoft team have read-write access to all of SciSoft.
138 21 Lynn Garren
* copy files to pnfs for archiving
139 21 Lynn Garren
** There is a procedure, but it is slow and not automatic.
140 21 Lynn Garren
141 13 Lynn Garren
h2. spack
142 13 Lynn Garren
143 13 Lynn Garren
* I attempt to help with the spack development, but this takes a back seat to the other efforts.
144 19 Lynn Garren
145 32 Joe Boyd
h2. heppdt (mu2e should take this over, Kutschke)
146 19 Lynn Garren
147 19 Lynn Garren
* This is a legacy product that was spun off as a C++ replacement for part of the original stdhep.
148 19 Lynn Garren
* It is still in use by mu2e.
149 20 Lynn Garren
150 23 Lynn Garren
h2. Mailing lists
151 23 Lynn Garren
152 23 Lynn Garren
* owner/manager of several mailing lists
153 23 Lynn Garren
** many are unused and can be retired
154 23 Lynn Garren
155 32 Joe Boyd
h2. CLHEP maintenance and support (someone at CERN)
156 20 Lynn Garren
157 20 Lynn Garren
* I have been the main point person for CLHEP bug fixes.
158 20 Lynn Garren
* Support will be passed to CERN.
159 24 Lynn Garren
160 25 Lynn Garren
h2. system management
161 24 Lynn Garren
162 26 Lynn Garren
* Still provide backup support for oink.  Rare that I do anything.
163 25 Lynn Garren
* detsim.fnal.gov
164 25 Lynn Garren
** Now supported by CCD