RE: Multiple event components

["Doug Olson" <dlolson@lbl.gov>]

Perhaps I am thinking of the wrong part of the schema,
but I was expecting that the ROOT equivalent to the
Objy reference to an event component to be something
like filename and sequence# in file.  The sequence number
corresponding to "event" in the TTRee::GetEvent(int event) method.
I don't see the ROOT event sequence# in your fileComponent;
Perhaps it is encoded in the location string?

Doug

> -----Original Message-----
> From: Torre Wenaus [mailto:wenaus@bnl.gov]
> Sent: Thursday, December 17, 1998 12:28 PM
> To: gcdev@sseos.lbl.gov
> Subject: Multiple event components
>
>
> Sorry I missed the meeting, I did intend to join today but it wasn't
> possible.
>
> Jeff just told me about the multiple event component issue. In
> the DST rerun
> that I am perpetually readying myself for the new schema has provision for
> hanging multiple event components off the event collection level, simply a
> filename and a type flag. In the rerun itself this will be empty,
> but you'll
> be able to generate a federation with this schema and stick on multiple
> components. I put in a type ID number and not a type name string, I don't
> know why, but you can map ID to name.
>
>   // Non objectivity event components referenced by filename
>   struct fileComponent
>   {
>     d_Char location[400];
>     d_Long type;
>   };
>   ooVArray(fileComponent) fileComponents;
>
> I do believe I'm actually close to the rerun, but I've given up
> giving time
> estimates.
>
>   -- torre
>
>
> -- Torre Wenaus, BNL     wenaus@bnl.gov    516-344-4755  Fax
> 516-344-4206 --
> -- STAR Experiment, RHIC@BNL  Computing and software project
> leader       --
> -- B. 510A Room 1-175
> http://www.rhic.bnl.gov/STAR/computing.html --
> --
>            http://www.wenaus.com/torre.html            --
>