I am trying to write a runProducer to feed data into QC. The producer should read a MC generated file and feed the info (MFT digits) into QC for each readout frame (ROF). In the run() function of the producer class I want to exit gracefully once the last ROF in the input file is reached.
What is the correct command and the associated header files?
That is, I need something like
if ( no more ROF) {
close QC nicely
}
the idea is to ‘pipe’ this producer to a qc task that gets each ROF and process it
Dear Guillermo,
It rings a bell. I am pretty sure that there has been a recent development in the DPL related to this. Calling @eulisse and @pkonopka.
Cheers,
Barth
to notify that a source will not produce any more data. Such a message will then percolate automatically and once all the devices reach that state the workflow will quit.
If data goes through Data Sampling, then I am not sure if that will work. What is a condition of propagating EndOfStream further? If all inputs of a DataProcessor receive an EndOfStream?
thanks for your answers.
Giulio: I am not sure if I have a DPL: I have a DataProcesssorSpec where the AlgorithSpec uses adaptFromTask. In the task I have a init() and a run(). I want to use the command there. Is this a DPL?
Another question: in run() I have a ‘ProcessingContext& pc’ as argument. Is this what you mean for the command? that is, do I write: pc.services().get().endOfStream() ?
Piotr: for the first tests I do not plan to use data sampling, but later on one should be able to use it. What command would you suggest in this case to exit when I reach the end of file?
I haven’t tried myself the feature with “EndOfStream”, but it should indeed work, even with Data Sampling (unless it has to handle more than one data source, and at least one doesn’t send “EndOfStream”).
What I have to add is sending MonitorObjects one last time when “EndOfStream” reaches a QC task.
Dear Guillermo,
I gave it a try, don’t expect it to work with EndOfStream. While Data Sampling forwards it just fine, the problem is that QC Tasks have also a fake timer input, which apparently doesn’t work well with the logic of handling EndsOfStream. This will require some more thought and fixes.
With the latest O2/dev and latest QC/master QC Tasks and Checks should correctly react to an EndOfStream signal.
When all of the producers will have sent EndOfStream (usage example here), QC Task will finish its cycle, publishing it MonitorObjects for the last time. Then it will send it to CheckRunner with an EndOfStream, which will perform Checks and store the results for the last time, then quit if all devices in the topology are done.
I have a question to this, just for clarification: If I now run a QC task that gets its input data from another device, then when all data was received the QC task should ultimately quit and the workflow should stop after finishing the last cycle and performing checks one last time, right?
Or do I need to include a quit request in my QC task myself?
The following devices will automatically quit when they will have processed all the data after receiving EndOfStream and propagate it further. You don’t have to request to quit in your QC Task. The framework will invoke TaskInterface::endOfCycle and then TaskInterface::endOfActivity.