Dear Farrukh
If you want to control the frequency of update of all tabs, maybe, you could use the same method (namely using 'none' DAQ') for calling event methods of tasks and tabs also for non-event based
application.
You may add a task in which you only call 'sleep' function for controlling the frequency.
For allowing you to use GUI buttons also during the sleep, you need to call the sleep function like following.
ProcessEvents function allows you to use GUI parts also during the sleep.
Int_t sec = GetSP()->GetSleepTime();
if (sec > 0) {
struct timespec req, rem;
req.tv_sec = 0;
req.tv_nsec = 100000000; // sleep time in loop
struct timeval endTime, currentTime;
gettimeofday(¤tTime, 0);
endTime.tv_sec = currentTime.tv_sec + sec;
endTime.tv_usec = currentTime.tv_usec;
int ret;
while(1) {
memset(&rem, 0, sizeof(rem));
ret = nanosleep(&req, &rem);
gettimeofday(¤tTime, 0);
if (currentTime.tv_sec > endTime.tv_sec ||
(currentTime.tv_sec == endTime.tv_sec && currentTime.tv_usec > endTime.tv_usec)) {
break;
}
gSystem->ProcessEvents();
}
}
gettimeofday is defined in sys/time.h header file in UNIX-like OS.
gSystem is in TSystem.h
For controlling the frequency, in this example, I added a new steering parameter for the task, which is defined like,
<Task>
... other definition of tasks ...
<SteeringParameters>
<SteeringParameterField>
<SPFieldName>SleepTime</SPFieldName>
<SPFieldType>Int_t</SPFieldType>
<SPFieldInitialization>10</SPFieldInitialization>
<SPFieldComment>Sleep time in sec</SPFieldComment>
</SteeringParameterField>
</SteeringParameters>
</Task>
Best regards,
Ryu
> Dear Farrukh
>
> The 'histoGUI' example was prepared as an example for displaying histograms.
> And the data are generated randomly in FillHisto task instead of reading from an input file.
> So the example is using 'none' DAQ as written in romeConfig.xml in the example; the DAQ class is
> implemented in include/ROMENoDAQSystem.h, and it actually does nothing.
>
> With 'none' DAQ, the program simply call Event method continuously without any control of the frequency.
>
> When you run the example, the frequency is not so fast because the CPU is used for updating the display.
> If you change <UpdateFrequency>, for example, to 10000, you will find the frequency of events through
> the task is increased because you update the display with a less frequency (thus lower CPU power is
> needed).
>
> If you are going to use ROME for non-event based application, there are two ways to call some functions
> defined in tabs.
> 1) With GUI parts, like buttons, menus, sliders and so on
> 2) With calling a function periodically.
>
> 1) is suitable if you want to actively control the GUI; a user needs to, for example, click a button for
> operate the tab.
>
> 2) is suitable if you want to update the display without any operations.
> You can see examples/argus/timer/ and examples/argus/thread as examples.
>
> Best regards,
>
> Ryu
>
> > Dear Colleagues,
> >
> > I have succesfully written a ROME application for monitoring MIDAS events and
> > understand that the appearance of a new MIDAS event record triggers the calling
> > of the event method in the Fill Histogram task.
> >
> > My two questions are however about the example in $ROMESYS/example/histoGUI -
> >
> > 1) In this example there is no MIDAS event nor event record - what then is
> > triggering the calling of the event method
> >
> > 2) Is it possible to regulate the frequency that the event method is called in
> > this example ?
> >
> > best wishes
> > Farrukh Azfar |