[NeXus-committee] DECTRIS example summary

"V. Armando Solé" sole at esrf.fr
Mon Jan 14 15:50:43 GMT 2013


On 14/01/2013 16:40, Watts Benjamin wrote:
> I think you're correct Armando, but can the file names be accessed from the inside?

Yes. In fact, when you follow the link, you get the information from the 
target, including parent, file and path in the target file. In fact what 
you loose is the information about in what file and under which path the 
link was present. So, it is the programmer (me in my case) who has to 
keep that information somewhere.

> Both the file names and the "image_nr_low/high" attributes solve the ordering problem, but I don't think they are good methods.
>
And what is good? At the end anything it works is "good".

We'll end up with a reconstruction method for each detector because I do 
not think what DECTRIS will do will be followed by manufacturers of the 
XPAD detector for instance where you find arrangements of detectors with 
different pixel sizes and not in a flat arrangement. Therefore my 
skepticism about previous discussions to display "images" and my push 
towards using the generic solution where given an array of pixels, one 
can get supply an array of positions (x, y and eventually z) and sizes.

Armando



More information about the NeXus-committee mailing list