Welcome to the Membrane Cryostat (35 Ton) working group wiki on the FNAL redmine site. We are the DUNE collaboration working group that will support the construction, operation and data analysis of the 35-Ton LAr-TPC prototype currently being built in the PC4 area at Fermilab. The 35-Ton Phase II coordinators are Alan Hahn, Mark Convery and Michelle Stancari.
For more information about the 35-Ton prototype hardware, you can go to https://sharepoint.fnal.gov/project/lbne/LBNE%20at%20Work/SitePages/Home.aspx.
A poster describing the status of 35-Ton work (as of May 2014) can be found in the "Files" section of this project.Weekly meetings are
- 10-11 CT Wednesdays for Hardware/Installation/Commissioning/Run Coordination (Theory Room WH3NW and Readytalk)
- 11-12 CT Wednesdays for Offline/Reconstruction/Simulation/Analysis (Theory Room WH3NW and Readytalk)
E-log shift schedule tool
DRC (deputy run coordinator) schedule
Cryo Expert List and Contact Details
To-Do List Jan 08th - Updated Jan 14th, 2016
Cooldown Period - please run TPC calibration data-taking script every ~30 minutes, see instructions here.
Old, broken link to E-log shift schedule tool
Getting Started on 35-Ton Analysis¶
Analysis of DUNE far detector data uses the LArSoft package.[[https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki]]
As a new analyst, your first goal should be running an example job with 35-Ton geometry. The steps for doing this are described in the LArSoft Redmine Wiki, which we link to here. This description is for running using Fermilab computers. Some institutions may have LArSoft running on their local clusters. But, in any case, it's probably better to start with the Fermilab machines. We assume that you have some familiarity with UNIX, C++ and Root. If not, it's probably best to seek out some tutorials on those topics before diving into LArSoft. There are lots of tutorials on the LarSoft wiki above.
We recommend the following steps:
- Setup your Fermilab Account[[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/Fermilab_Computing_Access]]
- Log in to lbnegpvm. Most people use ssh with the "-Y" option, and you might want to log in to lbnegpvm01.fnal.gov first. Then, you can get fancier and use the load-balanced nodes.[[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/Load_Balanced_Access_to_General_Purpose_VMs]]
- Try some of the Getting Started Examples
These are listed in DocDB 7381, which is updated on regular basis by Mark and Michelle.
Hardware, Online and Operations Tasks¶
These are listed in DocDB 7682, which is updated on a less regular basis by Mark and Michelle.
Keep up to date with commissioning and operations using the e-log:
Phone at PC4: ×3600 The phone is on the desks near LAPD and on the top of the 35T cryostat.
Phone at the electronics test area at DAB: x4716
Phone at the ROC-West control room: x5449
In August, 2013, the APA geometry for the 35-Ton prototype was changed from having 3 APAs to 4. All serious simulation and reconstruction should use the 4-APA configuration. Here's a link describing all lbne geometries: https://cdcvs.fnal.gov/redmine/projects/lbne-fd-sim/wiki/LBNE_Geometries
The latest geometry version is lbne35t4apa_v3. Here is a description in progress.
- For instructions on accessing 35-ton data and Monte Carlo samples stored in SAM
- Older data samples, up to Nov. 2015 are indexed here
Data Files for the Vertical Slice Test, 2014, 2015
- Older MC samples (MCC 4.0 and before) are linked here:
- Good run list from the 35-ton Cosmic Run is here (will be updated)
FTS/SAM Status links¶
- Online gateway machines lbne35t-gateway02.fnal.gov is the data transfer node, and lbne35t-gateway04.fnal.gov is the spare. Monitoring pages are linked below.
- FTS transferring files from the dropboxes on dCache and BlueArc. No longer used for raw data, but
used for MC production.
35-Ton Event Display¶
Here's a link to instructions for using Chao Zhang's event display
Online <--> offline channel map¶
The channels numbers when read out by the DAQ are not the same as those in LArSoft. See this
page for relevant maps: Channel map
There is an additional mapping for photon detectors which more closely resembles, but does not exactly match, the setup in Larsoft. It is described here: PD Channel Map
More Tutorials, Documentation, and Forums¶
ART User's page https://web.fnal.gov/project/ArtDoc/Pages/art-users.aspx
ART workbook and User's Guide https://web.fnal.gov/project/ArtDoc/Pages/workbook.aspx
Getting Started Examples
Dump the wire geometry to a text file
Getting the run and event number from an art-formatted file
Simulate horizontal-ish muons that trigger the counters on the cryostat walls
Using the Cosmic Tracker
Using the PANDORA Reconstruction
Using Project Python Job Submission
Tools for debugging and profiling code
Schematic cartoon of Long Drift Volume TPCs
Using TMinuit in an Analysis Module
lbnecode wiki https://cdcvs.fnal.gov/redmine/projects/lbnecode/wiki/_Tutorial_
Photon Simulation Tutorial
Data compression and zero suppression
Using the stitchersplitter module
Ganglia Monitoring of the DAQ nodes http://lbne35t-gateway01.fnal.gov/ganglia/
TPC Specific FEMB Configuration Check
Obsolete svn-based instructions - for historical interest only!¶
- Setup LArSoft [[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/Using_LArSoft_on_the_GPVM_nodes]]
- Setup your test release [[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/Getting_started_with_an_analysis_task#Set-up-a-working-directory]]
- Generate some single muon events using 35-Ton Geometry [[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/Go_create_some_muons]]
Instead of copying over prodsingle.fcl and editing it as suggested, you could also just copy over prodsingle_lbne35t.fcl. Take a look at the root files produced to see the MC-level quantities
- Run a reconstruction job on the muons you made [[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/_recon]] Once again, take at the root files to see some reco-level quantities
- Try running the Event Display on your events [[https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki/EVD_]] In my experience, this is unusably slow when using Xwindows from offsite to log into Fermilab, but there may be other ways to do it.
- Congratulations, you've run your first sim and reco LArSoft jobs. Now continue with the general LArSoft exercises to learn how to do real work.