Difference: LArSoftAtNevisSRT (1 vs. 35)

Revision 352014-02-07 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 101 to 101
 When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above. </verbatim> \ No newline at end of file

Added:
>
>
META TOPICMOVED by="WilliamSeligman" date="1391814976" from="Nevis.LArSoftAtNevis" to="Nevis.LArSoftAtNevisSRT"

Revision 342014-01-21 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 6 to 6
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 17-Dec-2013, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 21-Jan-2014, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Changed:
<
<
S2013.12.17 - ART 1.08.10.
>
>
S2014.01.21 - Freeze before switch to mrb+git S2013.12.17 - ART 1.08.10
 S2013.10.21 - new optical algorithms; frozen before introduction of Pandora S2013.06.25 - bug fixes for BezierTracks and SeedFinder; fixed release for MC challenge S2013.06.17 - put nutools into external package

Revision 332013-12-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 6 to 6
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 14-Nov-2013, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 17-Dec-2013, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Added:
>
>
S2013.12.17 - ART 1.08.10.
 S2013.10.21 - new optical algorithms; frozen before introduction of Pandora S2013.06.25 - bug fixes for BezierTracks and SeedFinder; fixed release for MC challenge S2013.06.17 - put nutools into external package

Revision 322013-12-10 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 54 to 54
 

Debugging

Changed:
<
<
The default versions of the program libraries are compiled without the debugger, so the programs will run faster. If you want to debug your code, use the -q debug option; e.g.,
>
>
As of Dec-2013, the default is to compile all the programs with the debugger, so you can use tools to debug your code. If you want to set this explicitly (in case the default version changes), use the -q debug option; e.g.,
 
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug
Line: 67 to 67
 source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.10.21
Added:
>
>

Production runs

If you're confident your code works, you probably want to compile your programs with compiler optimization turned on. To do this, use the prof qualifier; e.g.,

source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q prof

Always do a test run of your program with prof before submitting a large set of batch jobs. Occasionally there are issues that show up under optimization that don't show up in the debug versions.

 

Make life easier

You may want to put an alias to the appropriate set-up commands in your .myprofile or .mycshrc file; for example, if you look in ~seligman/.myprofile, you'll see the following:

Revision 312013-11-14 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 6 to 6
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 25-Jun-2013, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 14-Nov-2013, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Added:
>
>
S2013.10.21 - new optical algorithms; frozen before introduction of Pandora
 S2013.06.25 - bug fixes for BezierTracks and SeedFinder; fixed release for MC challenge S2013.06.17 - put nutools into external package S2013.05.12 - separation of objects and algorithms
Line: 48 to 49
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.06.25
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.10.21
 

Debugging

Line: 63 to 64
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.06.25
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.10.21
 

Make life easier

Revision 302013-07-25 - VictorGenty

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Deleted:
<
<
 
Deleted:
<
<
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Line: 50 to 49
 If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -rS2013.06.25
Added:
>
>
 

Debugging

Line: 87 to 88
  When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
Deleted:
<
<
The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.
 \ No newline at end of file
Added:
>
>
The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above. </verbatim>

Revision 292013-06-25 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 18-Mar-2013, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 25-Jun-2013, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Changed:
<
<
S2013.06.17 - put nutools into external package; fixed release for MC challenge
>
>
S2013.06.25 - bug fixes for BezierTracks and SeedFinder; fixed release for MC challenge S2013.06.17 - put nutools into external package
 S2013.05.12 - separation of objects and algorithms S2013.04.21 - frozen before new ART release S2013.03.11 - additions for 10kT and 35kT detectors
Line: 48 to 49
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -rS2013.06.17
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -rS2013.06.25
 

Debugging

Line: 63 to 63
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.06.17
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.06.25
 

Make life easier

Revision 282013-06-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  As of 18-Mar-2013, the following Fermilab LArSoft releases are maintained at Nevis:
Changed:
<
<
development - put nutools into external package
>
>
development S2013.06.17 - put nutools into external package; fixed release for MC challenge
 S2013.05.12 - separation of objects and algorithms S2013.04.21 - frozen before new ART release S2013.03.11 - additions for 10kT and 35kT detectors
