|
1 | 1 | --- |
2 | 2 | layout: page |
3 | 3 | title: SBND Calibration Database |
4 | | -description: SBND Calibration Database Instruction |
| 4 | +description: SBND Calibration Database Instructions |
5 | 5 | toc: true |
6 | 6 | --- |
7 | 7 |
|
8 | 8 | # SBND Calibration Database |
9 | 9 |
|
10 | 10 | Author: Marina Reggiani-Guzzo, PDRA at University of Edinburgh, mguzzo@ed.ac.uk |
| 11 | +Current Database manager: Lucy Kotsiopoulou, PhD student at University of Edinburgh, l.kotsiopoulou@sms.ed.ac.uk |
11 | 12 |
|
12 | | -Last update: 23 May 2024 |
| 13 | +Last update: 20th February 2024 |
13 | 14 |
|
14 | 15 | Hi there, this document contains all the information you need to know about the SBND calibration database. Please contact the author if you find any wrong/outdated information on this page. |
15 | 16 |
|
16 | 17 | **General comments** |
17 | 18 | - This page is under construction, this message will be removed when the displayed information is definite! |
18 | 19 | - If you are working on the SBND calibration, please check if the information for your calibration is listed below, otherwise please update [SBND Calibration Database Spreadsheet](https://docs.google.com/spreadsheets/d/1xbAhb6WnmxbwKxFc-4nnInjHdH8A50S6Zgh0mfZrSF4/edit#gid=217643219) |
19 | 20 |
|
| 21 | +**Further information about the database can be found in these presentations on the SBND docdb:** |
| 22 | +- Calibration update: status and quick guidelines, Lucy Kotsiopoulou, 7.8.2025 (SBN-doc-42768) |
| 23 | +- SBND Calibration Database (update), Alejandro Sánchez Castillo & Marina Reggiani-Guzzo & Moon Jung, 6.3.2025 (SBN-doc-40231) |
| 24 | +- Creating and populating a database, Marina Reggiani-Guzzo, 19.8.2024 (SBN-doc-37559) |
| 25 | +- SBND Calibration Database, Marina Reggiani-Guzzo, 2.2.2024 (SBN-doc-34811) |
| 26 | + |
| 27 | + |
| 28 | + |
20 | 29 | # Databases |
21 | 30 |
|
22 | 31 | There are two databases for SBND: **development database** and **production database**. The "development database" is an intermediate stage used to validate the values that will later on be uploaded to the "production database", which is the one accessed by analyser modules and simulations. That means that, every time the database needs to be updated (whether it is a value changing, or including/removing variables) it will be implemented in the "development database" first. The change should be validated by the person requesting the change, and once confirmed that everything looks ok, the changes will be pushed to the "production database". |
|
0 commit comments