DoSSiER: Database of Scientific Simulation and Experimental Results

Overview

The Geant4 and Genie collaborations regularly perform validation and regression tests. The results are stored in a central repository and can be easily accessed via a web application or a web service. The picture below shows the components of DoSSiER: Database of Scientific Simulation and Experimental Results. In the following we will describe these components and the technology choices we made.

Validation database

The Validation Database is a relational database that stores plots in form of images with meta-data, simulation results as multidimensional histograms, and experimental data as arrays. Images of final plots (gif, jpeg etc.) are stored as blobs (binary large objects) while histograms and data points are stored as arrays in the database. The meta-data describes the test, lists references to the experimental data, as well as other parameters that describe the test (e.g. software version, beam particle, beam energy/momentum,reaction, target material, secondaries etc.). In case the mandatory parameters are not sufficient to completely describe a test one can supply additional tags to provide more information. As database system we chose PostgreSQL which is a powerful, open source object-relational database system. Notes about installing postgres, creating the necessary database users etc. can be found here.

Java API

The java API is based on the data access object ( DAO) software design pattern and provides an abstract interface to the database. Both the web service and the web application are build on top of the java API. The code can be found in gitlab. The project is configured as a maven project and we use the netbeans IDE for development. For information about how to configure netbeans and how to check out the Java API and build it have a look here.

Web Application

The web application offers easy to navigate menus, to interactively select and overlay compatible data. Compatible data means the results belong to the same type of test and we are comparing the same observable and measurement variables. The application logic is such that only compatible data can be
selected via the provided menus. The web application also provides security and authentication to grant access to groups of functions and data that are internal to the Geant4 or Genie collaboration, e.g. viewing results from development releases, upload of new tests and modification of selected tests. The Web Application is based on Java Platform, Enterprise Edition ( Java EE) and utilizes the PrimeFaces open source JSF (Java Server Faces) component suite. The database is accessed using the classes provided by the Java API. It is deployed on a GlassFish application server. A GlassFish application server is included in the Netbeans distribution we are using, allowing the developer to locally deploy, debug and view the web application on the machine or laptop used for development. For historical reasons the project is called SimVa in gitlab. The code can be found here. Like the Java API the project is configured as a maven project. To connect to the database we are making use of Connection Pools which are started automatically when the Web Application server is started instructions how to configure the connection pools on the glassfish server can be found here.

Web Service (WebAPI) DoSSiER _WS

The web service is a JAX-RS (part of JavaEE), Restful (Representational State Transfer (REST)) Web service which allows programmatic access to the database and can be used by any computing language that can do http requests and parse xml/json files. Programmatic examples exist in java, C++, python, .. The data extracted from the database is formatted either as json or xml. Link to project in gitlab

C++ API: DbReader

The C++ API provides programatic read access to the database. It can be configured to either access the database via the web service or directly access the database using sql. Link to the project in gitlab

Links to relevant web sites

Link to indico meetings: https://indico.cern.ch/category/2948/

e-group archive (geant4-fnaldb-work): https://groups.cern.ch/group/geant4-fnaldb-work/default.aspx

JIRA story (requires geant4-jira account): https://jira-geant4.kek.jp/browse/DEV-192

Installing and configuring netbeans/jdk: https://twiki.cern.ch/twiki/bin/view/Geant4/NetbeansConfiguration

Link to glassfish server installation and configuration including creating of users and connection pools: https://twiki.cern.ch/twiki/bin/view/Geant4/ServerConfiguration

Configuring the PostgreSQL database: https://twiki.cern.ch/twiki/bin/view/Geant4/DatabaseConfiguration

Securing the web service and web application: https://twiki.cern.ch/twiki/bin/view/Geant4/SecuringWebServiceAndWebApplication

File upload via the maven command line: https://twiki.cern.ch/twiki/bin/view/Geant4/FileUploadViaMavenCommandLine

Link to gitlab: https://gitlab.cern.ch/groups/PhysicsValidationDB

Framework Development - Notes, Discussions, etc.

Use cases

• Use case 1 - Geant4 release validation for Hadronic models

