ROOT is available on the ROOT Download site.
|g++||required||version 3.2 or later.|
|MySQL||optional||necessary if you use rome together with MySQL database.|
|PostgreSQL||optional||necessary if you use rome together with PostgreSQL database.|
|SQLite||optional||necessary if you use rome together with SQLite database.|
|SQLite3||optional||necessary if you use rome together with SQLite version 3 database.|
|MIDAS||optional||necessary if you use rome online together with midas experiment.|
|graphviz||optional||necessary if you want to make a picture which shows task connections.|
|xz library||optional||necessary if you want to read midas files compressed by xz.|
|bzip2 library||optional||necessary if you want to read midas files compressed by bzip2.|
There are 3 different ways to download ROME
Following release are available :
|Version||link to release notes||Supported ROOT version|
|2.14||(release notes)||v4.02.00 - v5.32.00|
|2.13||(release notes)||v4.02.00 - v5.28.00|
|2.12||(release notes)||v4.02.00 - v5.26.00|
|2.11||(release notes)||v4.02.00 - v5.22.00|
|2.10||(release notes)||v4.02.00 - v5.18.00|
|2.9||(release notes)||v4.02.00 - v5.16.00|
|2.8||(release notes)||v4.00.08 - v5.14.00|
|2.7||(release notes)||v4.00.08 - v5.12.00|
ROME is available at a subversion repository at PSI.
You can check out ROME on 3 different ways :
|> svn co file:///afs/psi.ch/project/meg/svn/rome/trunk/rome rome|
|> svn co svn+ssh://email@example.com/afs/psi.ch/project/meg/svn/rome/trunk/rome rome|
|> svn co svn+ssh://firstname.lastname@example.org/afs/psi.ch/project/meg/svn/rome/trunk/rome rome|
|password is 'svn'|
These commands check out the development version (trunk version) of ROME.
To check out a release version replace
|rome/tags/rome_v?.? (e.g. rome/tags/rome_v2.7)|
It is possible that you are forced to type the password several times!
There's a workaround for this problem.
You can check the development notes under SVN log
Define the environment variable ROMESYS and update the path variable by typing :
|> export ROMESYS=~/ROME||on a linux bourne shell|
|> export PATH=$ROMESYS/bin:$PATH||on a linux bourne shell|
|> setenv ROMESYS ~/ROME||on a linux c-shell|
|> setenv PATH $ROMESYS/bin:$PATH||on a linux c-shell|
|> set ROMESYS=C:/ROME||on windows|
|> set Path=%Path%;%ROMESYS%/bin||on windows|
Go to the rome directory and link the ROMEBuilder by typing :
|> make||on linux|
|> nmake -f Makefile.win||on windows|
For information about writing a xml definition file please read the 'XML Definition File' section of the users guide.
For information about command line parameters for the ROMEBuilder please read the 'Command Line' section of the users guide.
|> romebuilder myExperiment.xml|
The ROMEBuilder has now generated all classes of the framework and has placed them in a also generated directory structure. Now you have to write your user code to the event methods of the task classes. The task classes are located in the directory '/src/tasks/'. For information about writing user code to the event methods please read the 'Access Methods' section of the users guide and see the sample application.
Run the ROMEBuilder again to link the user code into the framework.
You may repeat the steps 4. to 7. until you have reached the final version of your framework.
The name of the executable is [short cut][program name].exe. The short cut and the program name have to be defined in the xml definition file.
For information about command line parameters for the framework please read the 'Command Line' section of the users guide. However, the main steering of the framework is done over the framework configuration file. Please read the 'XML Configuration File' section of the users guide.
|Matthias Schneebeli, Ryu Sawada|