FCCSW external data files - re-organization

[vvolkl]

A quick search of FCCSW configs turns up the following files on eos:

/eos/project/f/fccsw-web/testsamples/FCC_minbias_100TeV.dat
/eos/project/f/fccsw-web/testsamples/testHepMCrandom.dat
/eos/project/f/fccsw-web/testsamples/testHepMCborders.dat
/eos/project/f/fccsw-web/testsamples/tkLayout_example_resolutions.root
/eos/project/f/fccsw-web/testsamples/example_MyPythia.dat
/eos/project/f/fccsw-web/testsamples/pp_h_4l.lhe
/eos/project/f/fccsw-web/testsamples/pp_zgzg_4l.lhe
/eos/project/f/fccsw-web/testsamples/elecNoise_ecalBarrel_50Ohm_traces2_2shieldWidth.root
/eos/project/f/fccsw-web/testsamples/elecNoise_emec_50Ohm_2shieldWidth_6layers.root

All the hepmc files can be easily produced on the fly. In addition, there are the following files not in testsamples on eos, which should be moved there:

/eos/user/n/nali/Hadrons/HadZ.root
/eos/user/n/nali/Hadrons/Analysis_HadZ.root
/eos/user/n/nali/SR/SR.root
/eos/user/n/nali/SR/Analysis_SR.root
/afs/cern.ch/user/a/azaborow/public/FCCSW/elecNoise_ecalBarrel_50Ohm_traces2_2shieldWidth_noise.root
/afs/cern.ch/work/c/cneubuse/public/FCChh/inBfield/noiseBarrel_mu100.root
/afs/cern.ch/user/c/cneubuse/public/FCChh/cellNoise_map_segHcal.root
/afs/cern.ch/work/c/cneubuse/public/FCChh/neighbours_map_segHcal.root
/afs/cern.ch/work/c/cneubuse/public/FCChh/cellNoise_map_segHcal_constNoiseLevel.root
/afs/cern.ch/work/c/cneubuse/public/FCChh/inBfield/noiseBarrel_mu100.root

[JavierCVilla]

Indeed, one of the tests is currently failing (RecCalorimeter.recTopoClustersBarrelCaloSystemElecNoise) since it is trying to access to:

/afs/cern.ch/user/a/azaborow/public/FCCSW/elecNoise_ecalBarrel_50Ohm_traces2_2shieldWidth_noise.root

which may not exist anymore.

[clementhelsens]

we really need to invest some time on some simple condition database as well. Javier do you have some expertise with this? Le 5 mars 2019 à 09:57, Javier Cervantes <notifications@github.com<mailto:notifications@github.com>> a écrit : Indeed, one of the tests is currently failing (RecCalorimeter.recTopoClustersBarrelCaloSystemElecNoise) since it is trying to access to: /afs/cern.ch/user/a/azaborow/public/FCCSW/elecNoise_ecalBarrel_50Ohm_traces2_2shieldWidth_noise.root<http://cern.ch/user/a/azaborow/public/FCCSW/elecNoise_ecalBarrel_50Ohm_traces2_2shieldWidth_noise.root> which may not exist anymore. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#326 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFBjDesN48-92Z4lJMB0tZd_DD5iRNEtks5vTjFngaJpZM4bJSSO>.

[JavierCVilla]

we really need to invest some time on some simple condition database as well.

@clementhelsens what do you mean with simple condition database?

[clementhelsens]

I mean instead of having files stored on afs or cvmfs that can be used for calibrations, or event unit tests, we can have them in a database to keep track Le 5 mars 2019 à 10:01, Javier Cervantes <notifications@github.com<mailto:notifications@github.com>> a écrit : we really need to invest some time on some simple condition database as well. @clementhelsens<https://github.com/clementhelsens> what do you mean with simple condition database? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#326 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFBjDfR3O25tpOoDQGvTDQyGEXo3w8KTks5vTjJlgaJpZM4bJSSO>.

[vvolkl]

Hi Clement, for actual detector conditions such as alignment we should investigate also DD4hep https://github.com/AIDASoft/DD4hep/tree/master/DDCond For now I don't see a problem with keeping a few root files with noise maps etc. on eos, but it's true, at one point a database will be a better solution

[clementhelsens]

Hi Valentin, last time I talked about DDCond with Markus Frank, it was not usable, but maybe things have changed. I don’t like much having too root many files on eos, as it really hard to keep track once people leaves. Clement Le 5 mars 2019 à 11:00, vvolkl <notifications@github.com<mailto:notifications@github.com>> a écrit : Hi Clement, for actual detector conditions such as alignment we should investigate also DD4hep https://github.com/AIDASoft/DD4hep/tree/master/DDCond For now I don't see a problem with keeping a few root files with noise maps etc. on eos, but it's true, at one point a database will be a better solution — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#326 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFBjDUnob6ZLDSktGDtSUEEraEsVihD3ks5vTkBZgaJpZM4bJSSO>.