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

where should functions that save XPCS / speckle results go? #57

Open
ambarb opened this issue Feb 8, 2021 · 1 comment
Open

where should functions that save XPCS / speckle results go? #57

ambarb opened this issue Feb 8, 2021 · 1 comment
Labels
_commonspeckle part of V2, but strictly related to a common repo (speckle + maybe scattering) discussion _futurepyCHX part of V2, future pyCHX once XPCS/speckle analysis is fully separated

Comments

@ambarb
Copy link
Collaborator

ambarb commented Feb 8, 2021

If in _common/speckle, then we would have pressure/expectation of saving as nexus file that will be estabilished.

It also seems like things are save as .csv as an interim solution and then all data saved in a .h5 file at the end. I imagine this is for computation that fails. Should we look in to "appending" to the .h5 file? @danielballan is this possible?

What havens to the .csv files once there is a master .h5 file?

@ambarb ambarb added _commonspeckle part of V2, but strictly related to a common repo (speckle + maybe scattering) _futurepyCHX part of V2, future pyCHX once XPCS/speckle analysis is fully separated discussion labels Feb 8, 2021
@ambarb
Copy link
Collaborator Author

ambarb commented Feb 8, 2021

Since the final goal is a Databroker of results, I say the current functions should stay in _futurepyCHX until that happens.

If someone is interested in making a file writer for Nexus, then this can be imported into _commonspeckle or live in _commonspeckle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_commonspeckle part of V2, but strictly related to a common repo (speckle + maybe scattering) discussion _futurepyCHX part of V2, future pyCHX once XPCS/speckle analysis is fully separated
Projects
None yet
Development

No branches or pull requests

1 participant