ID |
Date |
Author |
Topic |
Subject |
61
|
23 Mar 2005 |
Matthias Schneebeli | Info | xmlwriter.h |
> I realized that some unix system distribution does not provide xmlwriter.h in standard libxml2-devel
> package.
>
> For instance, scientific linux (also PSI linux) does not.
> I installed it from source.
>
> Macintosh has xmlreader.h by default, and does not xmlwriter.h.
> I installed it by using FINK.
> (FINK is a unix package porter like CYGWIN.)
>
> Someone may ask about it someday.
> A problem is that compiler will find xmlwriter.h even if the system does not have it, because ROME has.
> This may make it hard that users find out the problem.
>
>
> How to install libxml2.
> ---- UNIX OS ----
> In most cases, to use standard way of the system is good. But some system does not provide xmlwriter.h. In this case you may need to
> install it from source.
> 1. download source from <a href="http://xmlsoft.org/">http://xmlsoft.org/</a>.
> 2. decompress it and go to created directory.
> 3. % ./configure [options as you like];
> 4. % make;
> 5. become super user, if you are going to install it in system.
> 6. % make install
>
> ---- MacOSX ----
> By default, Macintosh does not have xmlwriter.h. You can follow the same way as other UNIX OS. And other way is to use FINK. (I hope
> many users already installed it.)
> 1. install FINK (<a href="http://fink.sourceforge.net">http://fink.sourceforge.net</a>)
> 2. become super user.
> 3. apt-get update;
> 4. apt-get install libxml2 libxml2-shlibs libxml2-bin
> If you are goint to use also MySQL.
> 5. apt-get install mysql12-dev mysql12-shlibs
> (* package name can be changed in future, you may find it with "apt-cache search libxml2" or "apt-cache search mysql")
I have replaced libxml with mxml (written by Stefan) which is now included in the rome distribution.
So there's no install problem on linux anymore. |
62
|
23 Mar 2005 |
Matthias Schneebeli | Bug Report | ResetFolders |
> > > In ROMEEventLoop.cpp::ReadEvent
> > > this->ResetFolders is called before fActiveDAQ->ReadEvent, so data in event headers are not updated
> > > properly.
> >
> > done
> I wonder if this is the reason why Jan couldn't read scaler events.
> Event ID was shifted by two events, so when scaler event comes, ROME can always recognize it as trigger events.
No the reason for Jan's problem was that rome never requested scaler events from the frontend. This is fixed now. |
63
|
24 Mar 2005 |
Ryu Sawada | Info | CVS_RSH |
I recommended to my friend trying ROME, but he couldn't download it, because he didn't set CVS_RSH.
There is no instruction for setting CVS_RSH in ROME download page.
You had better to write about it. |
64
|
26 Mar 2005 |
Ryu Sawada | Bug Report | problem after changing xml library |
After changing xml library from libxml2 to mxml, examples (sample and MEG) can not be compiled.
My project does not work too. What is necessary to make it work? |
65
|
29 Mar 2005 |
Ryu Sawada | Info | Histograms |
It does not seem that fHistoNameTitleOverWritten,fHistoNameFolderTitleOverWritten and so on are not
initialized.
I'm afraid it is not safe
,because when ***OverWritten is "true" parameters are not supposed to be initialized.
In my case, framework tries to make a histogram whose number of bins is 1701143923.
This is my definition of the histogram. Do I need to add something?
<Histogram>
<HistName>hXeQsum</HistName>
<HistTitle>Qsum</HistTitle>
<HistFolderName>Xenon</HistFolderName>
<HistFolderTitle>Xenon</HistFolderTitle>
<HistType>TH1F</HistType>
<HistXNbins>4096</HistXNbins>
<HistXmin>0</HistXmin>
<HistXmax>5e5</HistXmax>
</Histogram> |
66
|
29 Mar 2005 |
Ryu Sawada | Suggestion | Input file format |
I am going to make a new ROME project to analyze MC data. Input file will be ROOT which is created by
h2root.
And my friend who is working on dark matter search at Columbia university in NY is going to use
ROME. His file format is special binary format.
If I understand correctly, currently ROME can read midas and ROOT format.
Midas file names are always assumed as "run99999.mid". (99999 is run number)
ROOT files need to have structure defined in definition xml file.
I guess this is not enough to analyze special binary format or ROOT files created by h2root.
What I propose is to allow users to have own daq class. It might be something like
<DAQs>
<DAQ>
<DAQName>daqname</DAQName>
</DAQ>
</DAQs>
Then builder creates [shortcut][daqname].h, [shortcut][daqname].cpp.
[shortcut][daqname] class inherits ROMEDAQSystem class, and users must fill GetTimeStamp(),
Initialize(), Connect(), ReadEvent(int event), Disconnect(), Termination()
When "InputDataFormat" in configuration xml file is "daqname" analyzer uses this class.
|
67
|
30 Mar 2005 |
Matthias Schneebeli | Info | CVS_RSH |
> I recommended to my friend trying ROME, but he couldn't download it, because he didn't set CVS_RSH.
> There is no instruction for setting CVS_RSH in ROME download page.
>
> You had better to write about it.
Yes, thanks |
68
|
01 Apr 2005 |
Matthias Schneebeli | Info | Inportant !!! -> Changes in the user code requiered |
In the current cvs version of ROME several things have changed that require
changes in the user code.
- Most of the histogram parameters have been moved form the definition file to
the configuration file. Please consult the users guide.
- Database paths have also been moved to the configuration file. Furthermore
the format has changed for string replacements. It looks now like this :
<DataBasePath>"/AAA/BBB[0,%s]",/GSP/NumberOfBBB</DataBasePath>
For folders write : '/FolderName/FieldName'.
The format statement must always be %s!
- The tag 'InputDataFormat' has changed to 'DAQSystem' in the configuration
file.
- All bank access methods have to be accessed by gAnalyzer->GetMidas() not only
gAnalyzer.
Matthias |
69
|
03 Apr 2005 |
Ryu Sawada | Suggestion | user defined command line options |
This is not strong request, just a proposal because the same thing can be done by configuration file.
It may be useful if users can have his command line options.
For instance.
<CommandOptions>
<CommandOption>
<OptionFlag>m<OptionFlag>
<OptionName>isMC<OptionName>
<OptionType>Bool_t<OptionType>
<OptionInitialization>false<OptionInitialization>
</CommandOption>
<CommandOption>
<OptionFlag>t<OptionFlag>
<OptionName>TriggerType<OptionName>
<OptionType>Int_t<OptionType>
<OptionInitialization>0<OptionInitialization>
</COmmandOption>
</CommandOptions>
Then user can change the variable with command line option like
./megframework -m -t 2;
Then builder creates new method.
(Bool_t) MEGAnalyzer::GetisMC()
(Int_t) MEGAnalyzer::GetTriggerType() |
70
|
07 Apr 2005 |
Ryu Sawada | Info | Compiler warning |
Followings are warning message from compiler, please check if they are correct.
When I changed line-490 like,
490 while ((obj = iterFolders->Next())) {
warning disappeared.
ROMEAnalyzer.cpp:490: warning: suggest parentheses around assignment used as truth value
//get folder names
485 TObject *obj;
486 TObjArray *names = new TObjArray(100);
487
488 TCollection *folders = folder->GetListOfFolders();
489 TIterator *iterFolders = folders->MakeIterator();
490 while (obj = iterFolders->Next()) {
491 ROMEString str;
492 str.SetFormatted("%s",obj->GetName());
493 names->Add(new TObjString(str.Data()));
494 }
495
ROMEString.cpp:74: warning: `int numberOfDigits' might be used uninitialized in this function
ROMEXMLDataBase.cpp:83: warning: `ROMEXML*xml' might be used uninitialized in this function |
71
|
09 Apr 2005 |
Daniele Barbareschi | Bug Report | Compiling Builder |
I am Daniele Barbareschi, I am a Corrado Gatto's student
I work to interfacing between ALIROOT and MYSQL for CONSTANT CALIBRATION of
subdetector.
There's a bug in compiling...
NAME of file "ROMEXML.h,ROMEXML.cpp" in the ultimate version ROME is lowercase.
The gmake program return error.
Maybe ROMESQL too.
See you those files and similar.
D.B. |
72
|
14 Apr 2005 |
Ryu Sawada | Suggestion | GetDataBase, GetActiveDAQ |
There is no check if the pointer returned by GetDataBase,GetActiveDAQ is valid. This can result
segmentation fault.
For instance, if one specifies DAQ system as "none", or one does not specify DataBaseName, rome
stops without error message.
It is better to modify this behavior.
* One way is to stop application like.
ROMEDAQSystem* GetActiveDAQ() {
if(!fActiveDAQ){
gAnalyzer->Println("some error message");
fApplication->Terminate(1);
}
return fActiveDAQ;
};
*Other way is to use a dummy DAQSystem and DataBase which does nothing when user does not
specify DAQ or DataBase. When dummy is used, warning message must be shown, because it is
dangerous that users do not realize they are using dummy. |
73
|
15 Apr 2005 |
Matthias Schneebeli | Suggestion | GetDataBase, GetActiveDAQ |
> There is no check if the pointer returned by GetDataBase,GetActiveDAQ is valid. This can result
> segmentation fault.
> For instance, if one specifies DAQ system as "none", or one does not specify DataBaseName, rome
> stops without error message.
>
> It is better to modify this behavior.
>
>
> * One way is to stop application like.
> ROMEDAQSystem* GetActiveDAQ() {
> if(!fActiveDAQ){
> gAnalyzer->Println("some error message");
> fApplication->Terminate(1);
> }
> return fActiveDAQ;
> };
>
> *Other way is to use a dummy DAQSystem and DataBase which does nothing when user does not
> specify DAQ or DataBase. When dummy is used, warning message must be shown, because it is
> dangerous that users do not realize they are using dummy.
done |
74
|
15 Apr 2005 |
Ryu Sawada | Suggestion | About parameters in definition and configuration file |
At first there must be several opinions and discussions. Following is just my opinion.
Probably asking opinion some users before changing ROME is better.
There are some properties for histograms and databases.
* database name
* database type and connection
* field database name and path
* histogram properties
I assume that definition file is shared by several persons in experimental group and configuration files
are created for each users at the first execution. If you assume that we should share also configuration
file, story written below is different.
My basic concept is that
*Parameters which is complicated or will be shared among several users should be in definition file.
*Parameters which can be often changed at run time should be in configuration file.
The good point to specify values in definition file is that they are flexible, because we can use
ROMEString::SetFormatted.
It is outstanding point of ROME that we can design framework very flexibly due to builder.
Other point is that parameters in definition file will be written by programer while those in
configuration file can be written by non-experts. It is better that the application can work with few
changes of configuration file as possible. In my feeling, to specify database paths and histogram
parameters in configuration file correctly is too tough for normal users.
In my opinion, they are separated like,
Definition file:
* field database name and path
* histogram properties
Configuration file:
* database type and connection
* (histogram properties)
-- about database path
Normally, users share the same database structure. So I think it should be in definition file. I don't think
paths are changed so often.
-- about database type and connection
At first type and connection can be written in one line like,
xml://directory_of_database/database_name
mysql://[user_name]:[passwd]@[hostname]:[port]/database_name
none://
( odb://[host_name]/[experiment] or odb://experiment@host_name )
(parameters in [] are optional)
These parameters will be changed user by user, because they can have xml files in different place, and
they can use replicated SQL servers.
Password can be written in connection. So it should be in configuration file.
-- about histogram parameters
We can specify them with calculation if they are in definition file. I think it should be in definition file.
And to allow to overwrite in configuration file is also attractive. In my opinion overwriting with normal
type like Float_t,Int_t... is enough.
---------
In result, my opinion is like following.
Database name, database paths and histogram parameters are in definition file.
In default configuration file, config class writes database entries appeared in definition file.
Config class writes histogram parameters entries with empty values if the histogram is <Configurable>.
Only when
some value is written there, analyzer overwrite these parameters.
As I wrote above I think normal number like following are enough as values of histogram parameters in
configuration file.
<HistXmax>1000</HistXmax>
I don't think following is necessary.
</HistXmax>/GSP/parameter</HistXmax>
Definition file
<Folder>
<FolderName>foldername</FolderName>
<DataBaseAccess>true</DataBaseAccess>
<Field>
<FieldName>fieldname</FieldName>
<FieldType>Float_t</FieldType>
<DataBaseName>first_database</DataBaseName>
<DataBasePath>"/Path/to/record"</DataBasePath>
</Field>
<Field>
<FieldName>fieldname2</FieldName>
<FieldType>Float_t</FieldType>
<DataBaseName>second_database</DataBaseName>
<DataBasePath>"/Path/to/record2"</DataBasePath>
</Field>
</Folder>
...
<Histogram>
<HistName>histname</HistName>
<Configurable>true</Configurable>
<HistType>TH1F</HistType>
<HistTitle>ADC0 Bank</HistTitle>
<HistFolderTitle>ADC</HistFolderTitle>
<HistArraySize>gAnalyzer->GetGSP()->GetNumberOfADC()</HistArraySize>
<HistXNbins>4094</HistXNbins>
<HistXmin>1</HistXmin>
<HistXmax>4095</HistXmax>
</Histogram>
Default configuration file
<DataBases>
<DataBase>
<Name>first_database</Name>
<Connection>none://</Connection>
</DataBase>
<DataBase>
<Name>second_database</Name>
<Connection>none://</Connection>
</DataBase>
</DataBases>
...
<Histogram>
<HistName>histname</HistName>
<HistFolderTitle></HistFolderTitle>
<HistArraySize></HistArraySize>
<HistXNbins></HistXNbins>
<HistXmin></HistXmin>
<HistXmax></HistXmax>
</Histogram> |
75
|
15 Apr 2005 |
Ryu Sawada | Suggestion | <Online> in configuration file |
<Online> in configuration file is MIDAS specific thing. Non MIDAS users don't need it.
And it can be used when MIDAS is linked.
So it is better that <Online> appears only when MIDAS is linked. |
76
|
18 Apr 2005 |
Pierre-Andre Amaudruz | Suggestion | ROOTCINT path |
As ROOTSYS is required for the ROME build, I would suggest to
include the code below in the builder for the application Makefile.
This will make Rome less dependent on the ROOT path.
Replace in ROMEBuilder.cpp:
buffer.AppendFormatted("rootcint -f %sDict.cpp -c -p ",shortCut.Data());
by
buffer.AppendFormatted("LD_LIBRARY_PATH=$(ROOTSYS)/lib $(ROOTSYS)/bin/rootcint
-f %sDict.cpp -c -p ",shortCut.Data()); |
77
|
18 Apr 2005 |
Matthias Schneebeli | Suggestion | ROOTCINT path |
> As ROOTSYS is required for the ROME build, I would suggest to
> include the code below in the builder for the application Makefile.
> This will make Rome less dependent on the ROOT path.
>
> Replace in ROMEBuilder.cpp:
>
> buffer.AppendFormatted("rootcint -f %sDict.cpp -c -p ",shortCut.Data());
>
> by
>
> buffer.AppendFormatted("LD_LIBRARY_PATH=$(ROOTSYS)/lib $(ROOTSYS)/bin/rootcint
> -f %sDict.cpp -c -p ",shortCut.Data());
That's in the cvs now, thanks. |
78
|
22 Apr 2005 |
Ryu Sawada | Suggestion | user defined command line options |
> Then user can change the variable with command line option like
> ./megframework -m -t 2;
>
> Then builder creates new method.
> (Bool_t) MEGAnalyzer::GetisMC()
> (Int_t) MEGAnalyzer::GetTriggerType()
I realized better way. In this way users can add or remove command line options without changing their
task files. And it is not necessary to add new object in ROME.
What I propose is to make it in steering parameter. That is <SPCOmmandOption> in steering parameter's
properties.
<SteeringParameterField>
<SPFieldName>isMC</SPFieldName>
<SPFieldType>Bool_t</SPFieldType>
<SPCommandOption>m</SPCommandOption>
</SteeringParameterField>
<SteeringParameterField>
<SPFieldName>TriggerType</SPFieldName>
<SPFieldType>Int_t</SPFieldType>
<SPCommandOption>t</SPCommandOption>
</SteeringParameterField>
Then user can change the variable with command line option like
./megframework -m -t 2;
when -m is typed, isMC becomes true.
Trigger type will be 2.
They can specify the value both with config file and command line option just same as run numbers.
Values in config file will be overwritten by command line option.
|
79
|
22 Apr 2005 |
Ryu Sawada | Suggestion | user defined command line options |
>
> > Then user can change the variable with command line option like
> > ./megframework -m -t 2;
> >
> > Then builder creates new method.
> > (Bool_t) MEGAnalyzer::GetisMC()
> > (Int_t) MEGAnalyzer::GetTriggerType()
>
> I realized better way. In this way users can add or remove command line options without changing their
> task files. And it is not necessary to add new object in ROME.
>
> What I propose is to make it in steering parameter. That is <SPCOmmandOption> in steering parameter's
> properties.
>
> <SteeringParameterField>
> <SPFieldName>isMC</SPFieldName>
> <SPFieldType>Bool_t</SPFieldType>
> <SPCommandOption>m</SPCommandOption>
> </SteeringParameterField>
> <SteeringParameterField>
> <SPFieldName>TriggerType</SPFieldName>
> <SPFieldType>Int_t</SPFieldType>
> <SPCommandOption>t</SPCommandOption>
> </SteeringParameterField>
>
> Then user can change the variable with command line option like
> ./megframework -m -t 2;
> when -m is typed, isMC becomes true.
> Trigger type will be 2.
>
> They can specify the value both with config file and command line option just same as run numbers.
> Values in config file will be overwritten by command line option.
>
>
done. |
80
|
03 May 2005 |
Ryu Sawada | Suggestion | ROOTCINT path |
> > As ROOTSYS is required for the ROME build, I would suggest to
> > include the code below in the builder for the application Makefile.
> > This will make Rome less dependent on the ROOT path.
> >
> > Replace in ROMEBuilder.cpp:
> >
> > buffer.AppendFormatted("rootcint -f %sDict.cpp -c -p ",shortCut.Data());
> >
> > by
> >
> > buffer.AppendFormatted("LD_LIBRARY_PATH=$(ROOTSYS)/lib $(ROOTSYS)/bin/rootcint
> > -f %sDict.cpp -c -p ",shortCut.Data());
>
> That's in the cvs now, thanks.
LD_LIBRARY_PATH is not dedecated for ROOT. One can already have it, and overwriting it may cause error.
For instance, if he installed libstdc++ in non-standard place, he will set LD_LIBRARY_PATH there.
In case of GNU Makefile, we can use "if" statemente like,
ifdef LD_LIBRARY_PATH
LD_LIBRARY_PATH += $(ROOTSYS)/lib
else
LD_LIBRARY_PATH := $(ROOTSYS)/lib
endif |