Geant4 validation experts want to compare Geant4 predictions from one or more releases vs experimental data. Geant4 applications are written entirely in C++, and use Root (also C++) for as comparison/display tools or use the new g4analysis interface layer (w/ support for few persistency format). The data should come (via download) from a single, centrally available source (repository), open to public for a read-only access. The validation experts want to be able to work entirely in a single programming language which is C++.

Agreed solution: https://groups.cern.ch/group/geant4-fnaldb-work/Lists/Archive/Flat.aspx?RootFolder=%2Fgroup%2Fgeant4%2Dfnaldb%2Dwork%2FLists%2FArchive%2Fminute%20of%20todays%20meeting&FolderCTID=0x01200200F388B01EEEB87441A00F61A0B935AC10

The webapi will serve as a layer on on top of the java based low level library (API) that connects to the database (without exposing any details to the outside). The C++ api (or API in any other language (e.g. python, perl...) for that matter) is then reduced to making a http request and then parsing the response. The response can be formatted as xml or json, and parsed to de-serialize C++ object.

The advantages of the approach are:

• security (no database info is exposed).
• any language that can handle http request can be used to extract data from the repository.
• no duplication of low level libraries
• allows use of connection pools for optimized access to the database

Available Geant 4 hadronic tests

This table was created by the Geant4 hadronic working grouo some time ago and summarizes the status of testing/validation: http://www.geant4.org/geant4/collaboration/working_groups/hadronic/testing/index.shtml

Additional resources are posted here: https://cdcvs.fnal.gov/redmine/projects/g4/wiki/ExpValidationData

Statistical Testing

We plan to study how to use the StatTest application for (semi-)automatic regression testing. This twiki StatTest contains some instructions on how to get and use the code.

Conventions for serialization of objects to FNAL format (histograms)

The data-types are shown here: http://g4devel.fnal.gov:8080/DoSSiER/DisplayDatatypes.xhtml. Histogram are 1 and 2.

