You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Hi Everybody,
I want to try to describe the different tasks which are relevant for
the CEL topic, so to better say where I am and where I am going. I
would distinguish those sets of features :
    * The ROOT file format, which we could call the CEL ROOT format.
    * The textual file format, which we could call the CEL TXT format,
      and will prove useful when deeply reusing CompositeEventList
within the skimmer.
    * The set of C++ classes for the representation of CELs in memory
at runtime,
       with CompositeEventList at the top.
    * The C++ glue for the use of CELs as input or output of Gleam jobs
    * The C++/Perl glue for the use of CELs as input or output of the skimmer
    * The set of C++ classes for the description of components meta data
       (we have one in the skimmer today).

What is done ?
    * The ROOT file format should be now ok and rather stable.
    * The C++ class CompositeEventList is quite complete.
    * A Gleam glue is usable, even if it deserves more testing.
Today, one can generate CELs with the official format, and read them
back, provided he is writing the main C++ program which will reuse the
CompositeEventList class. For what concerns something more
"ready-to-use", we have a first Gleam glue prototype, with many
internal improvements which could be implemented, but the skimmer is
not yet instrumented for CELs. That's why, in the short-term, I plan
to test the Gleam glue just a little more, and quickly focus on the
support of basic use-cases, especially the construction of a CEL from
existing data files. The steps during the coming weeks could be :
   1. Consolidate the read of a CEL within a Gleam job
   2. Within the skimmer, add the possibility to construct the CEL for a
       given set of data files.
   3. Consolidate the write of a CEL within a Gleam job
   4. Review the dispatch of tasks between rootUtil and RootIo,
       especially the classes RootInputDesc and RootOutputDesc.
   5. Make the skimmer parameters files and the CELs textual format converge.
   6. Review the dispatch of tasks between the skimmer main class
       and CompositeEventList.
Let me know if I should modify my plans.

  • No labels