Line: 47 to 48
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.05.12
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -rS2013.06.17
 

Debugging

Line: 62 to 63
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.05.12
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.06.17
 

Make life easier

Line: 85 to 86
 

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

Added:
>
>
The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.

Revision 272013-06-06 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 74 to 74
  ${MYDEV} is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.
Added:
>
>

The MicroBooNE repository

There's a copy of the MicroBooNE offline repository at /a/share/westside/seligman/microboone/ubooneoffline. It will be kept updated with any changes to the repository at FNAL.

At present (June-2013), there are no separate LArSoft-like packages in this repository that are intended to be extensions or revisions to LArSoft, and therefore no build scripts. Therefore, I'm not building and updating libraries in the same way I do the Nevis LArSoft repository.

The MicroBooNE UPS products (e.g., the ability to type setup ubtools) has not been implemented at Nevis yet, in part because the MicroBooNE UPS products are very FNAL-specific.

 

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial. \ No newline at end of file

Revision 262013-05-14 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  As of 18-Mar-2013, the following Fermilab LArSoft releases are maintained at Nevis:
Changed:
<
<
development
>
>
development - put nutools into external package S2013.05.12 - separation of objects and algorithms
 S2013.04.21 - frozen before new ART release S2013.03.11 - additions for 10kT and 35kT detectors S2013.01.16 - frozen before LBNE geometry changes
Line: 46 to 47
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.04.21
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.05.12
 

Debugging

Line: 61 to 62
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.04.21
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.05.12
 

Make life easier

Revision 252013-04-23 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 18-Mar-2013, the following Fermilab LArSoft releases are maintained at Nevis:
development 
Changed:
<
<
S2013.03.11 - additions for 10kT and 35kT detectors; frozen before new ART release
>
>
S2013.04.21 - frozen before new ART release S2013.03.11 - additions for 10kT and 35kT detectors
 S2013.01.16 - frozen before LBNE geometry changes S2012.12.17 - frozen for MicroBooNE S2012.10.02 - switch to C++11; frozen for ArgoNeuT
Line: 45 to 46
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.03.11
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.04.21
 

Debugging

Line: 60 to 61
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.03.11
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.04.21
 

Make life easier

Revision 242013-03-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 16-Jan-2013, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 18-Mar-2013, the following Fermilab LArSoft releases are maintained at Nevis:
 
development 
Added:
>
>
S2013.03.11 - additions for 10kT and 35kT detectors; frozen before new ART release
 S2013.01.16 - frozen before LBNE geometry changes S2012.12.17 - frozen for MicroBooNE S2012.10.02 - switch to C++11; frozen for ArgoNeuT
Line: 44 to 45
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.01.16
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.03.11
 

Debugging

Line: 59 to 60
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.01.16
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.03.11
 

Make life easier

Revision 232013-01-16 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 26-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 16-Jan-2013, the following Fermilab LArSoft releases are maintained at Nevis:
 
development 
Added:
>
>
S2013.01.16 - frozen before LBNE geometry changes
 S2012.12.17 - frozen for MicroBooNE S2012.10.02 - switch to C++11; frozen for ArgoNeuT S2012.09.18 - improvements to event displays and many other fixes; the "hand-scan" release
Line: 43 to 44
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2012.12.17
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2013.01.16
 

Debugging

Line: 58 to 59
 
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
  • You can run the debugger on a fixed release:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2012.12.17
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2013.01.16
 

Make life easier

Revision 222012-12-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  As of 26-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
Changed:
<
<
development - switch to C++11
>
>
development S2012.12.17 - frozen for MicroBooNE
 S2012.10.02 - switch to C++11; frozen for ArgoNeuT S2012.09.18 - improvements to event displays and many other fixes; the "hand-scan" release S2012.05.09 - improvements to reconstruction & geometry
Line: 42 to 43
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2012.09.18
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2012.12.17
 

Debugging

Line: 55 to 56
 This will use program libraries compiled with the debugger option turned on. Then tools such as gdb and valgrind will show line numbers and can display lines of source code.
  • If you're working with your own code in a test release, you'll have to re-compile it to include the debugging information in your own programs. The commands make clean; make should do it.
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
Changed:
<
<
  • If you have to, you can run the debugger on a fixed release:
