Home » PANDA » PandaRoot » Meetings » PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
| Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO [message #9588 is a reply to message #9587] |
Tue, 20 October 2009 20:44   |
Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
|
first-grade participant |
From: *dip.t-dialin.net
|
|
Hi,
Unfortunately I will not be able to participate in the meeting tomorrow, but any way I have some remarks and questions about the talk above:
- There is no initialization in root macros! You only specify where your parameters should be initialized from, ASCII, ROOT or Oracle.
- Hardcoded parameters is something which the subsystem developers should avoid
- Global initialization task containing the individual subsystem initializations :
- The Runtimedb is such a thing
- Initialization task for the individual subsystems
- In each subsystem there is a parameter container factory that is a sub-class of FairContFact where the parameter containers have to be created for this sub system.
- Each sub-system can implement his parameters as a sub-class of FairParGenericSet, with this the I/O for the parameters is already implemented for ASCII, ROOT and Oracle. Or it can implements directly the FairParSet and deliver themselves the I/O
- The Idea behind Init and Re-Init is to be a defined place to initialize or re-initialize a task, moreover tasks can be added in any order or as subtasks of each other, that is why it is important that each task know how to initialize it self, and all tasks has access to the static runtime data base and with get or find container they can access the containers they need and then the parameter themselves.
Questions:
- What do you mean by dictionary in this context? what does it have more than parameter definitions and values? How different is it from PndEmcDigiPar for example?
- Where do you need to set a branch address? Usually this is hidden from the user? some people hardcore the branch name of the input for there task in the task init, and if the task can only analyze or work with this specific input then it is not that bad! others make the branch name as argument of the task ctor and then they pass it to the GetObject. So is that what you are speaking about here or something else?
- Which data base you are speaking about here?it is not clear for me, if you mean our run time data base and the oracle behind or something else?
- Event time stamp as key to query database! How do you think this should be implemented? And which parameters are changing event by event? Normally some parameters could change within a run and this is usually detected and trigger a re-init of the runtimedb and the reconstruction or analysis tasks.
The most important thing in parameter handling is the version management system, what ever you use for the parameter handling or parameter I/O you need a realistic version management even if you have oracle or MySQL as I/O.
regards
Mohammad
|
|
|
|
 |
|
PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
Re: PandaRoot meeting, Wednesday 21th of October, 10:00, EVO
|
|
|
coordinates....
|
Goto Forum:
Current Time: Thu Apr 18 11:50:10 CEST 2024
Total time taken to generate the page: 0.01083 seconds
|
GSI Forum
Search
Help
Members
Login
Home
