Print

Print
Hi Yuri, 

That's right.  When I say LCIO API I'm referring the the LCIO C++ software libraries. 

--Omar Moreno


On Tue, Apr 2, 2013 at 1:13 PM, Yuri Gershtein <[log in to unmask]> wrote:
Hi Omar,

yes, OK, sorry to be slow.
By API here you really mean the software library?

-y

On Apr 2, 2013, at 3:52 PM, Omar Moreno wrote:

Hello Yuri, 

Sorry for the confusion.  I didn't bring up the actual DSTs, I wrote "DST code" as a way of referring  you to the code found here

https://github.com/omar-moreno/hps_dst/




which also happens to be the code used to generate the DSTs.  When you check out that code (or pull), you will find an examples directory which contains some examples not only showing you how to read the DSTs but also how to read the LCIO files directly using the LCIO API.  Specifically, the example TwoTrackAnalysis_example.cxx reads the LCIO collections directly from the LCIO file and looks at events containing two tracks.  It then creates some simple plots using this information. It in NO WAY makes use of the DST.  Here is a direct link to the example: 

https://github.com/omar-moreno/hps_dst/blob/master/examples/TwoTrackAnalysis_example.cxx

--Omar Moreno



On Tue, Apr 2, 2013 at 12:36 PM, Stepan Stepanyan <[log in to unmask]> wrote:
Omar,

Are you talking about ROOT format DSTs.

Thanks, Stepan


On 4/2/13 3:35 PM, Yuri Gershtein wrote:
Hi Omar,

at a risk of being dense…

Why are you bringing up DST's here?
I keep getting confused with the discussions of the root  vs lcio and DST.
To me, the two issues are clearly separate - DST is just what information is persistent, and
root vs lcio is a software choice.

-y


On Apr 2, 2013, at 3:24 PM, Omar Moreno wrote:

@Jeremy: That's right, my comment above was a little premature.  The current version of the converter only uses the LCIO API so the ROOT dictionaries aren't needed anymore.  There was an old version of the converter that made use of the LCIO ROOT library but I have moved away from that. 

There are a couple of ways to access the LCIO files.  You can either access  the LCIO files directly using only the LCIO API or you can write a ROOT script which loads the LCIO ROOT dictionary.  This in turn allows access to the LCIO file from within ROOT.  I recommend the former because as you have experienced, generating the ROOT dictionaries sometimes causes issues.  If you check out the DST code, you can find an example of how to do this within the examples directory (TwoTrackAnalysis_example.cxx).  

--Omar Moreno


On Tue, Apr 2, 2013 at 11:46 AM, Yuri Gershtein <[log in to unmask]> wrote:

On Apr 2, 2013, at 2:42 PM, Graf, Norman A. wrote:

You only need the lcio root dictionary if you want to access the
lcio files directly from within root.

that's exactly what we want to do...

-y
--------------------------
Prof. Yuri Gershtein
W316 Serin Building
Department of Physics and Astronomy
136 Frelinghuysen Rd
Rutgers University
Piscataway, NJ 08854



--------------------------
Prof. Yuri Gershtein
W316 Serin Building
Department of Physics and Astronomy
136 Frelinghuysen Rd
Rutgers University
Piscataway, NJ 08854


Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1




--------------------------
Prof. Yuri Gershtein
W316 Serin Building
Department of Physics and Astronomy
136 Frelinghuysen Rd
Rutgers University
Piscataway, NJ 08854



Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1