Trivial PHENIX analysis example

I used a utility which creates you a data file with 100 or so Events. Each event holds exactly (only) one packet with Id 1001.

# include <fileEventiterator.h>

int main(int argc, char *argv[])

{

if (argc < 2)

{

cout << "Usage: " << argv[0] << " filename" << endl;

exit (1);

}

int status;

Eventiterator * it =

new fileEventiterator (argv[1], status);

if (status)

{

cout << "Couldn't open input file " << argv[1] << endl;

delete it;

exit(1);

}

Event *evt;

while ( evt = it->getNextEvent() )

{

evt->identify();

delete evt;

}

delete it;

return 0;

}

And that’s a scan utility which browses through the files and displays the events in there.

The highlighted lines are the essential ones which get you event objects from the file.

You are not exposed to all the mechanics of that process, you just use services provided by objects.

$ ./fileread file.evt | more

-- Event 1 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 2 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 3 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 4 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 5 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 6 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 7 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 8 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 9 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

-- Event 10 Run: 198 length: 222 frames: 1 type: 1 (Data Event)

And that’s the output...