Project

General

Profile

Developing With LArSoft » History » Version 90

Lynn Garren, 06/27/2018 01:57 PM

1 3 Lynn Garren
{{>toc}}
2 3 Lynn Garren
3 52 Katherine Lato
h1(count). Developing With LArSoft
4 1 Katherine Lato
5 52 Katherine Lato
h2(count). Quick links for Developing with LArSoft
6 36 Katherine Lato
7 35 Katherine Lato
* " LArSoft repositories packages and dependencies ":https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/_LArSoft_repositories_packages_and_dependencies_
8 45 Katherine Lato
* "Concepts in LArSoft":http://larsoft.org/important-concepts-in-larsoft/
9 1 Katherine Lato
10 52 Katherine Lato
h2(count). Designing
11 30 Katherine Lato
12 41 Katherine Lato
To design LArSoft code, it's important to understand the core LArSoft suite and all the components used by it. Reference the items below when designing new software.
13 34 Erica Snider
14 52 Katherine Lato
h3(count). LArSoft architecture and design principles
15 1 Katherine Lato
16 61 Gianluca Petrillo
* "Latest architecture document as PDF download":https://cdcvs.fnal.gov/redmine/projects/larsoft-architecture/repository/revisions/master/raw/output/LArSoftArchitecture.pdf
17 76 Katherine Lato
* "Design principles on larsoft.org":http://larsoft.org/important-concepts-in-larsoft/design/
18 1 Katherine Lato
19 85 Katherine Lato
h3(count). LArSoft packages and repositories
20 1 Katherine Lato
21 1 Katherine Lato
  * [[ LArSoft repositories, packages and dependencies ]]
22 86 Katherine Lato
  * [[Geometry Package]]
23 88 Katherine Lato
  * [[LArSoft art-independent code and repositories]]
24 1 Katherine Lato
25 63 Gianluca Petrillo
h3(count). The _art_ framework
26 29 Katherine Lato
27 66 Katherine Lato
  * "_art_ documentation on WordPress":http://art.fnal.gov for general information 
28 66 Katherine Lato
  * "_art_ documentation in Redmine":https://cdcvs.fnal.gov/redmine/projects/art/wiki for code specific information
29 66 Katherine Lato
  * "_art_ workbook":http://art.fnal.gov/art-workbook/ for examples and tutorials
30 64 Katherine Lato
  * [[Using art in LArSoft]]