>
>
  • You can run the debugger on a fixed release:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2012.09.18
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2012.12.17
 

Make life easier

Revision 212012-10-12 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 26-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
development - switch to C++11
Added:
>
>
S2012.10.02 - switch to C++11; frozen for ArgoNeuT
 S2012.09.18 - improvements to event displays and many other fixes; the "hand-scan" release S2012.05.09 - improvements to reconstruction & geometry

Revision 202012-10-12 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 33 to 33
  This will set your $PATH and $LD_LIBRARY_PATH variables to refer to the various packages required by LArSoft. After you execute this command, you can develop code and run jobs.
Added:
>
>
Note that this setup command only works properly once per login session. If you want to set things up differently (e.g., switch to a different release, turn on debug mode) then the simplest way to do it is to log out from your terminal session, log in again, and enter the new setup command.
 

Selecting a release

The above command will set up the development version of LArSoft. If you want to develop or revise code in LArSoft, this is the release you want.

Line: 68 to 70
 

Nevis notes

Changed:
<
<
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions.
>
>
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

Revision 192012-09-26 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 18-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 26-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
 
Changed:
<
<
development
>
>
development - switch to C++11
 S2012.09.18 - improvements to event displays and many other fixes; the "hand-scan" release S2012.05.09 - improvements to reconstruction & geometry
Deleted:
<
<
S2012.03.14 - ART 1.00.11 S2012.03.11 - ART 1.00.08 S2011.11.18 S2011.10.27 S2011.08.13 S2011.06.09 S2011.05.23 S2011.05.18 - add versions to classes_def.xml S2011.05.02
  The list of available releases is a subset of those in the official LArSoft repository at Fermilab. Requests for updates, compilations, and additional releases can be sent to seligman of nevis.columbia.edu

Revision 182012-09-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 14-Mar-2012, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 18-Sep-2012, the following Fermilab LArSoft releases are maintained at Nevis:
 
development 
Added:
>
>
S2012.09.18 - improvements to event displays and many other fixes; the "hand-scan" release
 S2012.05.09 - improvements to reconstruction & geometry S2012.03.14 - ART 1.00.11 S2012.03.11 - ART 1.00.08
Line: 45 to 46
  The above command will set up the development version of LArSoft. If you want to develop or revise code in LArSoft, this is the release you want.
Changed:
<
<
If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
>
>
If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.10.27
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2012.09.18
 

Debugging

Line: 60 to 61
 This will use program libraries compiled with the debugger option turned on. Then tools such as gdb and valgrind will show line numbers and can display lines of source code.
  • If you're working with your own code in a test release, you'll have to re-compile it to include the debugging information in your own programs. The commands make clean; make should do it.
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
Added:
>
>
  • If you have to, you can run the debugger on a fixed release:
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug -r S2012.09.18
 

Make life easier

Line: 70 to 75
  ${MYDEV} is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.
Deleted:
<
<

Event display

To use the event display with MicroBooNE events, you have to edit the configuration file:

cp $SRT_PUBLIC_CONTEXT/job/evd.fcl [whatever]
# Edit [whatever]/evd.fcl, changing argoneut_disp to microboone_disp
lar -c [whatever]/evd.fcl [yourfile].root
 

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. \ No newline at end of file

Revision 172012-05-09 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  As of 14-Mar-2012, the following Fermilab LArSoft releases are maintained at Nevis:
Changed:
<
<
development - add multiple crytostats to Geometry
>
>
development S2012.05.09 - improvements to reconstruction & geometry
 S2012.03.14 - ART 1.00.11 S2012.03.11 - ART 1.00.08 S2011.11.18

Revision 162012-04-10 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
Changed:
<
<
As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 14-Mar-2012, the following Fermilab LArSoft releases are maintained at Nevis:
 
development - add multiple crytostats to Geometry
S2012.03.14 - ART 1.00.11

