where should functions that save XPCS / speckle results go?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 8
- Forks
- 12
- Avg merge
- 2h 53m
- Merged PRs (30d)
- 6
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing functions that write speckle or XPCS results to CSV and H5 files, then determine the intended ownership and lifecycle of those outputs. Done means the repository has a decided location and documented behavior for appending to H5 files and handling interim CSV files.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100