1 / 5

SAXS data format and data handling needs at Soleil Javier Pérez SWING Beamline Synchrotron SOLEIL

SAXS - WAXS - GISAXS. SWING. SAXS data format and data handling needs at Soleil Javier Pérez SWING Beamline Synchrotron SOLEIL Saint-Aubin, France. NeXus : data storage format for images, intensities and contextual data. Detected : I(Q). I i , l. I T. Incoming intensity.

jalena
Download Presentation

SAXS data format and data handling needs at Soleil Javier Pérez SWING Beamline Synchrotron SOLEIL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SAXS - WAXS - GISAXS SWING SAXS data format and data handling needs at Soleil Javier Pérez SWING Beamline Synchrotron SOLEIL Saint-Aubin, France

  2. NeXus : data storage format for images, intensities and contextual data Detected : I(Q) Ii, l IT Incoming intensity Transmitted intensity • Several images are collected for each given sample • Monitoring intensities are also collected for each image • A single NeXus file is generated for the whole sequence

  3. Foxtrot : Graphical Application (Java) for Data reduction and first analysis • Mask, 2D  1D Radial averaging, Frame averaging, Frame subtraction • Determination of Guinier parameters (I0, Rg) • Macro language

  4. Output from Foxtrot : NeXus file + ASCII files to comply with users needs

  5. Am I happy ? Not completely • I also want to use Foxtrot with data coming from other facilities • But : I don’t want to change Foxtrot code for each new different format • I also want to use other applications (e.g. fit2D) on my own data • But : I don’t want to change my data format for each new interesting application • A possible solution : Common data format • Long process : Convince each facility to change its own data format ! • Limited to future : You cannot access old data which don’t have the common format Light and progressive solution • Meanwhile, alternative solution : Explain your own present data format • Each facility should provide a plug-in that describes its own data format • Each plug-in would define common simple functions (e.g.  Getdata(« typeOfData »)) • Each application would have to implement these simple functions  ONLY ONCE

More Related