Difference: LArSoftAtNevis (15 vs. 16)

Revision 162015-02-04 - WilliamSeligman

Line: 1 to 1

META TOPICPARENT	name="WilliamSeligman"

LArSoft at Nevis

Line: 17 to 17

After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific scripts, of course).

Changed:

<
<

DIstribution

>
>

Distribution

The MicroBooNE software directories are imported to Nevis via CVMFS. You can browse the files at /cvmfs/oasis.opensciencegrid.org/microboone on any of the Nevis Neutrino systems; they all have CVMFS installed. We automatically mirror Fermilab's releases.

Line: 124 to 124

Setting up ROOT and Geant4

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. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, check that there are no setup commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

>
> The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to use environment modules (the module command) to set up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, check that there are no setup or module commands in any of your shell initialization files like ~/.bashrc, 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. \ No newline at end of file

View topic | History: r18 < r17 < r16 < r15 | More topic actions...