Hi Ivana, I agree with your comments. It is a pity that we never found the time to separate the T classes from the AliRoot framework. For people not aware of the current discussion, the ALICE AliRoot framework (Simulation part) is based on the idea of a VirtualMonteCarlo. The abstract interface (should be TVirtualMC) was unfortunately made ALICE dependent and called AliMC. The abstract interface has real implementations for Geant3, Geant4 and Fluka. The application calls only the abstract interface that provides the same service for: - the input kinematics - the definition of the detector geometry - the step manager and hits/digits This interface has been extremely successfull within ALICE and has allowed comparisons between Geant3 and Geant4 with the same geometry definition and the same input/output. We are currently working on a geometry modeller much better than the ones in Geant3 or Geant4. We will release more information in due time explaining this new package in a few weeks. Once this package is ready, it is our intention to revesit/improve the idea of the VirtualMonteCarlo. Jacek has started the interesting exercise of extracting the portable part of the VirtualMontecarlo. Future developments should be made in view of the new geometry modeller. Rene Brun Ivana Hrivnacova wrote: > > Hi Jacek, > > I'd like to suggest you first to test > what you propose before offering it to the whole > TUniverse. > > In your RootVirtualMC you missed some > important feature of the whole architecure: > there are parts which are designed independently > on the rest of AliRoot framework and could be extracted > and reused within other framework. > Ideally this would be: > AliMC, TGeant3 package without Ali* classes; TGeant4 > As I already wrote you there are a few more files > from STEER that have be included; > but certainly not AliRun, AliModule etc. > which are the base for the AliRoot framework. > > Then as the example of usage - the application > can be made within the AliRoot framework including > the following packages: > STEER, AliGeant3 (currently Ali* files in TGeant3), AliGeant4 > (BTW you completely ignore AliGeant4 in your > RootVirtualMC which is necessary to run aliroot > with geant4 MC). > > I think, we can better discuss all this first > in a smaller forum (the AliRoot developers) > and when we come to something good, usable and *tested* > we can provide it to others. > > Best regards, > > Ivana > > ============================================================== > e-mail: Ivana.Hrivnacova@cern.ch > address: Institut Physique Nucleaire, 91406 Orsay, France > phone: (33) 01 69 15 65 94 > ============================================================== > > On Tue, 19 Mar 2002, Jacek M. Holeczek wrote: > > > Hi, > > Please find attached a "very, very, very" preliminary package which deals > > with extraction of TGeant3 and TGeant4 from AliSoft. > > See the "make.RootVirtualMC" shell script for explanations on how to get > > all required libraries created. > > Then go to "examples" subdirectory and run the "make.MCRoot" shell script > > in order to get "G3Root.so" and "G4Root.so", which you can load then > > using ".L ./G3Root.so" or ".L G4Root.so" from the ROOT prompt. > > Please note - I did NOT test that this whole suite is usable. For the > > moment I have just made sure that everything that is needed it there, > > compiles, links, and that ROOT can "load" these libraries in an > > interactive session (no special ROOT executable is needed, just the > > standard one as it comes with root binary distribution.) > > Have fun, > > Best regards, > > Jacek. > >
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:46 MET