Kyle,

Constants in calibration files are referenced by chip serial numbers (called "kpixAsic id") .  Values in data files are referenced by chip indices (called "kpixAsic index"). To map serials to indices, the reader needs to process "configuration records" embedded in data files. To analyze simulated data, you either have to embed an XML configuration record before the first data record, or read a configuration file (use KpixConfig.processConfigFile(...), the file should have the same format as configuration record).

KpixCalibrationSet.getCalibration(...) selects the chip by index (throws KpixCalibrationException if the provided index has not been matched to a serial number based on info in processed configuration records). KpixCalibrationSet.getCalibrationBySerial(...)selects the chip by serial.

Neither calibration files nor data files contain any information on things like layers, so KpixCalibrationSet does not have it either.

- Dmitry.



> -----Original Message-----
> From: Kyle Travis [mailto:[log in to unmask]]
> Sent: Monday, April 28, 2014 1:52 PM
> To: Onoprienko, Dmitry
> Cc: kpix-beamtest-software
> Subject: Re: [KPIX-BEAMTEST-SOFTWARE] Retrieving KpixCalibration
> 
> Okay, I'm now successfully able to retrieve a KpixCalibration using the
> default steering file, which is great. I ran into an issue along the
> way, however, which was specifying the address of the layer in reference
> to the KpixCalibrationSet. I had been using "getCalibration" which has
> kpixAsic as its first argument, and passing the first value in my
> calibration file, which appears as "<kpixAsic id=1015>..." for the first
> layer. Unless I'm mistaken, that number gets treated as the serial by
> KpixCalibrationSet, because I was only able to retrieve a calibration
> with the number 1015 when I passed it as the first argument to
> "getCalibrationBySerial".
> 
> Is this intentional? If so, what is the standard of addressing the
> different layers? Sorry if I missed something obvious here, but I want
> to make sure I can consistently get the right address without ignoring
> certain calibrations.
> 
> Thanks!
> 
> Kyle
> 
> 
> On 2014/04/23 14:32, Dmitry Onoprienko wrote:
> > Hello Kyle,
> >
> > I made constructors for specific record types public.
> >
> > - Dmitry.
> >
> >> -----Original Message-----
> >> From: Kyle Travis [mailto:[log in to unmask]]
> >> Sent: Wednesday, April 23, 2014 1:41 PM
> >> To: Onoprienko, Dmitry
> >> Cc: kpix-beamtest-software
> >> Subject: Re: [KPIX-BEAMTEST-SOFTWARE] Retrieving KpixCalibration
> >>
> >> Hi Dmitry,
> >>
> >> Thanks, that example helps a lot. Unfortunately I'm running into
> >> another
> >> issue, which is that the KpixDataRecord constructor is only accessibly
> >> within the KpixReader package. This makes me wonder, would it be
> >> better
> >> to have the simulation hit -> KpixDataRecord within the KpixReader
> >> package for consistency, or is there another solution for this?
> >>
> >> Thanks again,
> >>
> >> Kyle
> >
> >
> #################################################################
> #######
> > Use REPLY-ALL to reply to list
> >
> > To unsubscribe from the KPIX-BEAMTEST-SOFTWARE list, click the
> > following link:
> > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=KPIX-BEAMTEST-
> SOFTWARE&A=1

########################################################################
Use REPLY-ALL to reply to list

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