File storage and data handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Here I will be updating the new information on file storage and data handling so we can decide on how to read on the polarized data:
Data structure:
- it will be user, beamtime, & instrument dependent which data is recorded in one or in several .nxs files.
- the only common "agreement" is that fast changes (e.g. stroboscopic measurements) shall be in one .nxs.
- for polarization: it might happen that sometimes we have to read out from different and sometimes from the same .nxs file, both would need to be possible!
People to contact:
Massimiliano Novelli: Deciding on data structure and .nxs file handling for LokI+DREAM (relevant instruments)
Fredrik Ericsson: Deciding on which values will be readable from scicat (e.g. searching for polarizer state possible?)
Questions: Do you already work on this kind of problem how to read in the status of certain properties in one .nxs if its not defined if it will be one file or several? How important will it be for the next steps in this work?
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 resolving the .nxs data-structure and polarization requirements with the listed contacts, then define how completion will be verified for one or multiple files and the Scicat-readable properties.
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