31 1 Katherine Lato
32 78 Katherine Lato
h3(count). _gallery_
33 78 Katherine Lato
34 78 Katherine Lato
_gallery_ provides lightweight access to event data in art/ROOT files outside the art event processing framework executable. It is not an alternative framework; rather, it provides a library that can be used to write programs that need to read (but not write) art/ROOT files. Information is available at: http://art.fnal.gov/gallery/
35 78 Katherine Lato
36 52 Katherine Lato
h3(count). External packages
37 1 Katherine Lato
38 67 Katherine Lato
These are package written and maintained by the general physics and computing communities for 
39 1 Katherine Lato
40 36 Katherine Lato
|_.Package|_.Namespace|_.Short description|_.Location of headers|
41 36 Katherine Lato
|"C++":http://www.cplusplus.com/reference/|@std::@|\2. Extensions to base C++ that are part of the standard language|
42 36 Katherine Lato
|"ROOT":https://root.cern.ch|See below|Data-analysis tools|@$ROOT_INC@|
43 36 Katherine Lato
|"CLHEP":http://proj-clhep.web.cern.ch/proj-clhep/|@CLHEP::@|Class Library for High-Energy Physics|@$CLHEP_INC/CLHEP@|
44 36 Katherine Lato
|"Geant4":http://geant4.web.cern.ch/geant4/|See below|Detector simulations|@$G4INCLUDE@|
45 36 Katherine Lato
|"GENIE":http://www.genie-mc.org/|@genie::@|Neutrino Monte-Carlo Generator|@$GENIE_INC/GENIE@|
46 36 Katherine Lato
|"boost":http://www.boost.org/|@boost::@|General programming tools for C++|@$BOOST_INC/boost@|
47 65 Katherine Lato
|[[messagefacility:|Message Facility wiki documentation]]|@mf::@|Service for console messages|@$MESSAGEFACILITY_INC@|
48 72 Gianluca Petrillo
|[[art:wiki#Job-configuration|FHiCL Configuration]]|@fhicl::@|Configuration language and parsing tools|@$FHICLCPP_INC@|
49 42 Katherine Lato
|[[NuSoft and LArSoft|nutools and LArSoft]]|@simb::@ ...|Neutrino platform tools|@$NUTOOLS_INC@|
50 20 Katherine Lato
51 42 Katherine Lato
52 36 Katherine Lato
ROOT and Geant4 do not use namespaces. In general, ROOT classes begin with "T" (e.g., "TTree":http://root.cern.ch/root/html522/TTree.html, "TH1":http://root.cern.ch/root/html522/TH1.html) while "Geant4 classes":http://geant4www.triumf.ca/lxr/ begin with "G4" (e.g., "G4Track":http://geant4www.triumf.ca/lxr/source//track/include/G4Track.hh, "G4Step":http://geant4www.triumf.ca/lxr/source//track/include/G4Step.hh). Exception: Some of the newer ROOT sub-packages have namespaces (such as @ROOT::Math::@, @ROOT::Fit::@, @ROOT::Minuit2::@, @Reflex::@, @TMVA::@).
53 20 Katherine Lato
54 36 Katherine Lato
Some of these packages duplicate functionality; e.g., 4-vectors are implemented in both "ROOT":http://root.cern.ch/root/html522/TLorentzVector.html and "CLHEP":http://proj-clhep.web.cern.ch/proj-clhep/doc/CLHEP_2_1_2_2/doxygen/html/LorentzVector_8h.html. Given a choice, use a package that's higher in the above tables over one that's lower; e.g., choose ROOT classes over their CLHEP equivalents.
55 36 Katherine Lato
56 52 Katherine Lato
h2(count). Writing code
57 1 Katherine Lato
58 47 Katherine Lato
Whether you are writing new code or modifying existing code, please follow the guidelines listed below. There are also development tools and techniques available that can make coding easier.
59 47 Katherine Lato
60 52 Katherine Lato
h3(count). Guidelines
61 47 Katherine Lato
62 80 Katherine Lato
# [[The rules and guidelines|Coding guidelines]]
63 84 Katherine Lato
# [[Code documentation requirements and guidelines]]
64 80 Katherine Lato
# [[Process for contributing code to LArSoft]]
65 80 Katherine Lato
# [[Writing LArSoft service|Guidelines on writing (and using) services in LArSoft]] _(in general)_
66 80 Katherine Lato
# [[Writing LArSoft algorithms|Guidelines on writing (and using) algorithms in LArSoft]] _(not specific to any algorithm)_
67 80 Katherine Lato
# [[Guidelines on using the geometry]]
68 80 Katherine Lato
# [[LArSoft examples|Examples!]]
69 80 Katherine Lato
# [[Some C++ good practices|some C++ suggestions]]
70 90 Lynn Garren
# [[Using git repositories]]
71 1 Katherine Lato
72 60 Katherine Lato
---
73 60 Katherine Lato
74 83 Gianluca Petrillo
h3(count). How to...
75 83 Gianluca Petrillo
76 83 Gianluca Petrillo
* ... [[Use associations|create and use associations]]
77 87 Gianluca Petrillo
* ... [[From_ROOT_vectors_(TVector3)_to_ROOT_GenVector|use the new ROOT vectors and linear algebra classes in the code]] (GenVector, SMatrix)
78 87 Gianluca Petrillo
79 83 Gianluca Petrillo
80 83 Gianluca Petrillo
---
81 83 Gianluca Petrillo
82 79 Gianluca Petrillo
h3(count). [[Tips on updating your code after LArSoft release]]
83 79 Gianluca Petrillo
84 79 Gianluca Petrillo
---
85 79 Gianluca Petrillo
86 52 Katherine Lato
h3(count). Tools and techniques
87 47 Katherine Lato
88 75 Gianluca Petrillo
h4(count). Documenting and browsing code
89 75 Gianluca Petrillo
90 75 Gianluca Petrillo
* "LArSoft Doxygen":http://nusoft.fnal.gov/larsoft/doxsvn/html/index.html - comments in the code are incorporated into documentation using "the Doxygen tool.":http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html
91 75 Gianluca Petrillo
* "LXR Cross Referencer":http://cdcvs.fnal.gov/lxr/ -  general purpose source code indexer and cross-referencer that provides web-based browsing of source code with links to the definition and usage of any identifier. Supports multiple languages. Includes LArSoft code. Note, pages may take several seconds to load.
92 75 Gianluca Petrillo
93 52 Katherine Lato
h4(count). git and git flow
94 47 Katherine Lato
95 67 Katherine Lato
* [[LArSoft_git_Guidelines|git guidelines]]
96 57 Katherine Lato
* [[cet-is-public:git flow quick start]]
97 67 Katherine Lato
* [[cet-is-public:GitTipsAndTricks|Git Tips and Tricks]]
98 67 Katherine Lato
_(for the purposes of LArSoft development, please please ignore anything other than how to use various git commands to do specific tasks - and especially ignore the workflow advices)_
99 57 Katherine Lato
100 52 Katherine Lato
h4(count). Profiling
101 1 Katherine Lato
102 48 Katherine Lato
* [[memory profiling tools]]
103 48 Katherine Lato
* [[time profiling tools]]
104 48 Katherine Lato
* [[profiling utilities]]
105 48 Katherine Lato
106 52 Katherine Lato
h4(count). Debugging
107 48 Katherine Lato
108 56 Katherine Lato
* [[Debugging LArSoft with Allinea]] 
109 56 Katherine Lato
* [[Debugging LArSoft]] with RogueWave TotalView. (*TotalView is no longer being paid for. Please use Allinea above instead.*)
110 55 Katherine Lato
* [[Debugging with gdb]]
111 60 Katherine Lato
112 60 Katherine Lato
---
113 1 Katherine Lato
114 52 Katherine Lato
h2(count). Building
115 1 Katherine Lato
116 67 Katherine Lato
h3(count). Using the build system
117 1 Katherine Lato
118 36 Katherine Lato
  * *[[Quick Links|Look for experiment specific guides to using and developing LArSoft code ]]*
119 71 Katherine Lato
  *  Choose the correct release from the [[LArSoft release list|List of LArSoft Releases and Release Notes]]. 
120 73 Gianluca Petrillo
  * [[UpdatingToNewRelease|What to do when there is a new release ]] (a.k.a. **[[UpdatingToNewRelease|update LArSoft version]]**)
121 67 Katherine Lato
  
122 67 Katherine Lato
To get write access to the repositories, speak to the offline coordinator for your experiment. If you have a question, send email to larsoft-team@fnal.gov.
123 44 Lynn Garren
124 67 Katherine Lato
h3(count). Understanding CMakeLists.txt and product_deps files
125 67 Katherine Lato
126 1 Katherine Lato
* [[cet-is-public:Cetbuildtools cmake modules]]:  such as @cet_make@ and @cet_add_compiler_flags@. Used in @CMakeLists.txt@ files throughout LArSoft
127 1 Katherine Lato
* [[cet-is-public:Art cmake modules]]: such as @art_make@ and @simple_plugin@. Used in @CMakeLists.txt@ files throughout LArSoft
128 1 Katherine Lato
* [[cet-is-public:Defining products in the CET build environment]]: explains the @product_deps@ file
129 1 Katherine Lato
* [[cet-is-public:AddingProductDependencies|Adding Product Dependencies]]: how to edit the @product_deps@ and @CMakeLists.txt@ files to add dependencies
130 1 Katherine Lato
* [[cet-is-public:CodeTips|Various helpful tips for coding in the CET C++ environment]]: things you hope you never need to know
131 1 Katherine Lato
* [[cet-is-public:Building your own code with cmake]]:  pointer to a _really_ simple example
132 89 Robert Hatcher
* [[Using find_global_symbol.sh to find unresolved symbols]]: automatic library search for symbols
133 1 Katherine Lato
134 67 Katherine Lato
h3(count). mrb (multi-repository build) tool
135 67 Katherine Lato
136 67 Katherine Lato
* "mrb user guide":https://cdcvs.fnal.gov/redmine/projects/mrb/wiki/MrbUserGuide
137 67 Katherine Lato
* "mrb reference guide":https://cdcvs.fnal.gov/redmine/projects/mrb/wiki/MrbRefereceGuide
138 67 Katherine Lato
* "Documentation for buildtool":https://cdcvs.fnal.gov/redmine/projects/cet-is-public/wiki/Buildtool_script
139 67 Katherine Lato
** mrb calls @buildtool@ (from the @cetbuildtools@ product) to perform the build. 
140 67 Katherine Lato
141 67 Katherine Lato
h3(count). ups
142 67 Katherine Lato
143 77 Katherine Lato
* "Getting Started with UPS":https://cdcvs.fnal.gov/redmine/projects/ups/wiki/Getting_Started_Using_UPS and "About UPS":https://cdcvs.fnal.gov/redmine/projects/cet-is-public/wiki/AboutUPS 
144 67 Katherine Lato
* [[cet-is-public:AboutQualifiers|About qualifiers]]:  the things after "-q" in setup <prod> <ver> -q <qual>
145 67 Katherine Lato
* "More Relocatable UPS Documentation":https://cdcvs.fnal.gov/redmine/projects/ups/wiki/Documentation
146 36 Katherine Lato
147 38 Katherine Lato
h2(count). Testing
148 1 Katherine Lato
149 76 Katherine Lato
High-level description of testing is available at "larsoft.org":http://larsoft.org/larsoft-testing/
150 38 Katherine Lato
151 38 Katherine Lato
h3(count). LArSoft Continuous Integration (CI) system
152 36 Katherine Lato
153 52 Katherine Lato
  * "High-level description of CI":http://larsoft.org/continuous-integration/
154 82 Vito Di Benedetto
  * "CI results display page":http://lar-ci-history.fnal.gov/LarCI/app
155 82 Vito Di Benedetto
  * [[lar_ci:| LAr-Continuous-Integration subproject wiki]]
156 1 Katherine Lato
157 67 Katherine Lato
h2(count). Submitting for next release
158 36 Katherine Lato
159 52 Katherine Lato
After designing, coding, building and testing a piece of software, submit it to the LArSoft development branch so it is included in a new release.
160 42 Katherine Lato
161 42 Katherine Lato
* [[Getting new code into a LArSoft release]]  _(Procedures and policies for making changes to LArSoft releases)_
162 81 Katherine Lato
163 81 Katherine Lato
Also look at  [[Process for contributing code to LArSoft]].