Project

General

Profile

Developing With LArSoft » History » Version 81

Katherine Lato, 03/02/2017 01:35 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 52 Katherine Lato
h3(count). LArSoft repositories
20 1 Katherine Lato
21 1 Katherine Lato
  * [[ LArSoft repositories, packages and dependencies ]]
22 1 Katherine Lato
23 63 Gianluca Petrillo
h3(count). The _art_ framework
24 29 Katherine Lato
25 66 Katherine Lato
  * "_art_ documentation on WordPress":http://art.fnal.gov for general information 
26 66 Katherine Lato
  * "_art_ documentation in Redmine":https://cdcvs.fnal.gov/redmine/projects/art/wiki for code specific information
27 66 Katherine Lato
  * "_art_ workbook":http://art.fnal.gov/art-workbook/ for examples and tutorials
28 64 Katherine Lato
  * [[Using art in LArSoft]]
29 1 Katherine Lato
30 78 Katherine Lato
h3(count). _gallery_
31 78 Katherine Lato
32 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/
33 78 Katherine Lato
34 52 Katherine Lato
h3(count). External packages
35 1 Katherine Lato
36 67 Katherine Lato
These are package written and maintained by the general physics and computing communities for 
37 1 Katherine Lato
38 36 Katherine Lato
|_.Package|_.Namespace|_.Short description|_.Location of headers|
39 36 Katherine Lato
|"C++":http://www.cplusplus.com/reference/|@std::@|\2. Extensions to base C++ that are part of the standard language|
40 36 Katherine Lato
|"ROOT":https://root.cern.ch|See below|Data-analysis tools|@$ROOT_INC@|
41 36 Katherine Lato
|"CLHEP":http://proj-clhep.web.cern.ch/proj-clhep/|@CLHEP::@|Class Library for High-Energy Physics|@$CLHEP_INC/CLHEP@|
42 36 Katherine Lato
|"Geant4":http://geant4.web.cern.ch/geant4/|See below|Detector simulations|@$G4INCLUDE@|
43 36 Katherine Lato
|"GENIE":http://www.genie-mc.org/|@genie::@|Neutrino Monte-Carlo Generator|@$GENIE_INC/GENIE@|
44 36 Katherine Lato
|"boost":http://www.boost.org/|@boost::@|General programming tools for C++|@$BOOST_INC/boost@|
45 65 Katherine Lato
|[[messagefacility:|Message Facility wiki documentation]]|@mf::@|Service for console messages|@$MESSAGEFACILITY_INC@|
46 72 Gianluca Petrillo
|[[art:wiki#Job-configuration|FHiCL Configuration]]|@fhicl::@|Configuration language and parsing tools|@$FHICLCPP_INC@|
47 42 Katherine Lato
|[[NuSoft and LArSoft|nutools and LArSoft]]|@simb::@ ...|Neutrino platform tools|@$NUTOOLS_INC@|
48 20 Katherine Lato
49 42 Katherine Lato
50 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::@).
51 20 Katherine Lato
52 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.
53 36 Katherine Lato
54 52 Katherine Lato
h2(count). Writing code
55 1 Katherine Lato
56 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.
57 47 Katherine Lato
58 52 Katherine Lato
h3(count). Guidelines
59 47 Katherine Lato
60 80 Katherine Lato
# [[The rules and guidelines|Coding guidelines]]
61 80 Katherine Lato
# [[Code documentation guidelines]]
62 80 Katherine Lato
# [[Process for contributing code to LArSoft]]
63 80 Katherine Lato
# [[Writing LArSoft service|Guidelines on writing (and using) services in LArSoft]] _(in general)_
64 80 Katherine Lato
# [[Writing LArSoft algorithms|Guidelines on writing (and using) algorithms in LArSoft]] _(not specific to any algorithm)_
65 80 Katherine Lato
# [[Guidelines on using the geometry]]
66 80 Katherine Lato
# [[LArSoft examples|Examples!]]
67 80 Katherine Lato
# [[Some C++ good practices|some C++ suggestions]]
68 1 Katherine Lato
69 60 Katherine Lato
---
70 60 Katherine Lato
71 79 Gianluca Petrillo
h3(count). [[Tips on updating your code after LArSoft release]]
72 79 Gianluca Petrillo
73 79 Gianluca Petrillo
---
74 79 Gianluca Petrillo
75 52 Katherine Lato
h3(count). Tools and techniques
76 47 Katherine Lato
77 75 Gianluca Petrillo
h4(count). Documenting and browsing code
78 75 Gianluca Petrillo
79 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
80 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.
81 75 Gianluca Petrillo
82 52 Katherine Lato
h4(count). git and git flow
83 47 Katherine Lato
84 67 Katherine Lato
* [[LArSoft_git_Guidelines|git guidelines]]
85 57 Katherine Lato
* [[cet-is-public:git flow quick start]]
86 67 Katherine Lato
* [[cet-is-public:GitTipsAndTricks|Git Tips and Tricks]]
87 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)_
88 57 Katherine Lato
89 52 Katherine Lato
h4(count). Profiling
90 1 Katherine Lato
91 48 Katherine Lato
* [[memory profiling tools]]
92 48 Katherine Lato
* [[time profiling tools]]
93 48 Katherine Lato
* [[profiling utilities]]
94 48 Katherine Lato
95 52 Katherine Lato
h4(count). Debugging
96 48 Katherine Lato
97 56 Katherine Lato
* [[Debugging LArSoft with Allinea]] 
98 56 Katherine Lato
* [[Debugging LArSoft]] with RogueWave TotalView. (*TotalView is no longer being paid for. Please use Allinea above instead.*)
99 55 Katherine Lato
* [[Debugging with gdb]]
100 60 Katherine Lato
101 60 Katherine Lato
---
102 1 Katherine Lato
103 52 Katherine Lato
h2(count). Building
104 1 Katherine Lato
105 67 Katherine Lato
h3(count). Using the build system
106 1 Katherine Lato
107 36 Katherine Lato
  * *[[Quick Links|Look for experiment specific guides to using and developing LArSoft code ]]*
