noferini
commented
9 years ago Ciao Luca, in teoria le informazioni temporali ora sono calcolate come nell'analyzer. Se volete provare a guardare intanto a quelle (nella dev). Per ricostruire un evento basta fare un make e poi lanciare l'eseguibile sotto bin eeereco.exe -b path/nomefile.bin L'output è nomefile.root Per ora confronta solo le informazioni temporali. Francesco
Il 20/04/2015 21.22, Luca Baldini ha scritto:
Before the run db came along it made (kind of) sense to offer the possibility to the users to process and merge their own private copies of dst, but now that the run selection is handled via a query at the db there is only one official place where the DST files are stored. One can still create private copies of DST files for testing purposes by setting $E3PIPE_RECON_BASE, but e3merge.py should always point to where the files tracked in the db are.
— Reply to this email directly or view it on GitHub https://github.com/centrofermi/e3pipe/issues/82.
Before the run db came along it made (kind of) sense to offer the possibility to the users to process and merge their own private copies of dst, but now that the run selection is handled via a query at the db there is only one official place where the DST files are stored. One can still create private copies of DST files for testing purposes by setting $E3PIPE_RECON_BASE, but e3merge.py should always point to where the files tracked in the db are.