Import Geant4 0.1.0 source tree
This commit is contained in:
Gabriele Cosmo
@@ -1,4 +1,4 @@
|
||||
$Id: README,v 1.3 1998/11/12 11:15:42 morita Exp $
|
||||
$Id: README,v 1.2 1999/04/29 09:04:55 morita Exp $
|
||||
-------------------------------------------------------------------
|
||||
|
||||
=========================================================
|
||||
@@ -14,57 +14,68 @@ the avaiability of HepODBMS and Objectivity/DB.
|
||||
|
||||
To use HepODBMS and underlying Objectivity/DB package, user needs
|
||||
a deep knowledge of the object database and environmental set
|
||||
procedures, which is lacking in this release. The code is provided
|
||||
here to give just a brief idea of the persistency in using Geant4.
|
||||
procedures. The code is provided here to give just a brief idea
|
||||
of using the persistency in Geant4.
|
||||
|
||||
How to build:
|
||||
|
||||
- Setup:
|
||||
|
||||
In addition to Geant4 standard setup, HepODBMS, Objectivity/DB and
|
||||
federated database variables should be defined.
|
||||
In addition to the standard Geant4 setup, additional setup for
|
||||
HepODBMS, Objectivity/DB and federated database should be defined.
|
||||
|
||||
For CERN AFS users, an example setup script "g4odbms_setup.csh" is
|
||||
provided in this directory. Put a line such as
|
||||
|
||||
source ${G4INSTALL}/tests/exampleE02/g4odbms_setup.csh
|
||||
source ${G4INSTALL}/examples/extended/E02/g4odbms_setup.csh
|
||||
|
||||
in your .cshrc file, where ${G4INSTALL} is the actual location of
|
||||
the Geant4 package.
|
||||
|
||||
- Objectivity/DB boot file and lock server
|
||||
|
||||
Boot file contains a database schema information of some basic
|
||||
Boot file is a set of configuration file and baseline federated database
|
||||
file which contain database schema information of some basic
|
||||
HepODBMS and Objectivity/DB classes. Each time you compile your
|
||||
own persistent-capable class, a schema is compiled into your
|
||||
local copy of boot file. User must compile the Geant4 persistent
|
||||
capable schema into your local copy of the boot file.
|
||||
Default location is $HOME/G4EXAMPLE. If you want to have it
|
||||
to other location, define the following variables in your .cshrc.
|
||||
local copy of federeated database.
|
||||
|
||||
When creating a persistency library of Geant4, Geant4-specific persistent
|
||||
classes will be compiled into your local copy of the boot file.
|
||||
|
||||
Default location of the Geant4 boot file is $HOME/G4EXAMPLE.
|
||||
You may want to change the definition of this temporary boot
|
||||
file in your .cshrc.
|
||||
|
||||
example:
|
||||
setenv G4EXAMPLE_BOOT_DIR ${HOME}/tmp/G4EXAMPLE
|
||||
setenv G4EXAMPLE_BOOT ${G4EXAMPLE_BOOT_DIR}/G4EXAMPLE
|
||||
|
||||
For each boot file, user must have unique federated database ID (FDID).
|
||||
For each boot file, you must have unique federated database ID (FDID).
|
||||
This number can be obtained from your local manager of Objectivity
|
||||
lock server. Define G4EXAMPLE_FDID in your .cshrc.
|
||||
|
||||
example:
|
||||
setenv G4EXAMPLE_FDID 501
|
||||
|
||||
The system also have Objectivity/DB lock server running. For the
|
||||
CERN AFS users, see the notes below, for other systems, contact your
|
||||
local system manager for the lock server configuration.
|
||||
To compile the schema and to build the library, you also need an
|
||||
access to Objectivity/DB lock server. For the CERN AFS users, see
|
||||
the notes below, for other systems, contact your local system manager
|
||||
for the lock server configuration.
|
||||
|
||||
Then type,
|
||||
|
||||
gmake cleandb
|
||||
|
||||
to create your own boot file.
|
||||
to create your local copy of Geant4 boot file.
|
||||
___________________________________________________________________________
|
||||
Note: On CERN AFS, user must run his/her own lock server process
|
||||
due to a technical limitation on AFS and Objectivity.
|
||||
Note: On CERN AFS, contact your group system administrator to obtain access
|
||||
to your group lock server. If you want to run this example on your
|
||||
own, you must run your own lock server process on the same machine as
|
||||
you run the executable program, due to a technical limitation on AFS
|
||||
and Objectivity.
|
||||
|
||||
To start your own lock server process,
|
||||
|
||||
oocheckls -notitle `hostname` || \
|
||||
oolockserver -notitle -noauto `hostname`::${G4EXAMPLE_BOOT}
|
||||
@@ -83,8 +94,12 @@ Note: On CERN AFS, user must run his/her own lock server process
|
||||
or
|
||||
kill -9 <pid_of_ools>
|
||||
|
||||
User must have AFS ACL access enabled to HepODBMS and
|
||||
Objectivity/DB directories.
|
||||
You must have AFS ACL access to HepODBMS and Objectivity/DB
|
||||
directories.
|
||||
|
||||
At CERN, the FDID allocation table is given in this URL:
|
||||
|
||||
http://wwwinfo.cern.ch/asd/rd45/white-papers/9804/FDIDAllocation.html
|
||||
___________________________________________________________________________
|
||||
|
||||
- libG4persistency.a
|
||||
@@ -130,7 +145,7 @@ To browse the contents, use "ootoolmgr".
|
||||
ootoolmgr -notitle G4EXAMPLE &
|
||||
|
||||
Make sure to terminate ootoolmgr when you finish browsing.
|
||||
Otherwise lockserver will remember the browsing as a transaction,
|
||||
and the further updates to the database will be blocked.
|
||||
Otherwise lockserver will remember the browsing by ootoolmgr as
|
||||
a "transaction", and the further updates to the database will be blocked.
|
||||
|
||||
--
|
||||
|
||||
Reference in New Issue
Block a user