Discussion Group C4: Difference between revisions
From canSAS
No edit summary  | 
				|||
| Line 12: | Line 12: | ||
* The definitions of resolution needs work  | * The definitions of resolution needs work  | ||
** @Q_uncertainty – not good name, needs beefier definition that can include beam profiles and arrays etc.  | |||
* and intensity uncertainties need work!  | * and intensity uncertainties need work!  | ||
** Multiple uncertainties – need definition of terms other than Idev (sigma) e.g. Iscalingerror  | |||
* Lots of good feedback to improve the definition and make it more usable  | * Lots of good feedback to improve the definition and make it more usable  | ||
** This will be taken by the working group and the definition updated  | |||
* General conclusion was that we should work towards having the NXcanSAS definition adopted by NeXus  | * General conclusion was that we should work towards having the NXcanSAS definition adopted by NeXus  | ||
| Line 30: | Line 30: | ||
* Reference/example implementations of readers & writers – DFWG & all (at least those who write software!)  | * Reference/example implementations of readers & writers – DFWG & all (at least those who write software!)  | ||
* Work with NIAC to get NXcanSAS ratified as core application definition in NeXus - DFWG  | * Work with NIAC to get NXcanSAS ratified as core application definition in NeXus - DFWG  | ||
== Presentations ==  | == Presentations ==  | ||
Latest revision as of 08:18, 30 April 2015
Towards a common (multidimensional) data format and implementation
Discussion Leaders
- Andrew Jackson
 
Outcomes
- Discussion of the details of definition and implementation of the canSAS 2012 proposal / NXcanSAS
 
- The definitions of resolution needs work
- @Q_uncertainty – not good name, needs beefier definition that can include beam profiles and arrays etc.
 
 
- and intensity uncertainties need work!
- Multiple uncertainties – need definition of terms other than Idev (sigma) e.g. Iscalingerror
 
 
- Lots of good feedback to improve the definition and make it more usable
- This will be taken by the working group and the definition updated
 
 
- General conclusion was that we should work towards having the NXcanSAS definition adopted by NeXus
 
ACTIONS
- Uncertainty descriptions – Brian Pauw
 - Cross checking of keyword/entry names against NeXus definitions and see where we need extra - DFWG
 - Updates to definition based on feedback - DFWG
 - Update documentation - DFWG
 - Reference datasets - DFWG
 - Reference/example implementations of readers & writers – DFWG & all (at least those who write software!)
 - Work with NIAC to get NXcanSAS ratified as core application definition in NeXus - DFWG