- 1 Welcome to the DUNE Wiki!
- 2 Detectors, Physics, planning, general interest
- 3 ProtoDUNE Cold Electronics Testing
Welcome to the DUNE Wiki!
Questions or comments about this Wiki? Please write to Maxim and Brett (potekhin AT bnl.gov, bv AT bnl.gov). See the Help entry of the navigation bar on the left for more guidance about this wiki.
If you just joined DUNE, welcome aboard! Information for new members.
DUNE Institutions and people
- Main DUNE page
- Speakers' Committee
- Institution category (add your institution here)
- Collaboration Database
Select publications by and about DUNE are collected in the Publications topic.
Useful CERN Links:
- CERN Neutrino Platform
- CENF (CERN Neutrino Platform Work Pages)
- CERN Registration Procedure for new CENF members, which include CERN users (on site) and those who plan to access CERN computing facilities remotely
CERN Account Management
Once a membership is established, the account may be configured (e.g. one can create secondary and/or service accounts and apply for group membership at the CERN Account Management Page.
Detectors, Physics, planning, general interest
DUNE Far Detectors
Current and future prototypes
- 35t Liquid Argon Prototype (completed operations in 2016)
- CERN Prototypes (Single and Dual-Phase) (commissioning in 2017, data taking in 2018)
DUNE and its predecessor LBNE
- DUNE (formerly LBNE) in the news
- The Long-Baseline Neutrino Experiment: Exploring Fundamental Symmetries of the Universe
- P5 report
- Document Database at FNAL (a.k.a. DocDB). Password is required.
- http://lbne2-docdb.fnal.gov:8080/cgi-bin/DocumentDatabase LBNE (archive DB)
- http://docs.dunescience.org:8080/cgi-bin/DocumentDatabase DUNE (current DB)
- "Redmine". An integrated project and content management system used at FNAL (LBNE pages).
- DocDB 7463: ICARUS-LBNE Meetings and Documents.
- Data Volume and Rates (under construction)
- INT Workshops (2010)
- Intensity Frontier Experiments (Collection of IF Links)
- SHIP (proposed beam dump experiment at CERN SPS)
- FIFE - Fabric for Frontier Experiments. A project at FNAL aiming to implement collaborative and shared solutions, mainly for the Intensity Frontier Experiments.
- A Short-Baseline Experiment Proposal
Please visit the DUNE Computing topic. Some direct links:
ProtoDUNE Cold Electronics Testing
- FE warm testing should continue with the A series ASICs on hothdaq2
- ADC cold single socket testing should continue with the D series ASICs on hothdaqs 4 &5
- Brian/Justin will be working on quad socket ADC development on hothdaq3
- Matt B will be testing CE boxes on hothdaq1
- Oscillator and flash testing complete for now (big thank you to Jim for flash testing the past two days and to Arbin/Brian for getting the flash setup operational so quickly)
If we run out of labeled A or D series ASICs, there are pens in the cabinet. Please self-certify as having good handwriting if you are going to label chips. I suggest doing no more than 50-100 at a time as handwriting deteriorates with fatigue.
Shift Sign-Up Calendar
Please sign shifts in the above google calendar and notify Shift co-ordinators and Shift leaders by sending them email. New shifter needs to take required trainings, sign up the ESR (Experiment Safety Review) and take training before shift.
Below are the trainings required to work on Cold Electronics Testing
- Cybersecurity (GE-CYBERSEC)
- Physics department ALARA (PO-RADALARA-W)
- Cryogen Safety (HP-OSH-025)
In addition to these trainings, shifter needs to get BNL Domain Account (Windows) to sign up the ESR
Every shifter is required to fill the above google sheet during shift. Select the appropriate shift as per your shift station (hothdaq1, hothdaq2, hothdaq3 ans so..on) and fill all the fields as listed in the sheet. Write proper and detailed description of the Run in the "Notes" column, for example, if run fails, give full description of error occurred at what testing stage.
Shift leader is required to add daily shift summary at end of the shift in the above link. Along-with the shift summary, system experts should also add any changes occurring in testing code and releases etc. It is easy to get account in the e-log is anyone else interested.