ID |
Date![up up](up.png) |
Author |
Topic |
Subject |
202
|
15 Apr 2016 |
Ryu Sawada | Info | Error with maximum number of tabs in Argus section | Dear Sudeshna
I commit the change to the 'develop' branch.
Ryu
> I've fixed the problem of not being able to define 18 tabs. I edited
> /argus/include/ArgusHistoDisplay.h file:
> I changed the parameter values to:
>
> class ArgusHistoDisplay : public ArgusTab
> {
> protected:
> enum {
> kMaxNumberOfPads = 360,
> kMaxNumberOfPadsX = 10,
> kMaxNumberOfPadsY = 20,
> kNumberOfDisplayViewSelections0 = 54,
> kNumberOfDisplayViewSelections1 = 10,
> kNumberOfDisplayViewSelections2 = 10,
> kMaxNumberOfLines = 81
> };
>
> Now I can define 18 tabs with 3 pads in each.
>
>
>
>
> > Hi Ryu,
> >
> > I am trying to use <Argus> for tabbing like this:
> > <Argus>
> > <Tab>
> > <TabName>Tab1</TabName>
> > <ObjectArrayIndex>0</ObjectArrayIndex>
> >
> > <Index>0</Index>
> > </Tab>
> > <Tab>
> > <TabName>Tab1</TabName>
> > <ObjectArrayIndex>1</ObjectArrayIndex>
> > <Index>1</Index>
> > </Tab>
> > <Tab>
> > <TabName>Tab1</TabName>
> > <ObjectArrayIndex>2</ObjectArrayIndex>
> >
> > <Index>2</Index>
> > </Tab>
> >
> >
> >
> >
> > And I need to add 18 tabs with each tab having three pads.
> > Now I when ever I cross Tab6 with three pads on it, it gives me this error:
> >
> > [sganguly@g2be1 rometest]$ /home/sganguly/dqm/rome/bin/romebuilder.exe -i
> > midas.xml -midas
> > Maximal number of Tabs in the Argus section of Histogram 'h1_wf' reached : 20 !
> >
> > I have noticed that currently I can define 6 tabs and 5 pads on each tab maximum.
> >
> > Could you please help me with this?
> >
> > Thanks a lot!
> > Sudeshna |
203
|
18 Apr 2016 |
SUDESHNA GANGULY | Info | Clear histogram/group of histograms at the beginning of run in ROME | Hi All,
Is there any way in ROME that I can clear histograms at:
1)Run start.
2) Clear by group (tab) ?
Thanks a lot!
Sudeshna |
204
|
21 Apr 2016 |
Ryu Sawada | Info | Clear histogram/group of histograms at the beginning of run in ROME | Dear Sudeshna,
In ROME, histograms are associated with a task (not with a tab).
Histograms are reset at the beginning of runs when "HistAccumulate" is false.
You can set it in your configuration XML like,
<Histogram>
<HistName>MyHisto</HistName>
<HistAccumulate>false</HistAccumulate>
</Histogram>
If you want to clear by hand, you can use ResetHisto() function of your tasks; the function is automatically implemented by ROMEbuilder.
Ryu
> Hi All,
>
> Is there any way in ROME that I can clear histograms at:
>
> 1)Run start.
> 2) Clear by group (tab) ?
>
>
> Thanks a lot!
> Sudeshna |
206
|
06 May 2016 |
SUDESHNA GANGULY | Info | Can we reset histograms at the middle of a run in ROME? | Hi All,
Suppose I want to pause a run, at the middle, and change some run conditions. So
I want to clear histograms at the middle of a run. Is that possible to do in ROME?
That when I pause the run, I want to clear histograms. So with the new run
conditions, when we resume that run, we will get clear pads and histograms will
be filled in new.
Thanks a lot!
Sudeshna |
207
|
11 May 2016 |
Ryu Sawada | Info | Can we reset histograms at the middle of a run in ROME? | Dear Sudeshna,
I added a new button to clear histograms.
![](207/1?thumb=1)
Please update your ROME and use the 'develop' branch.
Best regards,
Ryu
> Hi All,
>
> Suppose I want to pause a run, at the middle, and change some run conditions. So
> I want to clear histograms at the middle of a run. Is that possible to do in ROME?
>
> That when I pause the run, I want to clear histograms. So with the new run
> conditions, when we resume that run, we will get clear pads and histograms will
> be filled in new.
>
>
> Thanks a lot!
> Sudeshna |
208
|
29 Nov 2017 |
Yusuke Uchiyama | Info | Compiler warning | Dear all,
Under the environment with GCC4.8.5 and ROOT6.08.04,
we get the following warning messages when compiling XXXAnalyzer3, XXXAnalyzer4,
XXXConfig, XXXConfig2,3,4, XXXDBAccess, and XXXConfigToForm.
In file included from /usr/include/stdlib.h:24:0,
from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
gcc485/include/ROMEAnalyzer.h:10,
from include/generated/MEGPrecompile.h:23,
from <command-line>:0:
/usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
with optimization (-O) [-Wcpp]
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
^
[345/369] compiling obj/MEGAnalyzer4.o
In file included from /usr/include/stdlib.h:24:0,
from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
gcc485/include/ROMEAnalyzer.h:10,
from include/generated/MEGPrecompile.h:23,
from <command-line>:0:
/usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
with optimization (-O) [-Wcpp]
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
^
It seems due to 'NOOPT' flag added to those objects in the Makefile.
Is the 'NOOPT' flag necessary? If not, how can we remove it?
Regards,
Yusuke |
209
|
29 Nov 2017 |
Ryu Sawada | Info | Compiler warning | Hi Yusuke
NOOPT is added for potentially large source files to reduce the compile time and memory usage.
I guess -D_FORTIFY_SOURCE option is added in your project Makefile or in your environment variable, instead of by
ROME.
However, we could modify ROME to explicitly disable it by adding -D_FORTIFY_SOURCE=0 to NOOPT.
That can be done by modifying builder/src/ROMEBuildMakeFile.cpp line 1348.
Could you try to do it ?
Ryu
> Dear all,
>
> Under the environment with GCC4.8.5 and ROOT6.08.04,
> we get the following warning messages when compiling XXXAnalyzer3, XXXAnalyzer4,
> XXXConfig, XXXConfig2,3,4, XXXDBAccess, and XXXConfigToForm.
>
>
> In file included from /usr/include/stdlib.h:24:0,
> from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> gcc485/include/ROMEAnalyzer.h:10,
> from include/generated/MEGPrecompile.h:23,
> from <command-line>:0:
> /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> with optimization (-O) [-Wcpp]
> # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> ^
> [345/369] compiling obj/MEGAnalyzer4.o
> In file included from /usr/include/stdlib.h:24:0,
> from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> gcc485/include/ROMEAnalyzer.h:10,
> from include/generated/MEGPrecompile.h:23,
> from <command-line>:0:
> /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> with optimization (-O) [-Wcpp]
> # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> ^
>
> It seems due to 'NOOPT' flag added to those objects in the Makefile.
> Is the 'NOOPT' flag necessary? If not, how can we remove it?
>
> Regards,
> Yusuke |
210
|
29 Nov 2017 |
Yusuke Uchiyama | Info | Compiler warning | Hi Ryu,
Thank you.
You are right. We add -D_FORTIFY_SOURCE=2 in CFLAGS and CXXFLAGS in our project Makefile.
If we remove it, the warnings go away.
I tried your suggestion but I got the following warning:
[346/369] compiling obj/MEGAnalyzer3.o
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default]
<command-line>:0:0: note: this is the location of the previous definition
However, if I add
'-U_FORTIFY_SOURCE' instead the warning above disappears.
Do you think it is OK for all?
Regards,
Yusuke
> Hi Yusuke
>
> NOOPT is added for potentially large source files to reduce the compile time and memory usage.
>
> I guess -D_FORTIFY_SOURCE option is added in your project Makefile or in your environment variable, instead of by
> ROME.
> However, we could modify ROME to explicitly disable it by adding -D_FORTIFY_SOURCE=0 to NOOPT.
> That can be done by modifying builder/src/ROMEBuildMakeFile.cpp line 1348.
>
> Could you try to do it ?
>
> Ryu
>
>
> > Dear all,
> >
> > Under the environment with GCC4.8.5 and ROOT6.08.04,
> > we get the following warning messages when compiling XXXAnalyzer3, XXXAnalyzer4,
> > XXXConfig, XXXConfig2,3,4, XXXDBAccess, and XXXConfigToForm.
> >
> >
> > In file included from /usr/include/stdlib.h:24:0,
> > from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> > gcc485/include/ROMEAnalyzer.h:10,
> > from include/generated/MEGPrecompile.h:23,
> > from <command-line>:0:
> > /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> > with optimization (-O) [-Wcpp]
> > # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> > ^
> > [345/369] compiling obj/MEGAnalyzer4.o
> > In file included from /usr/include/stdlib.h:24:0,
> > from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> > gcc485/include/ROMEAnalyzer.h:10,
> > from include/generated/MEGPrecompile.h:23,
> > from <command-line>:0:
> > /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> > with optimization (-O) [-Wcpp]
> > # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> > ^
> >
> > It seems due to 'NOOPT' flag added to those objects in the Makefile.
> > Is the 'NOOPT' flag necessary? If not, how can we remove it?
> >
> > Regards,
> > Yusuke |
211
|
29 Nov 2017 |
Ryu Sawada | Info | Compiler warning | Hi.
Thank you for testing.
-U_FORTIFY_SOURCE is fine, and can be implemented in ROME.
Ryu
> Hi Ryu,
>
> Thank you.
> You are right. We add -D_FORTIFY_SOURCE=2 in CFLAGS and CXXFLAGS in our project Makefile.
> If we remove it, the warnings go away.
>
> I tried your suggestion but I got the following warning:
>
> [346/369] compiling obj/MEGAnalyzer3.o
> <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default]
> <command-line>:0:0: note: this is the location of the previous definition
>
> However, if I add
> '-U_FORTIFY_SOURCE' instead the warning above disappears.
>
> Do you think it is OK for all?
>
> Regards,
> Yusuke
>
> > Hi Yusuke
> >
> > NOOPT is added for potentially large source files to reduce the compile time and memory usage.
> >
> > I guess -D_FORTIFY_SOURCE option is added in your project Makefile or in your environment variable, instead of by
> > ROME.
> > However, we could modify ROME to explicitly disable it by adding -D_FORTIFY_SOURCE=0 to NOOPT.
> > That can be done by modifying builder/src/ROMEBuildMakeFile.cpp line 1348.
> >
> > Could you try to do it ?
> >
> > Ryu
> >
> >
> > > Dear all,
> > >
> > > Under the environment with GCC4.8.5 and ROOT6.08.04,
> > > we get the following warning messages when compiling XXXAnalyzer3, XXXAnalyzer4,
> > > XXXConfig, XXXConfig2,3,4, XXXDBAccess, and XXXConfigToForm.
> > >
> > >
> > > In file included from /usr/include/stdlib.h:24:0,
> > > from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> > > gcc485/include/ROMEAnalyzer.h:10,
> > > from include/generated/MEGPrecompile.h:23,
> > > from <command-line>:0:
> > > /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> > > with optimization (-O) [-Wcpp]
> > > # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> > > ^
> > > [345/369] compiling obj/MEGAnalyzer4.o
> > > In file included from /usr/include/stdlib.h:24:0,
> > > from /meg/data1/shared/mc/benchmark_test/rome3-root6.08.04-
> > > gcc485/include/ROMEAnalyzer.h:10,
> > > from include/generated/MEGPrecompile.h:23,
> > > from <command-line>:0:
> > > /usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires compiling
> > > with optimization (-O) [-Wcpp]
> > > # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
> > > ^
> > >
> > > It seems due to 'NOOPT' flag added to those objects in the Makefile.
> > > Is the 'NOOPT' flag necessary? If not, how can we remove it?
> > >
> > > Regards,
> > > Yusuke |
Draft
|
28 Feb 2018 |
Francesco Renga | Forum | DB path | Dear all,
I need to perform a DB query in ROME, where I have to select an array of |
213
|
23 Jul 2019 |
Yusuke Uchiyama | Forum | Change of MIDAS library path | Dear all,
From the recent release of MIDAS, "midas-2019-06", the MIDAS library path is changed:
it was $MIDASSYS/linux/lib, but now $MIDASSYS/lib.
See https://midas.triumf.ca/elog/Midas/1564 for the detail.
Due to this change, ROME analyzers cannot be built with -midas option.
The solution seems easy: change the path in
$ROMESYS/buildersrc/ROMEBuilderMakeFile.cpp AddDAQLibraries().
However, directly changing the code will loose backward compatibility.
Do you have any suggestions?
Regards,
Yusuke |
|