# Changeset 140 for 1dwg/trunk

Ignore:
Timestamp:
Oct 9, 2009 6:00:42 PM (12 years ago)
Message:

manual is nearly complete for v1.0 release, still a few problems to resolve (table+figure, code examples), refs #19

Location:
1dwg/trunk/doc/src
Files:
22 edited

Unmodified
Removed
• ## 1dwg/trunk/doc/src/cansas1d_binding_Fortran.xml

 r130 The development of the FORTRAN language, binding FORTRAN
• ## 1dwg/trunk/doc/src/cansas1d_binding_IgorPro.xml

 r138 version="5.0" xmlns:xlink="http://www.w3.org/1999/xlink"> IgorPro binding binding IgorPro $Revision$
• ## 1dwg/trunk/doc/src/cansas1d_binding_Java.xml

 r134 Documentation for the JAXB binding binding Java
• ## 1dwg/trunk/doc/src/cansas1d_binding_Python.xml

 r130 Specific support for the cansas1d/1.0 data standard in Python binding Python
• ## 1dwg/trunk/doc/src/cansas1d_casestudy_af1410.xml

 r127 $Revision$ $Date$
case study SANS of AF1410 steel Overview
• ## 1dwg/trunk/doc/src/cansas1d_casestudy_collagen.xml

 r138
Overview case study SAXS of dry chick collagen To demonstrate how to get SAS data into the XML standard format, consider this set of SAXS data collected at the National Synchrotron Light Source, Brookhaven National width="150pt" scalefit="1"/>
The raw data was collected on a linear position-sensitive detector and reduced to The raw data was collected on a linear position-sensitive detector and reduced to columns of Q, I, and Iesd (estimated standard deviation of I). The only metadata available for this data (without resorting to digging through piles of old notebooks) was obtained from two file headers: of old notebooks) was obtained from two file headers: collagen.asc http://svn.smallangles.net/trac/canSAS/browser/1dwg/trunk/examples/collagen/COLLAGEN.ASC and collagen.saxs http://svn.smallangles.net/trac/canSAS/browser/1dwg/trunk/examples/collagen/collagen.saxs as shown. collagen.asc First few lines from file <citetitle>collagen.asc</citetitle> Sep 19 1994     01:41:02 am     Elt: 00090 Seconds ID: No spectrum identifier defined Memory Size: 8192 Chls  Conversion Gain: 1024  Adc Offset: 0000 Chls        collagen.saxs dry chick collagen, d = 673 A Full listing of file <citetitle>collagen.saxs</citetitle> dry chick collagen, d = 673 A 6531 eV, X6B But, the data can fulfill the minimum requirements of the 1D standard file format and also make an excellent example of a minimal canSAS reduced 1-D SAS data file in XML. But, there is enough information to fulfill the minimum requirements of the 1D standard file format and also make an excellent example of a minimal canSAS reduced 1-D SAS data file in XML. make the basic XML file It is easiest to copy a template rather than start from an empty file. Copy the cansas1d.xml file into your working directory and rename it to collagen.xml. cansas1d.xml http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xml file into your working directory and rename it to collagen.xml.
modify collagen.xml It is easier to see the metadata in the XML file before you enter the SAXS data into the file. With the brief metadata available, most lines can be eliminated. This will result in a file that looks like <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="example.xsl" ?> <SASroot version="1.0" xmlns="cansas1d/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="cansas1d/1.0 http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd" > <SASentry> <Title>dry chick collagen, d = 673 A, 6531 eV, X6B</Title> <Run /> <SASdata> <!-- Idata lines will go here --> </SASdata> <SASsample> <ID>dry chick collagen, d = 673 A, 6531 eV, X6B</ID> </SASsample> <SASinstrument> <name>X6B, NSLS, BNL</name> <SASsource> <radiation>X-ray synchrotron</radiation> <wavelength unit="A"> 1.898 <!-- = 12398/6531 --> </wavelength> </SASsource> <SAScollimation /> <SASdetector> <name>X6B PSD</name> </SASdetector> </SASinstrument> <SASnote> Sep 19 1994     01:41:02 am     Elt: 00090 Seconds ID: No spectrum identifier defined Memory Size: 8192 Chls  Conversion Gain: 1024  Adc Offset: 0000 Chls dry chick collagen, d = 673 A 6531 eV, X6B </SASnote> </SASentry> </SASroot> into the file. With the brief metadata available, most of the other lines in cansas1d.xml can be eliminated. This will result in a file that looks like the next example. <literal>collagen.xml</literal> with metadata but before data lines are added.
develop a bit of Excel Macro code to clarify our procedure.
Excel macros used Within Excel, with the SAXS data in columns as shown in the Excel table Using Excel macros to reformat the SAXS data Within Excel, binding Microsoft Excel with the SAXS data in columns as shown in the Excel table above, let's define the macros for our use. In Excel, type <alt><F11> to open the macro editing window. Function XML_tag(tag, attr, content) As String If attr = "" Then XML = "<" & tag & ">" Else XML = "<" & tag & " " & attr & ">" End If XML = XML & content XML = XML & "</" & tag & ">" XML_tag = XML End Function Function SAS_Idata_tag(element, unit, content) As String XML = XML_tag(element, "unit=""" & unit & """", content) SAS_Idata_tag = XML End Function Function Idata_tag(Q, Q_unit, I, I_unit, Idev, Idev_unit) As String XML = SAS_Idata_tag("Q", Q_unit, Q) XML = XML & SAS_Idata_tag("I", I_unit, I) XML = XML & SAS_Idata_tag("Idev", Idev_unit, Idev) Idata_tag = XML_tag("Idata", "", XML) End Function Your window will look similar to this one when you copy/paste the above code: (Yes, my spreadsheet is called MyFirstMacro.xls) Microsoft Excel macro to format the <literal>Idata</literal> lines. Your window will look similar to this one when you copy/paste the above example code: (Yes, my spreadsheet is called MyFirstMacro.xls) construct the Idata lines in XML move to spreadsheet cell E5 and enter this formula =IDATA_tag(A5,$A$4,B5,$B$4,C5,$C$4) formula =IDATA_tag(A5,$A$4,B5,$B$4,C5,$C$4) Copy it down all rows in column E through
width="150pt" scalefit="1"/>
• ## 1dwg/trunk/doc/src/cansas1d_definition_of_terms.xml

 r134 This section provides a glossary glossary defining the details about each specific field (XPath string, XML elements and attributes) in the cansas1d/1.0 standard.cansas1d/1.0 standardSASrootSASrootelementSASroot database. This is similar to the root element of a NeXus file (NXroot). SASentry. SASentryelementSASentry This is similar to NXentry used by NeXus. A SASentry can use an optional name attribute to provide a string for this SASentry.