Revision 152012-03-15 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
Changed:
<
<
development S2012.03.11
>
>
development - add multiple crytostats to Geometry S2012.03.14 - ART 1.00.11 S2012.03.11 - ART 1.00.08
 S2011.11.18 S2011.10.27 S2011.08.13 S2011.06.09 S2011.05.23
Changed:
<
<
S2011.05.18
>
>
S2011.05.18 - add versions to classes_def.xml
 S2011.05.02 The list of available releases is a subset of those in the official LArSoft repository at Fermilab. Requests for updates, compilations, and additional releases can be sent to seligman of nevis.columbia.edu

Revision 142012-03-13 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
development
Added:
>
>
S2012.03.11
 S2011.11.18 S2011.10.27 S2011.08.13

Revision 132011-12-30 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 6 to 6
 
Changed:
<
<
The Nevis copy of the LArSoft installation is currently in /a/share/amsterdam/seligman/microboone/LArSoft.
>
>
The Nevis copy of the LArSoft installation is currently in /a/share/westside/seligman/microboone/LArSoft.
  As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
Line: 23 to 23
 

Where can one run LArSoft

Changed:
<
<
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to amsterdam.
>
>
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.
 

Setting up the Environment

The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:

# sh-style shell, such as bash or zsh
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh
  # csh-style shell, such as tcsh
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.csh
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.csh
 

This will set your $PATH and $LD_LIBRARY_PATH variables to refer to the various packages required by LArSoft. After you execute this command, you can develop code and run jobs.

Line: 44 to 44
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.10.27
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.10.27
 

Debugging

The default versions of the program libraries are compiled without the debugger, so the programs will run faster. If you want to debug your code, use the -q debug option; e.g.,

Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug
>
>
source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug
 

This will use program libraries compiled with the debugger option turned on. Then tools such as gdb and valgrind will show line numbers and can display lines of source code.

Line: 62 to 62
  You may want to put an alias to the appropriate set-up commands in your .myprofile or .mycshrc file; for example, if you look in ~seligman/.myprofile, you'll see the following:
Changed:
<
<
export MYDEV=/a/share/amsterdam/seligman/microboone/mydev alias MBD="source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh; srt_setup SRT_LOCAL=\${MYDEV}; cd \${MYDEV}"
>
>
export MYDEV=/a/share/westside/seligman/microboone/mydev alias MBD="source /a/share/westside/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh; srt_setup SRT_LOCAL=\${MYDEV}; cd \${MYDEV}"
  ${MYDEV} is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.

Revision 122011-11-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
development
Added:
>
>
S2011.11.18
 S2011.10.27 S2011.08.13 S2011.06.09

Revision 112011-11-17 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 43 to 43
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.18
>
>
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.10.27
 
Changed:
<
<

Debuging

>
>

Debugging

  The default versions of the program libraries are compiled without the debugger, so the programs will run faster. If you want to debug your code, use the -q debug option; e.g.,
Line: 61 to 61
  You may want to put an alias to the appropriate set-up commands in your .myprofile or .mycshrc file; for example, if you look in ~seligman/.myprofile, you'll see the following:
Changed:
<
<
alias MBD="source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh; cd /a/share/amsterdam/seligman/microboone/mydev; srt_setup -a"
>
>
export MYDEV=/a/share/amsterdam/seligman/microboone/mydev alias MBD="source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh; srt_setup SRT_LOCAL=\${MYDEV}; cd \${MYDEV}"
 
Changed:
<
<
/a/share/amsterdam/seligman/microboone/mydev is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.
>
>
${MYDEV} is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.
 

Event display

Revision 102011-11-10 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 46 to 46
 source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.18
Added:
>
>

Debuging

The default versions of the program libraries are compiled without the debugger, so the programs will run faster. If you want to debug your code, use the -q debug option; e.g.,

source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -q debug

This will use program libraries compiled with the debugger option turned on. Then tools such as gdb and valgrind will show line numbers and can display lines of source code.

  • If you're working with your own code in a test release, you'll have to re-compile it to include the debugging information in your own programs. The commands make clean; make should do it.
  • Ignore the section on TotalView in the LArSoft wiki debugging page; we don't have it installed at Nevis. We do have ddd installed, but you're probably better off using the non-graphical gdb instead.
 

Make life easier