108 71 Katherine Lato
  *  Choose the correct release from the [[LArSoft release list|List of LArSoft Releases and Release Notes]]. 
109 73 Gianluca Petrillo
  * [[UpdatingToNewRelease|What to do when there is a new release ]] (a.k.a. **[[UpdatingToNewRelease|update LArSoft version]]**)
110 67 Katherine Lato
  
111 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.
112 44 Lynn Garren
113 67 Katherine Lato
h3(count). Understanding CMakeLists.txt and product_deps files
114 67 Katherine Lato
115 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
116 1 Katherine Lato
* [[cet-is-public:Art cmake modules]]: such as @art_make@ and @simple_plugin@. Used in @CMakeLists.txt@ files throughout LArSoft
117 1 Katherine Lato
* [[cet-is-public:Defining products in the CET build environment]]: explains the @product_deps@ file
118 1 Katherine Lato
* [[cet-is-public:AddingProductDependencies|Adding Product Dependencies]]: how to edit the @product_deps@ and @CMakeLists.txt@ files to add dependencies
119 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
120 1 Katherine Lato
* [[cet-is-public:Building your own code with cmake]]:  pointer to a _really_ simple example
121 1 Katherine Lato
122 67 Katherine Lato
h3(count). mrb (multi-repository build) tool
123 67 Katherine Lato
124 67 Katherine Lato
* "mrb user guide":https://cdcvs.fnal.gov/redmine/projects/mrb/wiki/MrbUserGuide
125 67 Katherine Lato
* "mrb reference guide":https://cdcvs.fnal.gov/redmine/projects/mrb/wiki/MrbRefereceGuide
126 67 Katherine Lato
* "Documentation for buildtool":https://cdcvs.fnal.gov/redmine/projects/cet-is-public/wiki/Buildtool_script
127 67 Katherine Lato
** mrb calls @buildtool@ (from the @cetbuildtools@ product) to perform the build. 
128 67 Katherine Lato
129 67 Katherine Lato
h3(count). ups
130 67 Katherine Lato
131 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 
132 67 Katherine Lato
* [[cet-is-public:AboutQualifiers|About qualifiers]]:  the things after "-q" in setup <prod> <ver> -q <qual>
133 67 Katherine Lato
* "More Relocatable UPS Documentation":https://cdcvs.fnal.gov/redmine/projects/ups/wiki/Documentation
134 36 Katherine Lato
135 38 Katherine Lato
h2(count). Testing
136 1 Katherine Lato
137 76 Katherine Lato
High-level description of testing is available at "larsoft.org":http://larsoft.org/larsoft-testing/
138 38 Katherine Lato
139 38 Katherine Lato
h3(count). LArSoft Continuous Integration (CI) system
140 36 Katherine Lato
141 52 Katherine Lato
  * "High-level description of CI":http://larsoft.org/continuous-integration/
142 1 Katherine Lato
  * "CI results display page":http://lar-ci-history.fnal.gov:8080/LarCI/app/view_builds/index
143 36 Katherine Lato
  * [[LAr-Continuous-Integration:| LAr-Continuous-Integration subproject wiki]]
144 1 Katherine Lato
145 67 Katherine Lato
h2(count). Submitting for next release
146 36 Katherine Lato
147 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.
148 42 Katherine Lato
149 42 Katherine Lato
* [[Getting new code into a LArSoft release]]  _(Procedures and policies for making changes to LArSoft releases)_
150 81 Katherine Lato
151 81 Katherine Lato
Also look at  [[Process for contributing code to LArSoft]].