LArSoft Internals

LArSoft code management and distribution

• Adding or removing users
• Administrative scripts will be kept in the larreltools repository.
• 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
• Using the cetmodules migration script

Repository cleanup

• Removing old feature branches
• Removing old history
• Truncating commit history

who does what

What Lynn does

Pages to update and move

None at this time.

GitHub markdown tips placeholder

• replace with github wiki tips?

Ongoing Projects

OBSOLETE Architecture revision

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

Usability improvements

LArSoft License

Completed Projects

Building with clang
Migration to root 6

LArSoft code analysis

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

Profiling tests

• ProtoDUNE and DUNE Far Detector 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
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.