You may want to put an alias to the appropriate set-up commands in your .myprofile or .mycshrc file; for example, if you look in ~seligman/.myprofile, you'll see the following:

Revision 92011-10-31 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/amsterdam/seligman/microboone/LArSoft.
Changed:
<
<
As of 24-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 31-Oct-2011, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Added:
>
>
S2011.10.27
 S2011.08.13 S2011.06.09 S2011.05.23

Revision 82011-08-17 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 24-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
development
Added:
>
>
S2011.08.13
 S2011.06.09 S2011.05.23 S2011.05.18

Revision 72011-06-22 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 24-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
development
Added:
>
>
S2011.06.09
 S2011.05.23 S2011.05.18 S2011.05.02

Revision 62011-05-24 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/amsterdam/seligman/microboone/LArSoft.
Changed:
<
<
As of 17-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 24-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
Added:
>
>
S2011.05.23
 S2011.05.18 S2011.05.02

Revision 52011-05-19 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 11 to 11
 As of 17-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
development
Added:
>
>
S2011.05.18
 S2011.05.02 The list of available releases is a subset of those in the official LArSoft repository at Fermilab. Requests for updates, compilations, and additional releases can be sent to seligman of nevis.columbia.edu
Line: 38 to 39
  If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.02
>
>
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.18
 

Make life easier

Revision 42011-05-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 49 to 49
  /a/share/amsterdam/seligman/microboone/mydev is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.
Added:
>
>

Event display

To use the event display with MicroBooNE events, you have to edit the configuration file:

cp $SRT_PUBLIC_CONTEXT/job/evd.fcl [whatever]
# Edit [whatever]/evd.fcl, changing argoneut_disp to microboone_disp
lar -c [whatever]/evd.fcl [yourfile].root
 

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. \ No newline at end of file

Revision 32011-05-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 17 to 17
 

Where can one run LArSoft

Changed:
<
<
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group.
>
>
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to amsterdam.
 

Setting up the Environment

Revision 22011-05-18 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 8 to 8
  The Nevis copy of the LArSoft installation is currently in /a/share/amsterdam/seligman/microboone/LArSoft.
Changed:
<
<
As of 17-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
>
>
As of 17-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:
 
development
S2011.05.02
Line: 36 to 36
  The above command will set up the development version of LArSoft. If you want to develop or revise code in LArSoft, this is the release you want.
Changed:
<
<
If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the fixed releases. Use the -r option to select a release. For example:
>
>
If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the frozen releases. Use the -r option to select a release. For example:
 
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.02

Revision 12011-05-17 - WilliamSeligman

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

The Nevis copy of the LArSoft installation is currently in /a/share/amsterdam/seligman/microboone/LArSoft.

As of 17-May-2011, the following Fermilab LArSoft releases are maintained at Nevis:

development
S2011.05.02
The list of available releases is a subset of those in the official LArSoft repository at Fermilab. Requests for updates, compilations, and additional releases can be sent to seligman of nevis.columbia.edu

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group.

Setting up the Environment

The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:

# sh-style shell, such as bash or zsh
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh

# csh-style shell, such as tcsh
source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.csh

This will set your $PATH and $LD_LIBRARY_PATH variables to refer to the various packages required by LArSoft. After you execute this command, you can develop code and run jobs.

Selecting a release

The above command will set up the development version of LArSoft. If you want to develop or revise code in LArSoft, this is the release you want.

If you just want to use LArSoft to run jobs, generate event displays, or analyze events, then you probably want to use one of the fixed releases. Use the -r option to select a release. For example:

source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh -r S2011.05.02

Make life easier

You may want to put an alias to the appropriate set-up commands in your .myprofile or .mycshrc file; for example, if you look in ~seligman/.myprofile, you'll see the following:

alias MBD="source /a/share/amsterdam/seligman/microboone/LArSoft/setup/setup_larsoft_nevis.sh; cd /a/share/amsterdam/seligman/microboone/mydev; srt_setup -a" 
/a/share/amsterdam/seligman/microboone/mydev is the test-release directory WilliamSeligman created as described near the end of the editing code page; you would use a directory of your own instead.

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback