Difference between revisions of "DUNE LAr Software Releases"

From DUNE
Jump to navigation Jump to search
 
(110 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
 +
----
 +
----
 +
----
 +
----
 +
==<span style="background:yellow">This page has moved to the [https://wiki.dunescience.org/wiki/DUNE_LAr_Software_Releases DUNE wiki]</span>==
 +
Below is an out-of-date snapshot of the page.
 +
----
 +
----
 +
----
 +
----
 +
 
==Introduction==
 
==Introduction==
  
Line 12: Line 24:
 
A release and all its dependencies may be installed on SLF and Mac machines using the [http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts pullProducts] command:
 
A release and all its dependencies may be installed on SLF and Mac machines using the [http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts pullProducts] command:
 
<code>
 
<code>
−
  ./pullProducts ~/ups slf6 dune-v04_36_01 e9 prof  # Scientific Linux 6
+
  ./pullProducts ~/ups slf6 dune-v06_58_00 e14 prof  # Scientific Linux 6
−
  ./pullProducts ~/ups d14 dune-v04_36_01 e9 prof    # mac Yosemite
+
  ./pullProducts ~/ups slf7 dune-v06_58_00 e14 prof  # Scientific Linux 7
−
  ./pullProducts ~/ups u14 dune-v04_36_01 e9 prof    # ubuntu
+
./pullProducts ~/ups d15 dune-v06_58_00 e14 prof    # mac OS X 10.11 El Capitan
 +
  ./pullProducts ~/ups d16 dune-v06_58_00 e14 prof    # macOS 10.12 Sierra
 
</code>
 
</code>
 
The first three arguments are the directory where the products are to be installed, the OS specifier and the product name and version. The last two are the UPS [https://cdcvs.fnal.gov/redmine/projects/cet-is-public/wiki/AboutQualifiers qualifiers]. The last is the compiler option (prof is nearly optimized but retains the code line numbers) and the first is a colon-separated list of all other qualifiers (e.g. e7:s15, not e7-s15). The available OS and qualifiers for a given release may be deduced from the list of manifests found in the manifest directory for the desired dune release in the [http://scisoft.fnal.gov/scisoft/bundles/dune dune bundle listing].
 
The first three arguments are the directory where the products are to be installed, the OS specifier and the product name and version. The last two are the UPS [https://cdcvs.fnal.gov/redmine/projects/cet-is-public/wiki/AboutQualifiers qualifiers]. The last is the compiler option (prof is nearly optimized but retains the code line numbers) and the first is a colon-separated list of all other qualifiers (e.g. e7:s15, not e7-s15). The available OS and qualifiers for a given release may be deduced from the list of manifests found in the manifest directory for the desired dune release in the [http://scisoft.fnal.gov/scisoft/bundles/dune dune bundle listing].
  
−
The above command will copy many tar files to the current directory and sot it is best to run it in a dedicated directory and not in the product installation area. E.g. something like:
+
Note that versions above are the latest available at the time of writing (typically updated each time a release is made). Older builds are available for some platforms that are no longer supported and the latest of those are:
 +
<code>
 +
./pullProducts ~/ups d13 dune-v06_13_00 e10 prof    # mac OS X 10.9 Mavericks
 +
./pullProducts ~/ups d14 dune-v06-56_00 e14 prof    # mac OS X 10.10 Yosemite
 +
./pullProducts ~/ups u14 dune-v06_06_01 e10 prof    # Ubuntu 14
 +
</code>
 +
These are likely too far out of date to be useful.
 +
 
 +
The above commands will copy many tar files to the current directory and so it is best to run it in a dedicated directory and not in the product installation area. E.g. something like:
 +
 
 +
Before first installation of UPS products, [http://scisoft.fnal.gov/scisoft/bundles/tools/checkPrerequisites checkPrerequisites] can be run to see if all prerequisite packages are installed.
  
 
<code>
 
<code>
Line 25: Line 48:
 
  wget http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts
 
  wget http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts
 
  chmod +x ./pullProducts
 
  chmod +x ./pullProducts
−
  ./pullProducts ~/ups slf6 dune-v04_21_00 e7 prof
+
  ./pullProducts ~/ups slf6 dune-v06_58_00 e14 prof
 
</code>
 
</code>
  
Line 32: Line 55:
 
<code>
 
<code>
 
  cd ~/ups
 
  cd ~/ups
−
  tar xf ~/Downloads/lbnecode-04.20.00-slf6-x86_64-e7-prof.tar.bz2
+
  tar xf ~/Downloads/duneutil-06.56.01-slf6-x86_64-e14-prof.tar.bz2
 +
</code>
 +
 
 +
Users of dunetpc develop at remote sites will sometimes need to do this when the dunetpc dependencies have advanced beyond those in the last dunetpc build. For example the above is needed on 20nov2017.
 +
 
 +
If ups is not installed on your machine, then download and unpack the ups product tar file in this manner. Follow the link to the latest version from the [http://scisoft.fnal.gov/scisoft/packages/ups SciSoft ups package list] and then choose the version appropriate to your machine, e.g. [http://scisoft.fnal.gov/scisoft/packages/ups/v6_0_5/ups-6.0.5-Darwin64bit%2B16.tar.bz2 ups-6.0.5-Darwin64bit+16.tar.bz2] for mac Sierra (Nov 2017).
 +
 
 +
Note that SIP must be disabled and openssl installed (keg-only) for mac El Capitan and Sierra. For more information, see the [https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/_Supported_Platforms_ LArSoft supported platforms page].
 +
 
 +
UPS can be very picky about the OS version for Ubuntu. To install and use the above Ubuntu 14 releases on an Ubuntu 16 or different Ubuntu 14 sub-version machine, first set the UPS version overrride in one of the following ways:
 +
 
 +
* Set the UPS_OVERRIDE environmental variable:
 +
<code>
 +
export UPS_OVERRIDE="-H Linux64bit+3.19-2.19"
 
</code>
 
</code>
  
−
If ups is not installed on you machine, then download and unpack the ups product tar file in this manner. Follow the link to the latest version from the [http://scisoft.fnal.gov/scisoft/packages/ups SciSoft ups package list] and then choose the version appropriate to your machine, e.g. [http://scisoft.fnal.gov/scisoft/packages/ups/v5_2_0/ups-5.2.0-Darwin64bit%2B14.tar.bz2 ups-5.2.0-Darwin64bit+14.tar.bz2] for mac Yosemite.
+
* Add an override file to the product directory:
 +
<code>
 +
echo "-H Linux64bit+3.19-2.19" > <product_directory>/ups_OVERRIDE.`hostname`
 +
</code>
 +
This is specific to each host. If you have a shared volume, you will need to do this for each machine.
  
 
==Using DUNE releases==
 
==Using DUNE releases==
Line 41: Line 81:
 
<code>
 
<code>
 
  source /grid/fermiapp/products/dune/setup_dune.sh
 
  source /grid/fermiapp/products/dune/setup_dune.sh
−
  setup dunetpc v04_21_00 -q e7:prof
+
  setup dunetpc v06_04_00 -q e14:prof
 
</code>
 
</code>
  
Line 47: Line 87:
 
<code>
 
<code>
 
  source /cvmfs/dune.opensciencegrid.org/products/dune/setup_dune.sh
 
  source /cvmfs/dune.opensciencegrid.org/products/dune/setup_dune.sh
−
  setup dunetpc v04_21_00 -q e7:prof
+
  setup dunetpc v06_46_00 -q e14:prof
 
</code>
 
</code>
  
Line 56: Line 96:
 
  setup gitflow
 
  setup gitflow
 
  setup mrb
 
  setup mrb
−
  setup dunetpc v04_21_00 -q e7:prof
+
  setup dunetpc v06_55_00 -q e14:prof
 
</code>
 
</code>
 +
 +
Note that ~/ups/setups will not work with a UPS override file (env override is OK). In that case, use ~/ups/setup.
  
 
In all cases, the ups command can be used to find out which versions of dunetpc are available:
 
In all cases, the ups command can be used to find out which versions of dunetpc are available:
Line 67: Line 109:
 
  "dunetpc" "v04_21_00" "Linux64bit+2.6-2.12" "debug:e7" ""
 
  "dunetpc" "v04_21_00" "Linux64bit+2.6-2.12" "debug:e7" ""
 
</code>
 
</code>
 +
 +
Useful commands:
 +
<code>
 +
  lar -c someconfig.fcl          # Use art event loop to process data according to the instructions in someconfig.fcl
 +
  fcldump someconfig.fcl 5      # Display the highest five levels of configuration in someconfig.fcl
 +
  listlibs type pattern          # Display the full path for all libraries of type "type" (e.g. service or module) whose full path name includes "pattern"
 +
</code>
 +
 +
If you want to develop code, i.e. modify the code in dunetpc, larsoft, etc. or add code from any other repositories, you can use the dune-dev package. Instructions may be found at https://github.com/dladams/dune-dev/blob/master/README.md.
  
 
==Building and installing dune releases==
 
==Building and installing dune releases==
Line 72: Line 123:
 
Build and installation instruction may be found on the [https://cdcvs.fnal.gov/redmine/projects/cvmfs/wiki/CVMFS_Tasks|'''Redmine CVMFS page''']. In particular, this page has the instructions for synchronizing the CVMFS releases with those in the FNAL grid area.
 
Build and installation instruction may be found on the [https://cdcvs.fnal.gov/redmine/projects/cvmfs/wiki/CVMFS_Tasks|'''Redmine CVMFS page''']. In particular, this page has the instructions for synchronizing the CVMFS releases with those in the FNAL grid area.
  
−
The code I (D. Adams) use to build releases is [https://github.com/dladams/dune-larrel dune-larrel]. See [https://github.com/dladams/dune-larrel/blob/master/README.md README.md] in that package or use "<code>larrel -H</code>" for instructions. The product of the build is a tar file and manifest for each dune release combination of OS, version, qualifier, etc.
+
The code I (D. Adams) use to build releases is [https://github.com/dladams/dune-larrel dune-larrel]. See [https://github.com/dladams/dune-larrel/blob/master/README.md README.md] in that package or use "<code>larrel -H</code>" for instructions. The (optional) products of the build include a release tag of dunetpc (in the repository) and a tar file and manifest for each dune release combination of OS, version, qualifier, etc. The latter can be installed in SciSoft as described below.
  
 
Once the release tag is made, then the product must be built for each combination of platform (SLF6, OSX-10.10, ...) and optimization level (prof, debug). An alternative for supported platforms (at presnt SLF6, OSX-10.9 and OSX-10.10) is to use Jenkins: load a KCA certificate in your browser (e.g. with get-cert and import), go to https://buildmaster.fnal.gov/view/LBNE/job/dune-release-build/, click on "Rebuild Last", change the release and submit. The script ~dladams/bin/copyFromJenkins or modified ~dladams/bin/jenkinscp can then be used to copy the product tar files and manifests to the (empty) current directory.
 
Once the release tag is made, then the product must be built for each combination of platform (SLF6, OSX-10.10, ...) and optimization level (prof, debug). An alternative for supported platforms (at presnt SLF6, OSX-10.9 and OSX-10.10) is to use Jenkins: load a KCA certificate in your browser (e.g. with get-cert and import), go to https://buildmaster.fnal.gov/view/LBNE/job/dune-release-build/, click on "Rebuild Last", change the release and submit. The script ~dladams/bin/copyFromJenkins or modified ~dladams/bin/jenkinscp can then be used to copy the product tar files and manifests to the (empty) current directory.
  
−
The above link to Jenkins will only work from inside the FNAL domain. Outside one can create a tunnel to an unused port (here 4444):
+
One or more builds often fail on Jenkins. To retry the failed builds, click on the build date to get to the page for that build and then click on "Matrix Reloaded" and then "Rebuild".
 +
 
 +
The above link to Jenkins will only work from inside the FNAL domain. I have not been able to get things to work properly with VPN or an ssh tunnel. I start a browser on an FNAL machine and send the window over the network. The commands I use:
 
<code>
 
<code>
−
ssh dladams@dunegpvm06.fnal.gov -L 4444:buildmaster.fnal.gov:443
+
get-cert -i
 +
firefox --no-remote
 
</code>
 
</code>
−
and then connect to the port at [https://localhost:4444/view/LBNE/job/dune-release-build/ https://localhost:4444/view/LBNE/job/dune-release-build].
+
or use ~dladams/bin/jenkins.
  
 +
A third option for building the product tar file and manifest is to use the script larsoft/larutils/buildScripts/buildDUNE.sh.
  
 
To install the SLF6 products in the FNAL grid area:
 
To install the SLF6 products in the FNAL grid area:
Line 92: Line 147:
 
To synchronize the CVMFS area with the grid area:
 
To synchronize the CVMFS area with the grid area:
 
<code>
 
<code>
−
  ssh -l cvmfsdune oasiscfs02.fnal.gov
+
  ssh -l cvmfsdune oasiscfs.fnal.gov
 
  dune-sync dune/dunetpc
 
  dune-sync dune/dunetpc
 
</code>
 
</code>
Line 114: Line 169:
 
The command script may be found at /afs/fnal.gov/files/home/room1/dladams/bin/copyToSciSoft or http://scisoft.fnal.gov/scisoft/bundles/tools/copyToSciSoft.
 
The command script may be found at /afs/fnal.gov/files/home/room1/dladams/bin/copyToSciSoft or http://scisoft.fnal.gov/scisoft/bundles/tools/copyToSciSoft.
 
In case of error, log in to scisoftportal.fnal.gov and (very carefully) remove invalid files from <code>/nasroot/SciSoft/bundles/...</code>.
 
In case of error, log in to scisoftportal.fnal.gov and (very carefully) remove invalid files from <code>/nasroot/SciSoft/bundles/...</code>.
 +
 +
After installation, the release should be announced on dune-computing-news AT fnal.gov.
  
 
==More information==
 
==More information==
Line 126: Line 183:
 
** [http://scisoft.fnal.gov/scisoft/packages/lbne_raw_data lbne_raw_data]
 
** [http://scisoft.fnal.gov/scisoft/packages/lbne_raw_data lbne_raw_data]
 
** [http://scisoft.fnal.gov/scisoft/packages/dune_pardata dune_pardata]
 
** [http://scisoft.fnal.gov/scisoft/packages/dune_pardata dune_pardata]
 +
* [https://cdcvs.fnal.gov/redmine/projects/dunetpc/repository dunetpc browser]
 
* Units are cm and ns (Tom, January 2015).
 
* Units are cm and ns (Tom, January 2015).
 
* [http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10280&filename=projectpy.pdf LBNE/DUNE job submission (talk by Tingjjun)]
 
* [http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10280&filename=projectpy.pdf LBNE/DUNE job submission (talk by Tingjjun)]
Line 134: Line 192:
 
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/Getting_LArSoft Getting LArSoft]
 
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/Getting_LArSoft Getting LArSoft]
 
* [http://scisoft.fnal.gov/scisoft/bundles/larsoft SciSoft bundles]
 
* [http://scisoft.fnal.gov/scisoft/bundles/larsoft SciSoft bundles]
 +
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/LArSoft_release_list Release notes]
 
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/issues Issues]
 
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/issues Issues]
 
* [mailto:larsoft@fnal.gov LArSoft mailing list].
 
* [mailto:larsoft@fnal.gov LArSoft mailing list].
−
* [https://cdcvs.fnal.gov/redmine/projects/artextensions/wiki/SeedService SeedService]
+
* [https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/LArSoft_git_Guidelines Git guidelines]
 +
* [https://cdcvs.fnal.gov/redmine/projects/artextensions/wiki/SeedService SeedService] (See also the [https://indico.fnal.gov/getFile.py/access?contribId=7&resId=0&materialId=slides&confId=11915 April 2016 talk by Gianluca])
 +
* [http://larsoft.org/list LArSoft algorithm documentation]
 +
* LArSoft documents in INSPIRE: [http://larsoft.org/links-to-documents Instructions], [https://inspirehep.net/youraccount/login Log in], [https://inspirehep.net/search?ln=en&cc=LArSoft+Notes&p=&action_search=Search, Search]
  
 
Art:
 
Art:
Line 146: Line 208:
 
* [https://cdcvs.fnal.gov/redmine/projects/messagefacility/wiki/Using_MessageFacility Message facility]
 
* [https://cdcvs.fnal.gov/redmine/projects/messagefacility/wiki/Using_MessageFacility Message facility]
 
* [https://cdcvs.fnal.gov/redmine/projects/art/wiki/Guide_to_writing_and_using_services Services wiki]
 
* [https://cdcvs.fnal.gov/redmine/projects/art/wiki/Guide_to_writing_and_using_services Services wiki]
 +
* [https://cdcvs.fnal.gov/redmine/projects/art/wiki/Guide_to_writing_and_using_tools Art tools]
 
* [https://cdcvs.fnal.gov/redmine/projects/art/issues Issues]
 
* [https://cdcvs.fnal.gov/redmine/projects/art/issues Issues]
 
* [https://cdcvs.fnal.gov/redmine/projects/cetbuildtools/wiki cetbuildtools defines many useful CMake commands]
 
* [https://cdcvs.fnal.gov/redmine/projects/cetbuildtools/wiki cetbuildtools defines many useful CMake commands]
  
 
Building:
 
Building:
 +
* [https://cdcvs.fnal.gov/redmine/projects/mrb/wiki/MrbRefereceGuide mrb reference guide]
 
* [https://cdcvs.fnal.gov/redmine/projects/lbnecode/wiki/_Tutorial_ LBNE tutorial]
 
* [https://cdcvs.fnal.gov/redmine/projects/lbnecode/wiki/_Tutorial_ LBNE tutorial]
 
* My package to simplify building is [https://github.com/dladams/dune-dev dune-dev]
 
* My package to simplify building is [https://github.com/dladams/dune-dev dune-dev]

Latest revision as of 15:21, 12 December 2017

This page has moved to the DUNE wiki

Below is an out-of-date snapshot of the page.

Introduction

This page describes recent releases of DUNE software for simulation and reconstruction of event data from the LAr TPCs and associated photon and muon detectors. The software is released in the dunetpc package. Earlier releases in the lbnecode package are described on this other page.

Finding and downloading DUNE releases

Releases of dunetpc (and other DUNE products) are installed at FNAL at

/grid/fermiapp/products/dune

and on CVMFS at

/cvmfs/dune.opensciencegrid.org/products/dune

A release and all its dependencies may be installed on SLF and Mac machines using the pullProducts command: 

./pullProducts ~/ups slf6 dune-v06_58_00 e14 prof   # Scientific Linux 6
./pullProducts ~/ups slf7 dune-v06_58_00 e14 prof   # Scientific Linux 7
./pullProducts ~/ups d15 dune-v06_58_00 e14 prof    # mac OS X 10.11 El Capitan
./pullProducts ~/ups d16 dune-v06_58_00 e14 prof    # macOS 10.12 Sierra

The first three arguments are the directory where the products are to be installed, the OS specifier and the product name and version. The last two are the UPS qualifiers. The last is the compiler option (prof is nearly optimized but retains the code line numbers) and the first is a colon-separated list of all other qualifiers (e.g. e7:s15, not e7-s15). The available OS and qualifiers for a given release may be deduced from the list of manifests found in the manifest directory for the desired dune release in the dune bundle listing.

Note that versions above are the latest available at the time of writing (typically updated each time a release is made). Older builds are available for some platforms that are no longer supported and the latest of those are: 

./pullProducts ~/ups d13 dune-v06_13_00 e10 prof    # mac OS X 10.9 Mavericks
./pullProducts ~/ups d14 dune-v06-56_00 e14 prof    # mac OS X 10.10 Yosemite
./pullProducts ~/ups u14 dune-v06_06_01 e10 prof    # Ubuntu 14

These are likely too far out of date to be useful.

The above commands will copy many tar files to the current directory and so it is best to run it in a dedicated directory and not in the product installation area. E.g. something like:

Before first installation of UPS products, checkPrerequisites can be run to see if all prerequisite packages are installed. 

mkdir ~/upstars
cd ~/upstars
wget http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts
chmod +x ./pullProducts
./pullProducts ~/ups slf6 dune-v06_58_00 e14 prof

Tar files for individual product versions (including dunetpc) may also be downloaded directly from the SciSoft product area. To install a product, simply untar these in the local products area: 

cd ~/ups
tar xf ~/Downloads/duneutil-06.56.01-slf6-x86_64-e14-prof.tar.bz2

Users of dunetpc develop at remote sites will sometimes need to do this when the dunetpc dependencies have advanced beyond those in the last dunetpc build. For example the above is needed on 20nov2017.

If ups is not installed on your machine, then download and unpack the ups product tar file in this manner. Follow the link to the latest version from the SciSoft ups package list and then choose the version appropriate to your machine, e.g. ups-6.0.5-Darwin64bit+16.tar.bz2 for mac Sierra (Nov 2017).

Note that SIP must be disabled and openssl installed (keg-only) for mac El Capitan and Sierra. For more information, see the LArSoft supported platforms page.

UPS can be very picky about the OS version for Ubuntu. To install and use the above Ubuntu 14 releases on an Ubuntu 16 or different Ubuntu 14 sub-version machine, first set the UPS version overrride in one of the following ways:

  • Set the UPS_OVERRIDE environmental variable:

export UPS_OVERRIDE="-H Linux64bit+3.19-2.19"

  • Add an override file to the product directory:

echo "-H Linux64bit+3.19-2.19" > <product_directory>/ups_OVERRIDE.`hostname`

This is specific to each host. If you have a shared volume, you will need to do this for each machine.

Using DUNE releases

Scripts to set up the FNAL and CVMFS releases are provided. To set up to use release 4.21 from the FNAL installation: 

source /grid/fermiapp/products/dune/setup_dune.sh
setup dunetpc v06_04_00 -q e14:prof

To use the CVMFS installation of the same release: 

source /cvmfs/dune.opensciencegrid.org/products/dune/setup_dune.sh
setup dunetpc v06_46_00 -q e14:prof

For local installation of all products in ~/ups, set up with something like the following: 

source ~/ups/setup      # Or source ~/ups/setups
setup git
setup gitflow
setup mrb
setup dunetpc v06_55_00 -q e14:prof

Note that ~/ups/setups will not work with a UPS override file (env override is OK). In that case, use ~/ups/setup.

In all cases, the ups command can be used to find out which versions of dunetpc are available: 

fnal:lbne> ups list -aK+ dunetpc 
"dunetpc" "v04_20_00" "Linux64bit+2.6-2.12" "e7:prof" "" 
"dunetpc" "v04_20_00" "Linux64bit+2.6-2.12" "debug:e7" "" 
"dunetpc" "v04_21_00" "Linux64bit+2.6-2.12" "e7:prof" "" 
"dunetpc" "v04_21_00" "Linux64bit+2.6-2.12" "debug:e7" ""

Useful commands: 

 lar -c someconfig.fcl          # Use art event loop to process data according to the instructions in someconfig.fcl
 fcldump someconfig.fcl 5       # Display the highest five levels of configuration in someconfig.fcl
 listlibs type pattern          # Display the full path for all libraries of type "type" (e.g. service or module) whose full path name includes "pattern"

If you want to develop code, i.e. modify the code in dunetpc, larsoft, etc. or add code from any other repositories, you can use the dune-dev package. Instructions may be found at https://github.com/dladams/dune-dev/blob/master/README.md.

Building and installing dune releases

Build and installation instruction may be found on the Redmine CVMFS page. In particular, this page has the instructions for synchronizing the CVMFS releases with those in the FNAL grid area.

The code I (D. Adams) use to build releases is dune-larrel. See README.md in that package or use "larrel -H" for instructions. The (optional) products of the build include a release tag of dunetpc (in the repository) and a tar file and manifest for each dune release combination of OS, version, qualifier, etc. The latter can be installed in SciSoft as described below.

Once the release tag is made, then the product must be built for each combination of platform (SLF6, OSX-10.10, ...) and optimization level (prof, debug). An alternative for supported platforms (at presnt SLF6, OSX-10.9 and OSX-10.10) is to use Jenkins: load a KCA certificate in your browser (e.g. with get-cert and import), go to https://buildmaster.fnal.gov/view/LBNE/job/dune-release-build/, click on "Rebuild Last", change the release and submit. The script ~dladams/bin/copyFromJenkins or modified ~dladams/bin/jenkinscp can then be used to copy the product tar files and manifests to the (empty) current directory.

One or more builds often fail on Jenkins. To retry the failed builds, click on the build date to get to the page for that build and then click on "Matrix Reloaded" and then "Rebuild".

The above link to Jenkins will only work from inside the FNAL domain. I have not been able to get things to work properly with VPN or an ssh tunnel. I start a browser on an FNAL machine and send the window over the network. The commands I use: get-cert -i firefox --no-remote or use ~dladams/bin/jenkins.

A third option for building the product tar file and manifest is to use the script larsoft/larutils/buildScripts/buildDUNE.sh.

To install the SLF6 products in the FNAL grid area: 

ssh dune@dunegpvm03.fnal.gov
cd /grid/fermiapp/products/dune
tar xf ~dladams/reltars/dunetpc-05.05.00-slf6-x86_64-e9-prof.tar.bz2

To synchronize the CVMFS area with the grid area: 

ssh -l cvmfsdune oasiscfs.fnal.gov
dune-sync dune/dunetpc

Replace dunetpc with dune_pardata, duneutil or lbne_raw_data to update any of those products. The script dune-sync is installed on the oasis server and may also be found at https://github.com/dladams/dune-larrel/blob/master/dune-sync.

Each synchronization generates a log in $HOME/logs and a CVMFS server tag. Periodically remove these. The tags may be listed with 

cvmfs_server tag dune.opensciencegrid.org

and tags removed with 

cvmfs_server tag -r TAG dune.opensciencegrid.org

To copy each product tar file to SciSoft and install the corresponding manifest: 

 copyToSciSoft /afs/fnal.gov/files/home/room1/dladams/reltars/dunecode-04.20.00-slf6-x86_64-e6-prof.tar.bz2
 copyToSciSoft workdir/manifests/dune-04.21.00-Linux64bit+2.6-2.12-e7-prof_MANIFEST.txt

The command script may be found at /afs/fnal.gov/files/home/room1/dladams/bin/copyToSciSoft or http://scisoft.fnal.gov/scisoft/bundles/tools/copyToSciSoft. In case of error, log in to scisoftportal.fnal.gov and (very carefully) remove invalid files from /nasroot/SciSoft/bundles/....

After installation, the release should be announced on dune-computing-news AT fnal.gov.

More information

DUNE:

LArSoft:

Art:

Building:

FHICL:

Release building:

35 ton prototype:

LBNE 35-ton Data Model and Reconstruction

DUNE and LarSoft geometry

LBNE code repositories and their browsers

LBNE jobs may be submitted using the package lbneutil described in a talk by Tingjun.

LBNE geometries are summarized here.

The reconstruction used in the 35-ton simulation is specified in lbnecode/source/fcl/lbne35t/reco/standard_reco_lbne35t.fcl.

Data production

  • The 35-ton MC data samples are described here.
  • MCC5

GENIE event generator


Results from LbTupler

Retrieved from "https://dune.bnl.gov/w/index.php?title=DUNE_LAr_Software_Releases&oldid=2190"