• ## 1dwg/trunk/doc/src/cansas1d_element_SAScollimation.xml

 r138 SAScollimation element SAScollimation parent: length length element length Amount/length of collimation inserted (on a SANS instrument) unit={unit} unit={unit} aperture element aperture Description of a slit or aperture. name: Optional name attribute for this aperture.  type: Optional text attribute to describe the type aperture (pinhole, 4-blade slit, Soller slit, ...). name={type} name: Optional name attribute for this aperture. type: Optional text attribute to describe the type aperture (pinhole, 4-blade slit, Soller slit, ...). name={type} size element size Opening dimensions of this aperture. name={name} distance name={name} distance element distance floating-point number Distance from this collimation element to the sample. unit={unit} unit={unit} x x element x floating-point number Dimension of the collimation in X. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. unit={unit} y Dimension of the collimation in X. The unit attribute is required. See the section about the rules for acceptable values. unit={unit} y element y floating-point number Dimension of the collimation in Y. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. unit={unit} z Dimension of the collimation in Y. The unit attribute is required. See the section about the rules for acceptable values. unit={unit} z element z floating-point number Dimension of the collimation in Z. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. Note: While Z dimension is allowed by the standard (provided by use of a standard element in the XML Schema), it does not make sense for small-angle scattering. unit={unit} Dimension of the collimation in Z. The unit attribute is required. See the section about the rules for acceptable values. While Z dimension is allowed by the standard (provided by use of a standard element in the XML Schema), it does not make sense for small-angle scattering. unit={unit}
