Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demonstrate round trip of DIALS data to Nexus data with no loss of signal #1474

Closed
Anthchirp opened this issue Oct 30, 2020 · 4 comments
Closed
Assignees
Labels
stale issues that have not seen activity for a while

Comments

@Anthchirp
Copy link
Member

(issue carried over from discussion in DIALS core meeting)

Nexus as working format for DIALS?

DIALS has an existing data model (past: pickle, now: msgpack). Internal names in that model correspond to the names used inside DIALS for development, eg. xyzobs.px.value has a clear definition.

  • internal names can be kept using soft/hardlinks

No objections for a dials.export $file.refl format=nexus, but do not use nexus as a format to interchange data within DIALS programs.

Q: What is the underlying benefit of using Nexus?

  • main benefit is putative interoperability

Actions:

ASB to create a transformation tool DIALS → Nexus → DIALS to demonstrate the feasibility of this approach, so that we have a concrete proposal to discuss.

@phyy-nx
Copy link
Member

phyy-nx commented Oct 30, 2020

👍

@stale
Copy link

stale bot commented Apr 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. The label will be removed automatically if any activity occurs. Thank you for your contributions.

@stale stale bot added the stale issues that have not seen activity for a while label Apr 29, 2021
@graeme-winter
Copy link
Contributor

Nice idea, this is never going to happen - we may also redefine NeXus one day anyway

@jbeilstenedmands
Copy link
Contributor

Closing to reduce issue load, please reopen if desired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale issues that have not seen activity for a while
Projects
None yet
Development

No branches or pull requests

4 participants