Feature #515
Non-legacy files area
0%
Description
At the moment there is a FILES area in legacy that contains old (probably broken) geometries, cabling, calibration information. I think we need somewhere to put non-legacy files. Three uses:
- Place for temporary geometries while we get config db up
- Cache for geometries downloaded from config db
- Storage for test cases
propose adding a Files directory to MAUS_ROOT_DIR. MiceModules then will look in the following directories (in this order):
MAUS_ROOT_DIR/Files
MICEFILES
./
for MiceModules. If it can't find anything, it will attempt to build geometry using just the definitions in the current file.
Sounds reasonable?
Updated by Tunnell, Christopher almost 12 years ago
Can we call it something other than "FILES"? The naming of that entire thing just sucks (I remember being really confused since everything is a file). Just for ideas, I remember hearing this stuff be called "COOL DB" or "RATDB" or "ZEBRA".... so I can't think of a good name for it. I guess everything in FILES should be related to the configuration DB, right? This is essentially a cache for the CDB? Maybe CDB_CACHE?
The use case is probably people edit those files before pushing it into the CDB and download CDB information into this?
I've cleaned up the step geometry area a little bit.
Updated by Rogers, Chris almost 12 years ago
The thing I was looking at - I wanted to make some integration tests with some test geometries (e.g. just a solenoid or whatever). I guess I should use a path like
${MAUS_ROOT_DIR}/tests/integration/simulation/whatever
cdb_cache is okay I guess though lower case to keep it consistent with the other directory names... if there are any temporary or test geometries it's a bit misleading but maybe test geometries go as above and lurk in tests area.
Updated by Tunnell, Christopher almost 12 years ago
hiding test geometries sounds like a good idea. The only geometries people should see are step 1, step 4-6. with substeps.
right/