You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
(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.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?
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.
The text was updated successfully, but these errors were encountered: