Difference between revisions of "Main Page"

From DUNE
Jump to navigation Jump to search
 
(157 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= LBNE =
+
= Welcome to the DUNE@BNL Wiki! =
== What are these pages? ==
 
This is the provisional location for documentation created and used by the LBNE group at BNL. These pages are created and maintained using Mediawiki.
 
  
== Getting started with Mediawiki ==
+
The official DUNE wiki is at https://wiki.dunescience.org/ (login required).
* [http://www.mediawiki.org/wiki/Help:Formatting Formatting text in Mediawiki (markup)]
 
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
 
* [//meta.wikimedia.org/wiki/Help:Contents User's Guide] - information on using the wiki software.
 
  
== Useful links ==
+
This wiki is intended to hold info relevant to BNL involvement in DUNE. Most questions regarding the content and design should be directed to Brett Viren and/or Maxim Potekhin.
* [http://lbne.fnal.gov/ Official LBNE page at FNAL]
 
* [http://lbne2-docdb.fnal.gov:8080/cgi-bin/DocumentDatabase LBNE Document Database at FNAL (a.k.a. '''DocDB''')]. Password is required. There are many ways to query the system, and the most widely used is by the unique ID number assigned to the document by DocDB.
 
* [https://cdcvs.fnal.gov/redmine/projects/lbne "Redmine"]. An integrated project and content management system used at FNAL.
 
* [https://sharepoint.fnal.gov/org/scd/fife/SitePages/Home.aspx FIFE - Fabric for Frontier Experiments]. A project at FNAL aiming to implement collaborative and shared solutions, mainly for the Intensity Frontier Experiments.
 
  
= LBNE Computing =
+
= Institutions, people and publications =
== Introduction ==
+
* [http://www.dunescience.org/ Main DUNE page]
Design, development, testing, commissioning, and operational support of software and systems for the LBNE
+
* [https://web.fnal.gov/collaboration/DUNE/SitePages/Speakers%20Committee.aspx Speakers' Committee]
experiment represent an immense undertaking. It consists of many individual pieces, some independent and
+
* [[:Category:Institution|Institution category]] (add your institution [[Form:Institution|here]])
some closely related to each other, as well as challenging integration tasks. The resources for creation and
+
* [https://dune.bnl.gov/people Collaboration Database]
maintenance of the software and services for the experiment are limited and are expected to be so for the
+
* [[Publications]] - select publications by and about DUNE
lifetime of the project and of the experiment. In that regard, the primary limiting resource is personnel, both
 
scientific and professional.
 
  
On the other hand, modern software frameworks, tools, and methodologies allow a variety of software and
+
= CERN =
computing tasks (infrastructure, science software tools, etc) to be optimally divided among collaborators at
+
* [http://home.cern/about/experiments/cern-neutrino-platform CERN Neutrino Platform]
multiple locations. Improved quality and efficiency of the software development and better maintenance are
+
* [http://cenf.web.cern.ch/ CENF] (CERN Neutrino Platform Work Pages)
achieved through the use of modern revision control, continuous integration, collaborative software systems, and
+
* [http://cenf.web.cern.ch/basic/registration-procedure CERN Registration Procedure] for new CENF members, which include CERN users (on site) and those who plan to access CERN computing facilities remotely
where possible, extensive re-use of code developed for other projects. Optimally designed software distribution,
+
* [[CERN Prototype | *Archive* DUNE Far Detector prototypes at CERN (protoDUNE)]]
Workload Management and Data Handling systems also increase efficiencies in operations area across the globally
+
* [https://account.cern.ch/account/ CERN Account Management Page] 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)
distributed computing platform of LBNE.
 
  
In order to increase efficiencies and better utilize the resources and pool of talent available to LBNE, we
+
= DUNE Far Detectors =
organize the breadth of the LBNE software and computing effort as a set of distinct but interrelated work areas:
+
* [[Installation and Integration ]]
 +
* [[SP - Cold Electronics]]
  
* Physics Analysis/Physics Working Groups (PWG), covering various directions and areas of the physics analysis based on the data collected by LBNE. This group is responsible for the science deliverables. ''Leader: Jon Urheim.''
+
= ProtoDUNE Cold Electronics Testing =
 +
Materials kept on a separate page: [[protoDUNE CE test]]
  
* Physics Tools Group (PT), which is responsible for creation and maintenance of software modules and data required by the R&D work in the design stage of the experiment, and later the analysis activity of the Physics Working groups, such as simulation applications, background characterization analysis, tracking and event reconstruction algorithms etc. ''Leader: Thomas Junk.''
+
= Archive and Reference =
 +
== DUNE prototypes ==
 +
* [[35t_Test|35t Liquid Argon Prototype]] (completed operations in 2016)
 +
* [[CERN Prototype | CERN Prototypes (Single and Dual-Phase)]] (archive)
  
* Software and Computing Organization (S&C), which develops and maintains a set of core services, systems, applications and policies necessary for implementation of the Physics Tools and higher-level analysis software. Examples include data distribution and access systems, optimal database access, code repositories and revision control, software frameworks etc. ''Co-Leaders: Maxim Potekhin, Liz Sexton-Kennedy.''
+
== DUNE and its predecessor LBNE ==
 +
* [http://lbne.fnal.gov/news.shtml DUNE (formerly LBNE) in the news]
 +
* [http://inspirehep.net/record/1245018?ln=en The Long-Baseline Neutrino Experiment: Exploring Fundamental Symmetries of the Universe]
 +
* [http://science.energy.gov/~/media/hep/hepap/pdf/May%202014/FINAL_P5_Report_Interactive_060214.pdf P5 report]
 +
<!-- * [https://sharepoint.fnal.gov/project/lbne/LBNE%20at%20Work/SitePages/Home.aspx "LBNE at Work", a useful compendium of links] -->
 +
* 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)
 +
* [https://cdcvs.fnal.gov/redmine/projects/lbne "Redmine"]. An integrated project and content management system used at FNAL (LBNE pages).
 +
* {{DocDB|7463|DocDB 7463}}: ICARUS-LBNE Meetings and Documents.
 +
* [https://lbne.bnl.gov/wiki/Data_Rates Data Volume and Rates] (archive)
  
* Data Acquisition and Online Systems Group (DAQ), responsible for the development, deployment and maintenance of the systems which collect data from the various detector elements, slow controls, interfaces with conditions databases and accelerator complex data network. ''Leader: Giles Barr.''
+
== Other Experiments ==
 
+
* [http://www.int.washington.edu/talks/WorkShops/int_10_2b/ INT Workshops (2010)]
The purpose of this structure is to improve efficiency by avoiding unnecessary duplication of effort across
+
* [http://www-microboone.fnal.gov/ MicroBooNE]
various sub-projects, achieve economies of scale and create an agile and productive environment for the scientists
+
* [[Intensity Frontier Experiments]] (Collection of IF Links)
to work in. As one example, database services, their access methods and many other aspects of database
+
* [http://www.uvic.ca/science/physics/vispa/research/theory/Bonivento.pdf SHIP] (proposed beam dump experiment at CERN SPS)
technology will be made available to PT by personnel working within the S&C (and with their liaisons at
+
* [https://sharepoint.fnal.gov/org/scd/fife/SitePages/Home.aspx FIFE - Fabric for Frontier Experiments]. A project at FNAL aiming to implement collaborative and shared solutions, mainly for the Intensity Frontier Experiments.
participating sites), without the need for each individual group to set up its own database shop. Likewise, a
+
* [http://arxiv.org/abs/1503.01520 A Short-Baseline Experiment Proposal]
consistent and well-managed methodology of building, validation and distribution of software is highly beneficial
 
to all segments of LBNE. Last but not least, this structure will also allow us to foster collaboration within LBNE,
 
by implementing efficient shared and reusable solutions.
 
 
 
== Documents and Planning ==
 
Our approach to planning is as follows:
 
* The Collaboration forms a set of Software and Computing Requirements, i.e. a well defined set of expectations of what its computing sector must deliver.
 
* A Computing Model is created, which is a combination of policies, organizational principles and technology guidelines which are brought together for optimal fulfillment of the Requirements.
 
* In order to realize the Computing Model, we develop the Implementation Plan, based on which practical documents such as FWP and WBS can be created.
 
[[Computing Effort Organization]]
 
[[Computing Model]]
 
 
 
 
 
 
 
<!-- * [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
 
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
 
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language] -->
 

Latest revision as of 16:41, 21 December 2017

Welcome to the DUNE@BNL Wiki!

The official DUNE wiki is at https://wiki.dunescience.org/ (login required).

This wiki is intended to hold info relevant to BNL involvement in DUNE. Most questions regarding the content and design should be directed to Brett Viren and/or Maxim Potekhin.

Institutions, people and publications

CERN

DUNE Far Detectors

ProtoDUNE Cold Electronics Testing

Materials kept on a separate page: protoDUNE CE test

Archive and Reference

DUNE prototypes

DUNE and its predecessor LBNE

Other Experiments