Bi-weekly meeting
Vidyo
-
- 1
- 2
-
3
AnalysisSpeakers: Mr Emanuele Di Marco (INFN Roma), Igor Abritta Costa (Istituto Nazionale di Fisica Nucleare)
- 4
- 5
-
6
Mechanics and DrawingsSpeakers: Filippo Rosatelli (Istituto Nazionale di Fisica Nucleare), Sandro Tomassini (LNF)
-
7
DAQSpeaker: Andrea Messina (ROMA1)
-
8
SiPM and PMTSpeaker: Francesco Iacoangeli (ROMA1)
-
9
PMT StudiesSpeaker: Davide Piccolo (LNF)
-
10
LIMESpeaker: Francesco Renga (ROMA1)
-
11
Editorial BoardSpeakers: Giovanni Maccarrone (LNF), Stefano Bianco (LNF)
Naming conventions:
Since the DB is filled automatically with a very simple script, a convention for repository and files should be followed
-
the repository name should be called: <detector>-<year>-<number> (e.g. LEMON-20-002, CYGNO-20-001). Ask the PubCom one not used
-
the main tex file must be called <detector>-<year>-<number>.tex
-
the bib file must be called <detector>-<year>-<number>.bib
Then:
-
For overleaf users:
- send a list of github userids that should be added to list with commit rights for a project <detector>-<year>-<number>
-
from the menu => github sharing => link and synch your project with this repository (it will create it), then push changes (the first time and every time you want to sync github, i.e. to make a new version for the DB)
-
For plain git users:
- ask PubCom to create a repository for your paper (same naming convention above)
-
work, commit, and push changes
-
For everyone:
- Repositories are private, since these are for internal revisions, so send a list of github userids that should be added to list with commit rights
When you want to make a new “frozen” version for some reason (e.g. to go to PubCom revision), ask PubCom, and all the fields in the airtable DB will be updated.
Airtable “view”: https://airtable.com/shrzOTHNqWQ6tARSi
For PubCom:
-
to create a new entry, just make a new entry in the Paper ID. This should correspond to the git repository name
-
insert manually also the title (I can make the script to parse the latex file and extract it automatically, but maybe we want it fixed)
-
change the status to the appropriate one
-
run the script (can be found in https://github.com/CYGNO-publications/airtable):
- python push_airtable.py CYGNO-20-001 --make upgit -v V1
-
this will:
- compile the latest version in git
-
change the output PDF name in <detector>-<year>-<number>-<version>.pdf
-
push the PDF in the repo and tag the repository with <version>
-
update automatically the airtable DB with the latest PDF and link to git with the latex code and figures
-