As discussed we support multi-dimensional histograms in the database, but data are stored as arrays with dimension=1. In case the original histogram is 2D (or higher dimensionality) we need to serialize its content to 1D array. The problem becomes, given a histogram to serialize its bin values, errors and bin edges in the datamembers of the json object: nbins, val, errStatPlus , errStatMinus , binMin , binMax ((e.g. http://g4devel.fnal.gov:8080/DoSSiER_WS/json/result/232).

Some conventions and rules:

• DoSSier does not store information on underflow or overflow bins. In case this is important for a specific test we can use the parnames, parvalues fields to store this information
• Considering ROOT as the original input format, we do not have separate statistical or systematic errors, we fill the fields errStatPlus and errStatMinus fields with the histogram errors and set to an empty array the systematic errors field: errSysMinus=errSysPlus=[]
• In case errors are symmetric we duplicate the same values, in both fields: errStatPlus=errStatMinus=[ 1, 2, 3 ]
• In DoSSier histograms are considered to have the most general form of non-equally distant bin edges, the case of equidistant bins is a specialization of this case. So binMin and binMax contain always explicitly bin edges. Equidistant bins are defined for the case: equal_all(binMin[]-binMax[] , binMin[0]-binMax[0]). For more than 1 dimension, bin edges are serialized: binMin=[ lowerEdgesFirstDimension, lowerEdgesSecondDimension , .... ] , similarly for binMax.
• Binning information is redundant since no holes are allowed in binning (if there are holes, you use a graph) and thus binMax[i-1]=binMin[i]
• nbins fields is an array containing the number of bins for each dimension, thus nbins=[ numBinsFirstDimension, numBinsSecondDimension, .... ]

An example of serialization of a 2D histogram is shown in the following image:

Pseudo-code to serialize an histogram object:

#Object histograms provide the following methods:
get_nbins(histo: input) -> return tuple(int)
get_bin_mins( histo: input , int : axis_index ) -> return tuple(float)
get_bin_content ( histo : input , tuple(int) : bin_indexes ) -> return float

#Serialize:
dimension=length( get_nbins(histogram) ) 
nbins=get_nbins(histogram)
dimension=length(nbins)
vals=[]
binMin=[]
for axis_index in range(1,dimension):
     binMin.append( get_bin_mins(histogram,axis_index)
for iz in nbins[2]:
     for iy in nbins[1]:
         for ix in nbins[0]:
              vals.append( get_bin_content( histogram, (ix,iy,iz) )

Conventions for serialization of objects to FNAL format (graphs)

The data-types are shown here: http://g4devel.fnal.gov:8080/DoSSiER/DisplayDatatypes.xhtml . Graphs are 1000 and 1001.

A graph is serialized similarly to the histogram, except that: nbins is an empty array: nbins=[] instead npoints filed is a integer containing the number of points.

The vals field is then filled with the list of X and Y values, e.g. npoints=3,vals=[x0,x1,x2,y0,y1,y2] similarly for errors.

json data exchange format

The listing below shows an example of the json exchange format. Note the field "version" gives the version of the json format. The gson library that is used in the Java API allows support of multiple versions and therefore allows to evolve the schema in the future. The database has fields like mod time, db ids, access and score that are not represented in the json file. This values are considered transient and are not necessary to represent the data. The database id's and modtime will be automatically assigned when a record is committed. The access field controls the access to the data (public, internal, temporary, to be deleted....) by default data that's getting uploaded will be declared internal and is not visible to the public until a moderator declares it public and makes it available for general use. The scores link?? In addition to keep the format compact we decided not to expand the database reference entries or particle tables. In both cases these are uniquely identified (reference: inspire record number or url), (particle: pdgid). Also note that the exchange should be useable for describing both simulated data (test or experimental data. In case of simulated data we list the testname here "simplified Calorimeter" in case of experimental data we give the reference to the article the data comes from.

{
 "ResultList": [
{
  "version":1,
  "testname" : "SimplifiedCalo",
  "reference": null, 


or

  "testname" : null",
  "reference": 
{
    "inspireid": 1252221, 
    "linkurl": null
  }, 

  "mcdetail": {
    "model": "FTFP_BERT", 
    "mctool": {
      "mcname": "GEANT4"
    }, 
    "versiontag": "10.2.ref09"
  }, 
  "access": {}, 
  "parnames": [], 
  "reaction": {
   "rname": "particle production"
  }, 
  "beam": {
  "bname": "particle gun",
  "reference": {
  "inspireid": null, 
  "linkurl": null
  },
   "datatableids":[],
    "MeanEnergy": [
      1000, 
      2000, 
      3000, 
      4000, 
      5000, 
      6000, 
      7000, 
      8000, 
      9000, 
      10000, 
      11000, 
      12000, 
      13000, 
      14000, 
      15000, 
      16000, 
      17000, 
      18000, 
      19000, 
      20000, 
      25000, 
      50000, 
      100000, 
      200000, 
      500000
    ], 
    "ParticleIds": [
      -211
    ]
  }, 
  "parvalues": [], 
  "datatable": {
     "datatype": ????????????
    "nbins": [], 
    "val": [
      1, 
      2, 
      3, 
      4, 
      5, 
      6, 
      7, 
      8, 
      9, 
      10, 
      11, 
      12, 
      13, 
      14, 
      15, 
      16, 
      17, 
      18, 
      19, 
      20, 
      25, 
      50, 
      100, 
      200, 
      500, 
      0.33810499999999999, 
      0.37874799999999997, 
      0.423931, 
      0.43946800000000003, 
      0.42226000000000002, 
      0.41208899999999998, 
      0.41946, 
      0.42390800000000001, 
      0.43114000000000002, 
      0.40968700000000002, 
      0.43012800000000001, 
      0.43390200000000001, 
      0.43440899999999999, 
      0.46484199999999998, 
      0.44543300000000002, 
      0.43936599999999998, 
      0.456013, 
      0.46803299999999998, 
      0.45123099999999999, 
      0.45836300000000002, 
      0.48840499999999998, 
      0.54613100000000003, 
      0.60701700000000003, 
      0.72766900000000001, 
      0.919103
    ], 
    "title": "energy response", 
    "binMin": [], 
    "errSysMinus": [
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0
    ], 
    "axisTitle": [
      "E_{kin}^{beam}, GeV", 
      "<Evis>/E_{beam}"
    ], 
    "binMax": [], 
    "npoints": 25, 
    "errStatMinus": [
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0.0071832399999999996, 
      0.0055442199999999999, 
      0.0053159599999999998, 
      0.0047449800000000002, 
      0.00358333, 
      0.0032749699999999999, 
      0.00298388, 
      0.00299366, 
      0.0030828399999999999, 
      0.0026445100000000001, 
      0.0027955699999999998, 
      0.0026091, 
      0.0023751800000000002, 
      0.0025970899999999998, 
      0.0023476600000000001, 
      0.00220141, 
      0.0022037699999999999, 
      0.0022623600000000002, 
      0.0020870799999999998, 
      0.00203338, 
      0.0019717100000000002, 
      0.0015319699999999999, 
      0.0016336300000000001, 
      0.00149018, 
      0.00097508800000000004
    ], 
    "errStatPlus": [
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0.0071832399999999996, 
      0.0055442199999999999, 
      0.0053159599999999998, 
      0.0047449800000000002, 
      0.00358333, 
      0.0032749699999999999, 
      0.00298388, 
      0.00299366, 
      0.0030828399999999999, 
      0.0026445100000000001, 
      0.0027955699999999998, 
      0.0026091, 
      0.0023751800000000002, 
      0.0025970899999999998, 
      0.0023476600000000001, 
      0.00220141, 
      0.0022037699999999999, 
      0.0022623600000000002, 
      0.0020870799999999998, 
      0.00203338, 
      0.0019717100000000002, 
      0.0015319699999999999, 
      0.0016336300000000001, 
      0.00149018, 
      0.00097508800000000004
    ], 
    "errSysPlus": [
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0, 
      0
    ]
  }, 
  "observable": {
    "oname": "normalized visible Energy"
  }, 
  "target": "AtlasECAL"
}
 ]
}

Naming convention for the Geant 4 version tags

The database contains a table mcdetail where the field version tag represents the version of the monte carlo tool (Geant4/Genie). The convention for this versiontags is enforced by the Java API and is described in the following. This regexp has python syntax and matches the cases we have discussed so far:

[0-9]+\.[0-9]+(\.((p[0-9]+)|(beta[0-9]*)|(ref[0-9]+)|(cand[0-9]+))(\.(cand[0-9]*)?(test[0-9]+)?)?)?

Public releases:

• 10.1
• 10.1.p01
• 10.2.beta
• 10.1.beta01

Internal releases:

• 10.1.ref01
• 10.2.cand03

Special name to indicate some special test:

• 10.1.ref01.test1

The table will contain a text field where we can specify a human readable description of what "test1" means (e.g. "Using Bertini Tag X-Y-Z")

Tested with: https://regex101.com/#python

PDG Codes to be added to the DB

B+	521	B-	-521	B0	511	Bc+	541
Bc-	-541	Bs0	531	D+	411	D-	-411
D0	421	Ds+	431	Ds-	-431	GenericIon	0
He3	1000020030	J/psi	443	N(1440)+	12212	N(1440)0	12112
N(1520)+	2124	N(1520)0	1214	N(1535)+	22212	N(1535)0	22112
N(1650)+	32212	N(1650)0	32112	N(1675)+	2216	N(1675)0	2116
N(1680)+	12216	N(1680)0	12116	N(1700)+	22124	N(1700)0	21214
N(1710)+	42212	N(1710)0	42112	N(1720)+	32124	N(1720)0	31214
N(1900)+	42124	N(1900)0	41214	N(1990)+	12218	N(1990)0	12118
N(2090)+	52214	N(2090)0	52114	N(2190)+	2128	N(2190)0	1218
N(2220)+	100002210	N(2220)0	100002110	N(2250)+	100012210	N(2250)0	100012110
Upsilon	553	a0(1450)+	10211	a0(1450)-	-10211	a0(1450)0	10111
a0(980)+	9000211	a0(980)-	-9000211	a0(980)0	9000111	a1(1260)+	20213
a1(1260)-	-20213	a1(1260)0	20113	a2(1320)+	215	a2(1320)-	-215
a2(1320)0	115	alpha	1000020040	anti_B0	-511	anti_Bs0	-531
anti_D0	-421	anti_He3	-1000020030	anti_N(1440)+	-12212	anti_N(1440)0	-12112
anti_N(1520)+	-2124	anti_N(1520)0	-1214	anti_N(1535)+	-22212	anti_N(1535)0	-22112
anti_N(1650)+	-32212	anti_N(1650)0	-32112	anti_N(1675)+	-2216	anti_N(1675)0	-2116
anti_N(1680)+	-12216	anti_N(1680)0	-12116	anti_N(1700)+	-22124	anti_N(1700)0	-21214
anti_N(1710)+	-42212	anti_N(1710)0	-42112	anti_N(1720)+	-32124	anti_N(1720)0	-31214
anti_N(1900)+	-42124	anti_N(1900)0	-41214	anti_N(1990)+	-12218	anti_N(1990)0	-12118
anti_N(2090)+	-52214	anti_N(2090)0	-52114	anti_N(2190)+	-2128	anti_N(2190)0	-1218
anti_N(2220)+	-100002210	anti_N(2220)0	-100002110	anti_N(2250)+	-100012210	anti_N(2250)0	-100012110
anti_alpha	-1000020040	anti_b_quark	-5	anti_c_quark	-4	anti_d_quark	-1
anti_dd1_diquark	-1103	anti_delta(1600)+	-32214	anti_delta(1600)++	-32224	anti_delta(1600)-	-31114
anti_delta(1600)0	-32114	anti_delta(1620)+	-2122	anti_delta(1620)++	-2222	anti_delta(1620)-	-1112
anti_delta(1620)0	-1212	anti_delta(1700)+	-12214	anti_delta(1700)++	-12224	anti_delta(1700)-	-11114
anti_delta(1700)0	-12114	anti_delta(1900)+	-12122	anti_delta(1900)++	-12222	anti_delta(1900)-	-11112
anti_delta(1900)0	-11212	anti_delta(1905)+	-2126	anti_delta(1905)++	-2226	anti_delta(1905)-	-1116
anti_delta(1905)0	-1216	anti_delta(1910)+	-22122	anti_delta(1910)++	-22222	anti_delta(1910)-	-21112
anti_delta(1910)0	-21212	anti_delta(1920)+	-22214	anti_delta(1920)++	-22224	anti_delta(1920)-	-21114
anti_delta(1920)0	-22114	anti_delta(1930)+	-12126	anti_delta(1930)++	-12226	anti_delta(1930)-	-11116
anti_delta(1930)0	-11216	anti_delta(1950)+	-2218	anti_delta(1950)++	-2228	anti_delta(1950)-	-1118
anti_delta(1950)0	-2118	anti_delta+	-2214	anti_delta++	-2224	anti_delta-	-1114
anti_delta0	-2114	anti_deuteron	-1000010020	anti_k(1460)0	-100311	anti_k0_star(1430)0	-10311
anti_k1(1270)0	-10313	anti_k1(1400)0	-20313	anti_k2(1770)0	-10315	anti_k2_star(1430)0	-315
anti_k2_star(1980)0	-100315	anti_k3_star(1780)0	-317	anti_k_star(1410)0	-100313	anti_k_star(1680)0	-30313
anti_k_star0	-313	anti_kaon0	-311	anti_lambda	-3122	anti_lambda(1405)	-13122
anti_lambda(1520)	-3124	anti_lambda(1600)	-23122	anti_lambda(1670)	-33122	anti_lambda(1690)	-13124
anti_lambda(1800)	-43122	anti_lambda(1810)	-53122	anti_lambda(1820)	-3126	anti_lambda(1830)	-13126
anti_lambda(1890)	-23124	anti_lambda(2100)	-3128	anti_lambda(2110)	-23126	anti_lambda_b	-5122
anti_lambda_c+	-4122	anti_neutron	-2112	anti_nu_e	-12	anti_nu_mu	-14
anti_nu_tau	-16	anti_omega-	-3334	anti_omega_b-	-5332	anti_omega_c0	-4332
anti_proton	-2212	anti_s_quark	-3	anti_sd0_diquark	-3101	anti_sd1_diquark	-3103
anti_sigma(1385)+	-3224	anti_sigma(1385)-	-3114	anti_sigma(1385)0	-3214	anti_sigma(1660)+	-13222
anti_sigma(1660)-	-13112	anti_sigma(1660)0	-13212	anti_sigma(1670)+	-13224	anti_sigma(1670)-	-13114
anti_sigma(1670)0	-13214	anti_sigma(1750)+	-23222	anti_sigma(1750)-	-23112	anti_sigma(1750)0	-23212
anti_sigma(1775)+	-3226	anti_sigma(1775)-	-3116	anti_sigma(1775)0	-3216	anti_sigma(1915)+	-13226
anti_sigma(1915)-	-13116	anti_sigma(1915)0	-13216	anti_sigma(1940)+	-23224	anti_sigma(1940)-	-23114
anti_sigma(1940)0	-23214	anti_sigma(2030)+	-3228	anti_sigma(2030)-	-3118	anti_sigma(2030)0	-3218
anti_sigma+	-3222	anti_sigma-	-3112	anti_sigma0	-3212	anti_sigma_b+	-5222
anti_sigma_b-	-5112	anti_sigma_b0	-5212	anti_sigma_c+	-4212	anti_sigma_c++	-4222
anti_sigma_c0	-4112	anti_ss1_diquark	-3303	anti_su0_diquark	-3201	anti_su1_diquark	-3203
anti_t_quark	-6	anti_triton	-1000010030	anti_u_quark	-2	anti_ud0_diquark	-2101
anti_ud1_diquark	-2103	anti_uu1_diquark	-2203	anti_xi(1530)-	-3314	anti_xi(1530)0	-3324
anti_xi(1690)-	-23314	anti_xi(1690)0	-23324	anti_xi(1820)-	-13314	anti_xi(1820)0	-13324
anti_xi(1950)-	-33314	anti_xi(1950)0	-33324	anti_xi(2030)-	-13316	anti_xi(2030)0	-13326
anti_xi-	-3312	anti_xi0	-3322	anti_xi_b-	-5132	anti_xi_b0	-5232
anti_xi_c+	-4232	anti_xi_c0	-4132	b1(1235)+	10213	b1(1235)-	-10213
b1(1235)0	10113	b_quark	5	c_quark	4	chargedgeantino	0
d_quark	1	dd1_diquark	1103	delta(1600)+	32214	delta(1600)++	32224
delta(1600)-	31114	delta(1600)0	32114	delta(1620)+	2122	delta(1620)++	2222
delta(1620)-	1112	delta(1620)0	1212	delta(1700)+	12214	delta(1700)++	12224
delta(1700)-	11114	delta(1700)0	12114	delta(1900)+	12122	delta(1900)++	12222
delta(1900)-	11112	delta(1900)0	11212	delta(1905)+	2126	delta(1905)++	2226
delta(1905)-	1116	delta(1905)0	1216	delta(1910)+	22122	delta(1910)++	22222
delta(1910)-	21112	delta(1910)0	21212	delta(1920)+	22214	delta(1920)++	22224
delta(1920)-	21114	delta(1920)0	22114	delta(1930)+	12126	delta(1930)++	12226
delta(1930)-	11116	delta(1930)0	11216	delta(1950)+	2218	delta(1950)++	2228
delta(1950)-	1118	delta(1950)0	2118	delta+	2214	delta++	2224
delta-	1114	delta0	2114	deuteron	1000010020	e+	-11
e-	11	eta	221	eta(1295)	100221	eta(1405)	9020221
eta(1475)	100331	eta2(1645)	10225	eta2(1870)	10335	eta_prime	331
etac	441	f0(1370)	30221	f0(1500)	9030221	f0(1710)	10331
f0(500)	9000221	f0(980)	9010221	f1(1285)	20223	f1(1420)	20333
f2(1270)	225	f2(1810)	9030225	f2(2010)	9060225	f2_prime(1525)	335
gamma	22	geantino	0	gluon	21	h1(1170)	10223
h1(1380)	10333	k(1460)+	100321	k(1460)-	-100321	k(1460)0	100311
k0_star(1430)+	10321	k0_star(1430)-	-10321	k0_star(1430)0	10311	k1(1270)+	10323
k1(1270)-	-10323	k1(1270)0	10313	k1(1400)+	20323	k1(1400)-	-20323
k1(1400)0	20313	k2(1770)+	10325	k2(1770)-	-10325	k2(1770)0	10315
k2_star(1430)+	325	k2_star(1430)-	-325	k2_star(1430)0	315	k2_star(1980)+	100325
k2_star(1980)-	-100325	k2_star(1980)0	100315	k3_star(1780)+	327	k3_star(1780)-	-327
k3_star(1780)0	317	k_star(1410)+	100323	k_star(1410)-	-100323	k_star(1410)0	100313
k_star(1680)+	30323	k_star(1680)-	-30323	k_star(1680)0	30313	k_star+	323
k_star-	-323	k_star0	313	kaon+	321	kaon-	-321
kaon0	311	kaon0L	130	kaon0S	310	lambda	3122
lambda(1405)	13122	lambda(1520)	3124	lambda(1600)	23122	lambda(1670)	33122
lambda(1690)	13124	lambda(1800)	43122	lambda(1810)	53122	lambda(1820)	3126
lambda(1830)	13126	lambda(1890)	23124	lambda(2100)	3128	lambda(2110)	23126
lambda_b	5122	lambda_c+	4122	mu+	-13	mu-	13
neutron	2112	nu_e	12	nu_mu	14	nu_tau	16
omega	223	omega(1420)	100223	omega(1650)	30223	omega-	3334
omega3(1670)	227	omega_b-	5332	omega_c0	4332	opticalphoton	0
phi	333	phi(1680)	100333	phi3(1850)	337	pi(1300)+	100211
pi(1300)-	-100211	pi(1300)0	100111	pi+	211	pi-	-211
pi0	111	pi2(1670)+	10215	pi2(1670)-	-10215	pi2(1670)0	10115
proton	2212	rho(1450)+	100213	rho(1450)-	-100213	rho(1450)0	100113
rho(1700)+	30213	rho(1700)-	-30213	rho(1700)0	30113	rho+	213
rho-	-213	rho0	113	rho3(1690)+	217	rho3(1690)-	-217
rho3(1690)0	117	s_quark	3	sd0_diquark	3101	sd1_diquark	3103
sigma(1385)+	3224	sigma(1385)-	3114	sigma(1385)0	3214	sigma(1660)+	13222
sigma(1660)-	13112	sigma(1660)0	13212	sigma(1670)+	13224	sigma(1670)-	13114
sigma(1670)0	13214	sigma(1750)+	23222	sigma(1750)-	23112	sigma(1750)0	23212
sigma(1775)+	3226	sigma(1775)-	3116	sigma(1775)0	3216	sigma(1915)+	13226
sigma(1915)-	13116	sigma(1915)0	13216	sigma(1940)+	23224	sigma(1940)-	23114
sigma(1940)0	23214	sigma(2030)+	3228	sigma(2030)-	3118	sigma(2030)0	3218
sigma+	3222	sigma-	3112	sigma0	3212	sigma_b+	5222
sigma_b-	5112	sigma_b0	5212	sigma_c+	4212	sigma_c++	4222
sigma_c0	4112	ss1_diquark	3303	su0_diquark	3201	su1_diquark	3203
t_quark	6	tau+	-15	tau-	15	triton	1000010030
u_quark	2	ud0_diquark	2101	ud1_diquark	2103	uu1_diquark	2203
xi(1530)-	3314	xi(1530)0	3324	xi(1690)-	23314	xi(1690)0	23324
xi(1820)-	13314	xi(1820)0	13324	xi(1950)-	33314	xi(1950)0	33324
xi(2030)-	13316	xi(2030)0	13326	xi-	3312	xi0	3322
xi_b-	5132	xi_b0	5232	xi_c+	4232	xi_c0	4132

Nuclei.txt: List of nuclei created in FTFP_BERT</verbatim>

-- AndreaDotti - 2015-10-28

• allParticles.txt: Source of the tables of particles and nuclei</verbatim>

• schema_latest.pdf: latest database schema</verbatim>