MetaData - Put the plugin names into the meta data of the database
Moin moin everybody,
this MR streaamlines the metadata. Instead of writing
P0 <shared lib0>
P1 <shared lib1>
P2 <shared lib2>
as individual columns to the databse, I propose to write
PluginLibs <shared lib0>;<shared lib1>;<shared lib2>
further, I realized that we can exploit the getName() method of the GeoVPlugins themselves to also publish the system names. So I added
BuiltDetectors <detName 0>;<detName 1>;<detName 2>;
The advnatage, we can use this column of the AAAHEADER
table to deduce super easily in athena which subdetectors are in the file nad toggle the Detector flags accordingly. We may need to fiddle the plugin names in GeoModelATLAS
Merge request reports
Activity
Hi Johannes. I think we should keep the plugin libraries as is, because it allows us to resolve the pathname and soname of the file. It could be helpful in trying to figure out details of how the file was created. I am not opposed to adding the plugin names either. If this table is getting overburdened we could add another.
I think we should keep in mind that GeoModel should ideally avoid adding ATLAS-only functionality.
added 1 commit
- 6650f310 - detector -> pluginName && data_ID identifier
The information itself prevails. I'm just slightly reshuffling it and exploiting that each GeoModelPlugin has its own name. Sure we can try to write a new table with the GeoPublishPlugins but then we also need to come up with a complicated to mechanism to collect all plugin names. I think that's the easiest solutions to detect which detectors are inside the geometry
- Resolved by Johannes Junggeburth
Added this to the list of the discussion topics for the weekly meeting
added 7 commits
-
6650f310...3dd09442 - 4 commits from branch
main
- d448c62f - Put the plugin names into the meta data of the database
- 90b33c1c - Skip empty names
- a8720e72 - detector -> pluginName && data_ID identifier
Toggle commit list-
6650f310...3dd09442 - 4 commits from branch