cansas1d documentation

From canSAS
Revision as of 17:51, 14 March 2008 by Jemian (talk | contribs) (start to reference the subversion/TRAC repositories, added 1st rule that requires the XML Schema)

Disclaimer

This description is meant to inform the community how to layout the information within the XML files. However, should the information in this document and the canSAS 1D SAS XML Schema differ, the XML Schema will be deemed to have the most correct description of the standard.

General Layout of the XML Data

overview

block diagram at SASroot level

After an XML header, the root element of the file is SASroot which contains one or more SASentry elements, each of which describes a single experiment (data set, time-slice, step in a series, new sample, etc.). Details of the SASentry element are also shown in the next figure. Refer to the block diagram at SASroot level for an alternative depiction. See cansas1d.xml for an example XML file. Examples and Case Studies and other background information are available on the canSAS 1D Data Formats Working Group page and its discussion page. Details about each specific field (XPath string, XML elements and attributes) are described on the cansas1d_definition_of_terms page.

block diagrams

There are block diagrams available to describe the standard:

required XML file header

<?xml version="1.0"?>
<SASroot version="1.0"
	xmlns="http://www.smallangles.net/cansas1d"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.smallangles.net/cansas1d/ 
	                    http://www.smallangles.net/cansas1d/1.0/cansas1d.xsd"
	>

alternative XML file header (referencing a stylesheet)

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="example.xsl" ?>
<SASroot version="1.0"
	xmlns="http://www.smallangles.net/cansas1d"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.smallangles.net/cansas1d/ 
	                    http://www.smallangles.net/cansas1d/1.0/cansas1d.xsd"
	>

XML layout for multiple experiments

Each experiment is described with a single SASentry element. The brief example below shows how multiple experiments can be included in a single XML file. (For the sake of brevity, the data for each experiment has been omitted from the example below.)

<?xml version="1.0"?>
<SASroot version="1.0"
	xmlns="http://www.smallangles.net/cansas1d"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.smallangles.net/cansas1d/ 
	                    http://www.smallangles.net/cansas1d/1.0/cansas1d.xsd"
	>
  <SASentry name="071121.dat#S22">
    <!-- contents of the first experiment in the file go here -->
  </SASentry>
  <SASentry name="name attribute is optional">
    <!-- any number of additional experiments can be included, as desired -->
  </SASentry>
</SASroot>

Rules

definition of Q geometry for small-angle scattering
definition of translation and orientation geometry
  1. canSAS1d/1.0 XML data files will adhere to the standard if they can successfully validate against the established XML Schema (http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd)
  2. Q=(4 π / λ) sin(θ)
    where λ is the wavelength of the radiation and 2θ is the angle through which the detected radiation has been scattered.
  3. units to be given in standard SI abbreviations (eg, m, cm, mm, nm, K) with the following exceptions:
    1. um=micrometres
    2. C=celsius
    3. A=Angstroms
    4. percent=%.
    5. fraction
    6. a.u.=arbitrary units
    7. none=no units are relevant (such as dimensionless)
  4. where reciprocal units need to be quoted the format shall be "1/abbreviation"
  5. axes:
    1. z is along the flight path (positive value in the direction of the detector)
    2. x is orthogonal to z in the horizontal plane (positive values increase to the right when viewed towards the incoming radiation)
    3. y is orthogonal to z and x in the vertical plane (positive values increase upwards)
  6. orientation (angles):
    1. roll is about z
    2. pitch is about x
    3. yaw is about y
  7. Unicode characters MUST NOT be used
  8. Binary data is not supported

Note: translation and orientation geometry used by canSAS are consistent with:

  1. http://en.wikipedia.org/wiki/Cartesian_coordinate_system
  2. http://en.wikipedia.org/wiki/Right-hand_rule
  3. http://www.nexusformat.org/Coordinate_Systems
  4. http://mcstas.risoe.dk/documentation/tutorial/node6.html
  5. http://webhost5.nts.jhu.edu/reza/book/kinematics/kinematics.htm

Documentation and Definitions

XML Schema

XML Stylesheets

Stylesheets could be used to strip out the metadata or to convert into another file format. No examples have yet been described here.

Examples and Case Studies

  • basic example: Note that, for clarity, only one row of data is shown. This is probably a very good example to use as a starting point for creating XML files with a text editor.
  • bimodal-test1.xml: Simulated SAS data to test size distribution calculation routines.
  • dry chick collagen: illustrates the minimum information necessary to meet the requirements of the standard format
  • AF1410 steel: SANS study using magnetic contrast variation (with multiple samples and multiple data sets for each sample)
  • cansas1d-template.xml: This is used to test all the rules in the XML Schema. This is probably not a very good example to use as a starting point for creating XML files with a text editor since it tests many of the special-case rules.

Support tools for Visualization & Analysis software

IgorPro

An import/export tool for IgorPro has been created (cansasXML.ipf). You can check out the IgorPro working directory from the SVN server (see below).

As of 2008-03-14,

  • test suite of XML files developed
  • the support can import the XML files into IgorPro
  • Development of a GUI (to support the Irena package) has begun
  • Development to add export capabilities (from IgorPro) back to the cansas1d/1.0 format has begun

Software repositories


Validation of XML against the Schema

  1. open browser to: http://www.xmlvalidation.com/
  2. paste content of candidate XML file (with reference in the header to the XML Schema as shown above) into the form
  3. press <validate>
  4. paste content of cansas1d.xsd XSD file into form and press <continue validation>
  5. check the results