| Re: Proxy dict successfully used for the event loop [message #9686 is a reply to message #9683] |
Thu, 05 November 2009 14:53   |
Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
|
first-grade participant |
From: *gsi.de
|
|
Hi,
fine for me, if it is really needed, and if it can be maintained and developed it is ok.
| Quote: |
BTW: Why do we use Geant3? It is not maintaining anymore. And it is even an external package which we can not easily modify or maintain.
|
Geant3 in cernlib is not maintained any more and what we use it Geant3VMC which is maintained by the ROOT team and ALICE collaboration, we also participate in the development and maintenance so we can easily change things if needed. The fact that it is external tells you that if it comes to a dead end we just remove it without any effect to our software. But here with the Babar stuff it is different, First it is inside our stuff and you want to integrate it everywhere so taken this out or replacing it is not as easy as removing G3.
| Quote: |
The major purpose of the job lifetime proxy dict is to store and get access to condition objects which do not necessarily change from event to event. In principle, this proxy dict should be used as an interface to the conditions database.
|
You said also that this "job lifetime proxy" is not yet implemented, what about the connection to the database? is the plan now to implement (or port?) everything here, including a version management system and so on?
regards
Mohammad
|
|
|
|
GSI Forum
Search
Help
Members
Login
Home
