Opened 14 years ago

Closed 13 years ago

#6 closed defect (fixed)

change names & order of columns in Idata

Reported by: prjemian Owned by: prjemian
Priority: major Version:
Keywords: Cc:

Description

The present standard for the order of the columns in the SAS out put file disagrees with the order agreed at the meeting. This agreement was on human-readable (not by consensus on this point—there was one dissenter) 2-6 ordered columns (the dissenter wanted the information sequential, but did not dispute order), in the following order Q; I(Q)[; Idev(Q)[; Qdev(Q) [; Qmean(Q); ShadowFactor? (Q)]]]. The order of the columns WAS agreed, and for a reason: It was the one Steve and Ron used for their collaboration, the one IPNS and we use in our text outputs, and the one NIST uses in their text outputs, and the one indicating frequency of use. The history of this standard can be verified by looking at Steve and Ron’s original examples in http://svn.smallangles.net/svn/canSAS/1dwg/trunk/. Ken suggests a return in the standard to this order, with the columns in braces being optional, but the first two of them (Idev(Q) and Qdev in that order) very strongly recommended.

Attachments (1)

[cansas-1dwg] stylesheet revised.eml (1.2 KB) - added by prjemian 14 years ago.
Ken's original email

Download all attachments as: .zip

Change History (5)

Changed 14 years ago by prjemian

Ken's original email

comment:1 Changed 14 years ago by prjemian

  • Status changed from new to assigned

Suggest that the change be implemented as:

Q; I [; Idev] [; Qdev] [; Qmean] [; ShadowFactor?]

Qfwhm will be dropped

comment:2 Changed 14 years ago by prjemian

Andrew Jackson requests:
Can we have dQv and dQh fields to describe slit smeared data?

Add these columns, as well: Qh,Qv,
with the special rule that: Qdev xor (dQv or dQh)
That is, Qdev, dQv, or dQh are optional but Qdev cannot be appear with either of the other two. (That logic should be a bear, er challenge to implement in XML Schema.)

Columns will be:
Q; I [; Idev] [ [; Qdev] | [ [; dQv] [; dQh] ] ] [; Qmean] [; ShadowFactor??]

comment:3 Changed 14 years ago by prjemian

here's how it will be done in the cansas1d.xsd XML schema:
(documentation removed)

<xsd:choice>
	<!-- [ [Qdev] | [[dQv] | [dQh]] ] -->
	<element name="Qdev" minOccurs="0" maxOccurs="1"
		type="tns:floatUnitType" default="0">
	</element>
	<xsd:sequence>
		<element name="dQw" minOccurs="0" maxOccurs="1"
			type="tns:floatUnitType" default="0">
		</element>
		<element name="dQl" minOccurs="0" maxOccurs="1"
			type="tns:floatUnitType" default="0">
		</element>
	</xsd:sequence>
</xsd:choice>

comment:4 Changed 13 years ago by prjemian

  • Resolution set to fixed
  • Status changed from assigned to closed

Slight change of plans after reviewing principles with the persons requesting the change. The desire is to represent the resolution in two dimensions of Bonse-Hart type SAS instrument. The terms dQh and dQv refer to horizontal and vertical components. These terms still remain dependent on the orientation of the SAS instrument. (Most Bonse-Hart instruments scan in the horizontal plane with vertical rotation axis. Synchrotron Bonse-Hart USAXS prefer to scan in the vertical plane with horizontal rotation axis due to favorable polarization term.)

After review, made the change to the more appropriate terms: dQw and dQl

dQw: resolution in the Q-scanning direction

dQl: resolution in the direction transverse to Q scanning

<xsd:choice>
	<!-- [ [Qdev] | [[dQw] | [dQl]] ] -->
	<element name="Qdev" minOccurs="0" maxOccurs="1" 
		type="tns:floatUnitType" default="0" />
	<xsd:sequence>
		<element name="dQw" minOccurs="0" maxOccurs="1" 
			type="tns:floatUnitType" default="0" />
		<element name="dQl" minOccurs="0" maxOccurs="1" 
			type="tns:floatUnitType" default="0" />
	</xsd:sequence>
</xsd:choice>

Note: See TracTickets for help on using tickets.