LArSoft Internals¶

• Table of contents
• LArSoft Internals
  • LArSoft code management and distribution
  • Repository cleanup
  • Truncating commit history
  • who does what
  • Pages to update and move
  • FNAL Redmine tricks
  • Ongoing Projects
  • Code cleanup
  • Completed Projects
  • LArSoft code analysis
  • Profiling tests
  • Legacy Redmine project sites

LArSoft code management and distribution¶

• Adding / removing users
• Admin scripts
• LArSoft release management
  • How to tag and build a normal LArSoft vxx_yy_zz release
  • How to tag and build a LArSoft patch release
  • Installing products on cvmfs
• Informal list of experiment contacts
• Policy for development from a tagged release
• Procedure to create a new version of larsoft_data, uboone_data, etc.
• Installation procedures
• LArSoft cvmfs
• Nightly builds (no longer done)

Repository cleanup¶

• Removing old feature branches
• Removing old history

Truncating commit history¶

• Truncating commit history at svn to git transition

who does what¶

What Lynn does

Pages to update and move¶

Some pages in LArSoft have a combination of useful and out-of-date information. It would be good to at least remove the out-of-date material, even better would be to update it. The following is a list. Feel free to revise any of the pages and suggest where they should go. (Note, some information may belong partly on larsoft.org and partly in redmine.)

• Using LArSoft on the GPVM nodes - review and update (and place in Developing with LArSoft or Using LArSoft)
• Package Documentation - out of date?
• Geometry - should this be split between larsoft.org and Developing with LArSoft could be under Designing, or under Examples.
• Reconstruction - merge into larsoft.org?
• Simulation - update code references, split?
• Space Points - out of date?
• [[larsoftsvn:Seed Finding and Bezier Tracking]] - look at legacy info, maybe delete, or find owner?
• [[larsoftsvn:Optical Simulations]] - - look at legacy info, update, split?
• dependencies

FNAL Redmine tricks¶

Ongoing Projects¶

Architecture revision

• Data products architecture and design
  • action items
• Data product revision (phase II)

Usability improvements

LArSoft License

Code cleanup¶

• Services and modules scheduled for removal

Completed Projects¶

Building with clang
Migration to root 6

LArSoft code analysis¶

• Code analysis process
• Code and Performance analysis tools
• PMA module code analysis

Profiling tests¶

• ProtoDUNE and DUNE Far Detector simulation and reconstruction workflows (v06_57_00)

Legacy Redmine project sites¶

These were the sites used when LArSoft was developed under cvs and svn + SoftRelTools, respectively:

LArSoft-cvs wiki for the legacy cvs-based LArSoft project
[[larsoftsvn:| LArSoft-svn wiki for the legacy svn-based LArSoft project]]

As of Jan 24, 2014, LArSoft transitioned from svn / SRT to git / mrb / ups, but we retain the legacy projects for historical reasons.