source:
sasview/src/sas/sasgui/guiframe/media/data_formats_help.rst
@
46f798f
Last change on this file since 46f798f was 48b8f6d, checked in by smk78, 8 years ago | |
---|---|
|
|
File size: 4.5 KB |
Data Formats
SasView reads several different 1D SAS (I(Q) vs Q), 2D SAS(I(Qx,Qy) vs (Qx,Qy)) and 1D SESANS (P(z) vs z) data files. From SasView 4.1 onwards, a :ref:`File_Converter_Tool` allows some legacy formats to be converted into modern formats that SasView will read.
1D SAS Formats
SasView will read ASCII ('text') files with 2 to 4 columns of numbers in the following order:
Q, I(Q), ( dI(Q), dQ(Q) )
where dQ(Q) is the instrumental resolution in Q and assumed to have originated from pinhole geometry.
Numbers can be separated by spaces or commas.
SasView recognises the following file extensions which are not case-sensitive:
- .TXT
- .ASC
- .DAT
- .XML (in canSAS format v1.0 and 1.1)
If using CSV output from, for example, a spreadsheet, ensure that it is not using commas as delimiters for thousands.
The SasView :ref:`File_Converter_Tool` available in SasView 4.1 onwards can be used to convert data sets with separated I(Q) and Q files (for example, BSL/OTOKO, and some output from FIT2D and other SAXS-oriented software) into either the canSAS SASXML (XML) format or the NeXus NXcanSAS (HDF5) format.
For a description of the CanSAS/SASXML format see: http://www.cansas.org/formats/canSAS1d/1.1/doc/
For a description of the ISIS 1D format see: http://www.isis.stfc.ac.uk/instruments/loq/software/colette-ascii-file-format-descriptions9808.pdf
For a description of the NXcanSAS format see: http://cansas-org.github.io/NXcanSAS/classes/contributed_definitions/NXcanSAS.html
All the above formats are written by the Mantid Framework.
For a description of the NIST 1D format see: http://danse.chem.utk.edu/trac/wiki/NCNROutput1D_IQ
For a description of the BSL/OTOKO format see: http://www.diamond.ac.uk/Beamlines/Soft-Condensed-Matter/small-angle/SAXS-Software/CCP13/BSL.html
2D SAS Formats
SasView will read ASCII ('text') files in the NIST 2D format (with the extensions .ASC or .DAT) or files in the NeXus NXcanSAS (HDF5) format (with the extension .H5). File extensions are not case-sensitive. Both of these formats are written by the Mantid Framework.
Most of the header lines in the NIST 2D format can actually be removed except the last line, and only the first three columns (Qx, Qy, and I(Qx,Qy)) are actually required.
The SasView :ref:`File_Converter_Tool` available in SasView 4.1 onwards can be used to convert data sets in the 2D BSL/OTOKO format into the NeXus NXcanSAS (HDF5) format.
For a description of the NIST 2D format see: http://danse.chem.utk.edu/trac/wiki/NCNROutput1D_2DQxQy
For a description of the NXcanSAS format see: http://cansas-org.github.io/NXcanSAS/classes/contributed_definitions/NXcanSAS.html
For a description of the BSL/OTOKO format see: For a description of the BSL/OTOKO format see: http://www.diamond.ac.uk/Beamlines/Soft-Condensed-Matter/small-angle/SAXS-Software/CCP13/BSL.html
1D SESANS Format
SasView version 4.1 onwards will read ASCII ('text') files in a prototype SESANS standard format (with the extensions .SES or .SESANS). The file extensions are not case-sensitive.
The file format has a list of name-value pairs at the top of the file which detail the general experimental parameters necessary for fitting and analyzing data. This list should contain all the information necessary for the file to be 'portable' between users.
Following the header is a 6 column list of instrument experimental variables:
- Spin echo length (z, in Angstroms)
- Spin echo length error (Δ z, in Angstroms) (experimental resolution)
- Neutron wavelength (λ , in Angstroms) (essential for ToF instruments)
- Neutron wavelength error (Δλ , in Angstroms)
- Normalized polarization (P ⁄ P0 , unitless)
- Normalized polarization error (Δ(P ⁄ P0) , unitless) (measurement error)
Note
This help document was last changed by Steve King, 07Oct2016