Nexus Support for SESANS (Trac #917)

[rprospero]

Currently, the SESANS data are stored in their own format with its own reader. Storing the SESANS data in a Nexus format would present multiple advantages

• Multiple runs could be combined into the same file. This could allow SANS and SESANS on asample to be stored in a single file. Alternately, position scans or temperature series could be stored within one file.

*: Less Code would be needed. The hope is that the SESANS data will sit as a small addition on top of the current Nexus code, instead of its own 174 line module with separate parsing logic

• The files will have better interoperability with other software. The SESANS data could be loaded into standard nexus readers (e.g. HDFView) without needing any new code. Similarly, other scattering software which currently support nexus files will be more likely to enhance that functionality with support for SESANS files than to add an entirely new file format.

With these advantages come one major disadvantage: The NxCanSAS format, as it stands, is inappropriate for SESANS and there is not currently accepted alternative standard. A new format can be proposed at hte next CanSAS meeting, but proposals always carry more weight when acompanied with a working prototype.

Migrated from http://trac.sasview.org/ticket/917

{
    "status": "new",
    "changetime": "2017-04-04T16:53:39",
    "_ts": "2017-04-04 16:53:39.452669+00:00",
    "description": "Currently, the SESANS data are stored in their own format with its own reader.  Storing the SESANS data in a Nexus format would present multiple advantages\n\n* Multiple runs could be combined into the same file.  This could allow SANS and SESANS on asample to be stored in a single file.  Alternately, position scans or temperature series could be stored within one file.\n\n*: Less Code would be needed. The hope is that the SESANS data will sit as a small addition on top of the current Nexus code, instead of its own 174 line module with separate parsing logic\n\n* The files will have better interoperability with other software.  The SESANS data could be loaded into standard nexus readers (e.g. HDFView) without needing any new code.  Similarly, other scattering software which currently support nexus files will be more likely to enhance that functionality with support for SESANS files than to add an entirely new file format.\n\nWith these advantages come one major disadvantage:  The NxCanSAS format, as it stands, is inappropriate for SESANS and there is not currently accepted alternative standard.  A new format can be proposed at hte next CanSAS meeting, but proposals always carry more weight when acompanied with a working prototype.",
    "reporter": "awashington",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView Bug Fixing",
    "time": "2017-04-04T15:43:16",
    "component": "SasView",
    "summary": "Nexus Support for SESANS",
    "priority": "minor",
    "keywords": "sesans nexus",
    "milestone": "SasView WishList",
    "owner": "awashington",
    "type": "enhancement"
}

[smk78]

Trac update at 2017/04/04 16:53:39: smk78 commented:

Surely there would be more benefit to storing SESANS data in a format where it can be stored alongside (ie, in the same file as) SANS data? In which case, using Nexus, rather than NXcanSAS makes no sense (since no one routinely stores reduced SANS data in Nexus format).

To use NXcanSAS all that is required is a proposal to extend the standard.

A similar extension proposal should also be made in respect of the CanSAS1D format.

I'm happy to help with these proposals!

[smk78]

@wimbouwman comments

For us in Delft this is not important. It might be for ISIS.

[butlerpd]

This should probably be moved to the discussions at this point? Along those lines, there was a discussion at the brief canSAS session about some extensions but all extensions at this point are mostly along the lines of specifying agreed nomenclatures. I would be interested in understanding how the current format is incompatible with SESANS? The format was fairly broadly defined though the sesans data are not in q. Is there anything else?

[butlerpd]

Working on cleanup in preparation for Contributor Camp XII:

@smk78 @rprospero @wimbouwman @krzywon can this now be closed? I think the sesans group have a agreed format now and in fact have recently asked to extend it - though again I think that putting into the nxcansas format and asking for approval of definitions would be the better way. Still that is a different ticket. For now it seems to me that this can just be closed as obsolete?

[wimbouwman]

Hi Paul, I know so little about the Nexus format, that I cannot answer your question. Wim

From: Paul Butler @.> Sent: zondag 26 november 2023 00:29 To: SasView/sasdata @.> Cc: Wim Bouwman @.>; Mention @.> Subject: Re: [SasView/sasdata] Nexus Support for SESANS (Trac #917) (#18)

Working on cleanup in preparation for Contributor Camp XII:

@smk78https://urldefense.com/v3/__https:/github.com/smk78__;!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnFuciCEUA$ @rprosperohttps://urldefense.com/v3/__https:/github.com/rprospero__;!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnGMfGHZOw$ @wimbouwmanhttps://urldefense.com/v3/__https:/github.com/wimbouwman__;!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnGBQc1l7w$ @krzywonhttps://urldefense.com/v3/__https:/github.com/krzywon__;!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnEfA7nm_w$ can this now be closed? I think the sesans group have a agreed format now and in fact have recently asked to extend it - though again I think that putting into the nxcansas format and asking for approval of definitions would be the better way. Still that is a different ticket. For now it seems to me that this can just be closed as obsolete?

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/SasView/sasdata/issues/18*issuecomment-1826442021__;Iw!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnEVrujaAg$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ACUIQEJD3MBYYLH357DDS6DYGJ5NRAVCNFSM6AAAAAAQORLZQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGQ2DEMBSGE__;!!PAKc-5URQlI!4n3-jy3V7OgtOn60qYGdS_B4k9g--SBsIrvwft4Re-AV1DvtKH1evS007iZ425F0zV0vgNBNmGDquG8W9NHihnF3azhDoQ$. You are receiving this because you were mentioned.Message ID: @.**@.>>