• ## 1dwg/trunk/doc/src/cansas1d_element_SASdata.xml

 r138 $Revision$ $Date$ element SASdata SASdata parent: SASentry Idata Idata Idata element Idata container Q element Q typical. unit={unit} unit={unit} I element I [1..1] Intensity of the detected radiation. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. One possibility Intensity of the detected radiation. The unit attribute is required. See the section about the rules for acceptable values. One possibility might be 1/cm for absolute units when the intensity describes a differential cross-section per unit data processing, especially in the area of units conversion. unit={unit} unit={unit} Idev element Idev The unit attribute is required. See rules for units for acceptable values. One units for acceptable values. One possibility might be 1/cm. unit={unit} unit={unit} Qdev element Qdev (optional: see note below on usage) The unit attribute is required. See rules for units for acceptable values. Either for acceptable values. Either 1/A or 1/nm are typical. unit={unit} unit={unit} dQw element dQw The unit attribute is required. See rules for units for acceptable values. Either units for acceptable values. Either 1/A or 1/nm are typical. unit={unit} unit={unit} dQl element dQl Q resolution perpendicular to the axis of scanning (the low-resolution slit length direction). Useful for defining resolution axis of scanning (the low-resolution slit length direction). Useful for defining resolution data from slit-smearing instruments such as Bonse-Hart geometry. (optional: see note below on usage) The unit attribute is required. See rules for units for acceptable values. Either units for acceptable values. Either 1/A or 1/nm are typical. unit={unit} unit={unit} Qmean element Qmean attribute is required. See rules for units for acceptable values. Either for acceptable values. Either 1/A or 1/nm are typical. unit={unit} unit={unit} Shadowfactor element Shadowfactor Describes the adjustment due to the beam stop penumbra. There is no unit attribute. This definition needs revision. NIST? There is no unit attribute. {any} {any} container Any element(s) not defined in the cansas1d/1.0 standard can be placed at this point. See {any} See {any} for more details. When an optional element (Idev, Qdev, ...) When an optional element (Idev, Qdev, ...) is used, it must be given in every Idata within the enclosing SASdata. every Idata within the enclosing SASdata. (The Shadowfactor attribute definition needs revision. NIST?) The Shadowfactor attribute definition needs revision. NIST?

• ## 1dwg/trunk/doc/src/cansas1d_element_SASentry.xml

 r138 SASentry element SASentry parent: SASroot SASroot Title Title element Title string Title of this SASentry. Title of this SASentry. Run Run element Run string name={short-Run-identifier} {any} name={short-Run-identifier} {any} Any element(s) not defined in the cansas1d/1.0 standard can be placed at this point. See {any} See {any} for more details. xmlns:{foreign-prefix}={foreign-namespace} SASdata xmlns:{foreign-prefix}={foreign-namespace} SASdata element SASdata elements with Run elements. (Give them the same name.) name={short-Run-identifier} name={short-Run-identifier} for more details. xmlns:{foreign-prefix}={foreign-namespace} SASsample xmlns:{foreign-prefix}={foreign-namespace} SASsample element SASsample Description of the sample. name={short-SASsample-identifier} SASinstrument name={short-SASsample-identifier} SASinstrument element SASinstrument SASprocess SASprocess element SASprocess Description of a processing or analysis step. name={short-SASprocess-identifier} SASnote name={short-SASprocess-identifier} SASnote element SASnote Free form description of anything not covered by other elements. name={short-SASnote-identifier} name={short-SASnote-identifier}
• ## 1dwg/trunk/doc/src/cansas1d_element_SASinstrument.xml

 r138 SASinstrument element SASinstrument parent: SASentry SASentry name name string SASsource SASsource SAScollimation SAScollimation SASdetector SASdetector
• ## 1dwg/trunk/doc/src/cansas1d_element_SASnote.xml

 r131 SASnote element SASnote parent: xmlns:{foreign-prefix}={foreign-namespace} xmlns:{foreign-prefix}={foreign-namespace}
• ## 1dwg/trunk/doc/src/cansas1d_element_SASprocess.xml

 r138 SASprocess element SASprocess parent: name name element name string date date element date string description description element description string term term element term string SASprocess step. unit={unit} unit={unit} SASprocessnote element SASprocessnote {any} {any} Any element(s) not defined in the cansas1d/1.0 standard can be placed at this point. See {any} See {any} for more details. xmlns:{foreign-prefix}={foreign-namespace} xmlns:{foreign-prefix}={foreign-namespace} {any} {any} Any element(s) not defined in the cansas1d/1.0 standard can be placed at this point. See {any} for more details. xmlns:{foreign-prefix}={foreign-namespace} See {any} for more details. xmlns:{foreign-prefix}={foreign-namespace}
• ## 1dwg/trunk/doc/src/cansas1d_element_SASroot.xml

 r128 SASroot element SASroot parent: SASentry SASentry container [1..inf] A single SAS scan is reported in a SASentry. Include as many SASentry elements as desired. They may contain related or unrelated data. name is an optional attribute to provide a string for this SASentry. (Use of this string is not defined by this A single SAS scan is reported in a SASentry. Include as many SASentry elements as desired. They may contain related or unrelated data. name is an optional attribute to provide a string for this SASentry. (Use of this string is not defined by this standard.)  name=short-name name=short-name

• ## 1dwg/trunk/doc/src/cansas1d_element_SASsource.xml

 r138 SASsource element SASsource parent: SASinstrument radiation radiation element radiation string [1..1] beam_size beam_size element beam_size container [0..1] beam is round, just use X dimension. Note: While Z dimension is allowed by the standard, it does not make sense for small-angle scattering. name={name} beam_shape name={name} beam_shape element beam_shape string [0..1] wavelength wavelength element wavelength floating-point number [0..1] unit={unit} wavelength_min unit={unit} wavelength_min element wavelength_min floating-point number [0..1] Some facilities specify wavelength using a range. The minimum of such a range is given by wavelength_min. unit={unit} wavelength_max unit={unit} wavelength_max element wavelength_max floating-point number [0..1] Some facilities specify wavelength using a range. The maximum of such a range is given by wavelength_max. unit={unit} wavelength_spread unit={unit} wavelength_spread element wavelength_spread floating-point number [0..1] Some facilities specify the width of the wavelength spectrum. The width of such a range is given by wavelength_spread. unit={unit} unit={unit} x x element x floating-point number [0..1] Dimension of the beam in X. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. unit={unit} y Dimension of the beam in X. The unit attribute is required. See the section about the rules for acceptable values. unit={unit} y element y floating-point number [0..1] Dimension of the beam in Y. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. unit={unit} z Dimension of the beam in Y. The unit attribute is required. See the section about the rules for acceptable values. unit={unit} z element z floating-point number [0..1] Dimension of the beam in Z. The unit attribute is required. See cansas1d_documentation#Rules for acceptable values. Note: While Z dimension is allowed by the standard (provided by use of a standard element in the XML Schema), it does not make sense for small-angle scattering. unit={unit} Dimension of the beam in Z. The unit attribute is required. See the section about the rules for acceptable values. While Z dimension is allowed by the standard (provided by use of a standard element in the XML Schema), it does not make sense for small-angle scattering. unit={unit}

 r132 $Date$ Required header for cansas1d/1.0 XML files XML header <?xml version="1.0"?> <SASroot version="1.0" xmlns="cansas1d/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="cansas1d/1.0 http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd"> local directory. Refer to <link xlink:href="http://www.w3schools.org/xsl">W3 Schools XSLT Help</link> for assistance in constructing XSLT files. </para> Help</link> for assistance in constructing XSLT files.<footnote><para><link xlink:href="http://www.w3schools.org/xsl"><literal >http://www.w3schools.org/xsl</literal></link></para></footnote> </para> <para> XML rules actually allow for multiple stylesheet declarations. Explore this possibility as your own adventure. </para> <row> <entry> <emphasis role="bold"> <link xlink:href="#cansas1d_documentation-element-SASroot">SASroot</link> </emphasis> <link xlink:href="#cansas1d_documentation-element-SASroot" ><literal>SASroot</literal></link> </entry> <entry>container</entry> <entry> <para>The canSAS reduced 1-D SAS data (cansas1d/1.0) will be in the <emphasis role="bold">SASroot</emphasis> database.</para> <literal>SASroot</literal> database.</para> <para> (This is similar to NXroot <link xlink:href="http://www.nexusformat.org/NXroot">NXroot</link> used by NeXus.) xlink:href="http://www.nexusformat.org/NXroot"><literal>NXroot</literal></link> used by NeXus.<footnote><para><link xlink:href="http://www.nexusformat.org/NXroot" ><literal>http://www.nexusformat.org/NXroot</literal></link></para></footnote>) </para> </entry> <entry> <itemizedlist> <listitem> <para> <emphasis role="bold">version="1.0"</emphasis> is required to <literal>version="1.0"</literal> is required to identify the cansas1d/1.0 standard for SAS data.</para> </listitem> <listitem> <para> <emphasis role="bold">xmlns</emphasis> sets the default namespace for all elements (with no prefix) in this file. <literal>xmlns</literal> sets the default namespace URI for all elements (with no prefix) in this file. </para> </listitem> <listitem> <para> <emphasis role="bold">xmlns:xsi</emphasis> sets <emphasis role="bold">xsi</emphasis> as the prefix for any elements from the governing XML Schema.</para> <literal>xmlns:xsi</literal> sets <literal>xsi</literal> as the prefix for any elements from the governing XML Schema and defines the namespace URI to use with the <literal>xsi:</literal> element prefix.</para> </listitem> <listitem> <para> <emphasis role="bold">xsi:schemaLocation</emphasis> associates a <literal>xsi:schemaLocation</literal> associates a suggested URL (where the cansas1d/1.0 XML Schema might be found) with the default namespace string. </para> </listitem> </itemizedlist> <para>See Note 1 below</para> </entry> <entry> <para>See Note 2 below</para> </entry> </row> </tgroup> </table> <glossary> <glosslist> <glossentry> <glossterm>Note 1: Required header for cansas1d/1.0 XML files</glossterm> <glossdef> <programlisting><SASroot version="1.0" xmlns="cansas1d/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="cansas1d/1.0 http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd"></programlisting> </glossdef> </glossentry> <glossentry> <glossterm> Note 2: Description of attributes in required header for cansas1d/1.0 XML files </glossterm> <glossdef><programlisting>version="1.0" xmlns="{this-namespace-URI}" xmlns:xsi="{URL-of-governing-XML-Schema}" xsi:schemaLocation="{this-namespace-URI}  {URL-to-find-XML-Schema}"</programlisting></glossdef> </glossentry> </glosslist> </glossary> </section>
• ## 1dwg/trunk/doc/src/elements.xml

 r138 Each of these is described below. Explain the attribute={text} syntax. Elements of type header describe the required XML header lines.  Use them without question. describe the required XML header lines. Without questions, use the header in the section titled Required XML Header. attributename="value" where either single or double quotes surround the value. All attributes must have a value. All attributes must have a value.  Attributes may be given in any order.
• ## 1dwg/trunk/doc/src/other.xml

 r138 ascii3col.xsl <citetitle>ascii3col.xsl</citetitle>
cansasxml-html.xsl
• ## 1dwg/trunk/doc/src/specification.xml

 r134 are deemed to be valid cansas1d/1.0 data files. More needs to be written here. In this document, curly braces, {}, are used to indicate text that is supplied by the user.  Such as, an attribute may be written name={text} and this means that the user would replace {text} with text that gives, in this example, a name such as final detector. Thus resulting in name="final detector" which is a well-formed XML attribute. Another example is an instance of the {any} element.  Suppose one had analysis data, then {any} would be replaced with analysis and the element might look like this: <analysis> ... analysis content goes here ... </analysis>
• ## 1dwg/trunk/doc/src/wiki.xml

 r136 Version 1.0 was tagged from the subversion repository on 2009-05-12 as no changes were committed since January 2009. Use this command to checkout the tagged release. svn checkout http://svn.smallangles.net/svn/canSAS/1dwg/tags/v1.0 cansas1dwg-1.0 Checkout tagged release from subversion repository. svn checkout http://svn.smallangles.net/svn/canSAS/1dwg/tags/v1.0 cansas1dwg-1.0 After an XML header, the root element of the file is SASrootSASroot >SASrootelementSASroot which contains one or more SASentrySASentry >SASentryelementSASentry elements, each of which describes a single experiment (data set, time-slice, step in a series, new sample,
Basic elements of the cansas1d/1.0 standard Required header for cansas1d/1.0 XML files XML header <?xml version="1.0"?> <SASroot version="1.0" xmlns="cansas1d/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="cansas1d/1.0 http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd"> Basic elements of the canSAS 1-D standard
Element Description XML Header descriptive info required at the start of every XML file SASroot root element of XML file  SASentry data set, time-slice, step in a series, new sample, etc.   Title for this particular SASentry   Run run number or ID number of experiment   {any} any cansas1d/1.0 element can be used at this point   SASdata this is where the reduced 1-D SAS data is stored    Idata a single data point in the dataset   {any} any cansas1d/1.0 element can be used at this point   SASsample description of the sample   SASinstrument description of the instrument    SASsource description of the source    SAScollimation description of the collimation    SASdetector description of the detector   SASprocess for each processing or analysis step   SASnote anything at all
Rules cansas1d/1.0 XML data files will adhere to the standard if they can successfully validate validation against XML Schema against the established XML Schema (canSAS1d.xsd). Basic elements of the canSAS 1-D standard
Element Description XML Header descriptive info required at the start of every XML file SASroot root element of XML file  SASentry data set, time-slice, step in a series, new sample, etc.   Title for this particular SASentry   Run run number or ID number of experiment   {any} any cansas1d/1.0 element can be used at this point   SASdata this is where the reduced 1-D SAS data is stored    Idata a single data point in the dataset   {any} any cansas1d/1.0 element can be used at this point   SASsample description of the sample   SASinstrument description of the instrument    SASsource description of the source    SAScollimation description of the collimation    SASdetector description of the detector   SASprocess for each processing or analysis step   SASnote anything at all Q=(4 \pi / \lambda) \sin(\theta)
Required XML file header <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="cansasxml-html.xsl" ?> <SASroot version="1.0" xmlns="cansas1d/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="cansas1d/1.0 http://svn.smallangles.net/svn/canSAS/1dwg/trunk/cansas1d.xsd">
Rules cansas1d/1.0 XML data files will adhere to the standard if they can successfully validate validation against XML Schema against the established XML Schema (canSAS1d.xsd). Q=(4 \pi / \lambda) \sin(\theta) geometry Q where \lambda is the wavelength of the radiation and 2\theta is the angle through which the detected radiation has been scattered. units to be given in standard SI abbreviations (eg, m, cm, mm, nm, K) with the following exceptions: um=micrometres C=celsius A=Angstroms percent=%. fraction a.u.=arbitrary units none=no units are relevant (such as dimensionless) where reciprocal units need to be quoted the format shall be "1/abbreviation" when raised to a power, use similar to "A^3" or "1/m^4" (and not "A3" or "A**3" or "m-4") axes: geometry translation z is along the flight path (positive value in the direction of the detector) x is orthogonal to z in the horizontal plane (positive values increase to the right when viewed towards the incoming radiation) y is orthogonal to z and x in the vertical plane (positive values increase upwards)
Converting data into the XML format The canSAS/xmlWriter http://www.smallangles.net/canSAS/xmlWriter/ xmlWriter is a WWW form to translate three-column ASCII text data into the cansas1d/1.0 XML format. This form will help you in creating an XML file with all the required elements in the correct places. The form requests the SAS data of Q, I, and Idev (defined elsewhere on this page) and some basic metadata (title, run, sample info, ...). Press the Submit button and you will receive a nicely formatted WWW page with the SAS data. If you then choose "View page source" (from one of your browser menus), you will see the raw XML of the cansas1d/1.0 XML format and you can copy/paste this into an XML file. The SAS data that you paste into the form box is likely to be copied directly from a 3-column ASCII file from a text editor. Line breaks are OK, they will be treated as white-space as will tabs and commas. Do not be concerned that the data looks awful in the form entry box, just check the result to see that it comes out OK.
Converting data into the XML format The canSAS/xmlWriter http://www.smallangles.net/canSAS/xmlWriter/ xmlWriter is a WWW form to translate three-column ASCII text data into the cansas1d/1.0 XML format. This form will help you in creating an XML file with all the required elements in the correct places. The form requests the SAS data of Q, I, and Idev (defined elsewhere on this page) and some basic metadata (title, run, sample info, ...). Press the Submit button and you will receive a nicely formatted WWW page with the SAS data. If you then choose "View page source" (from one of your browser menus), you will see the raw XML of the cansas1d/1.0 XML format and you can copy/paste this into an XML file. The SAS data that you paste into the form box is likely to be copied directly from a 3-column ASCII file from a text editor. Line breaks are OK, they will be treated as white-space as will tabs and commas. Do not be concerned that the data looks awful in the form entry box, just check the result to see that it comes out OK.
Here is a brief sketch of how a file would be arranged with multiple SASentry elements and multiple SASdata elements. Brief sketch of a file with multiple SASentry and SASdata blocks.
Note: See TracChangeset for help on using the changeset viewer.