Improve zoom.ipynb notebook structure + content
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Executive summary
Adding two different notebooks, adding new 3He files, Question about 2D plotting
Context and background knowledge
- Adding two different notebooks for a 3He cell analyzer with (a) unpol-in and (b) polarized-in DirectBeam data (coming here) - still with some todos inside
- Adding new 3He files (see attachment "Data_files.zip")
To-Dos:
- Adding I(Qx,Qy) to the corrected datasets + plot it
- Adding
TotalPolarizationCorrectedDatato the corrected channels (currently only the UpUp contibution is taken into account)
Inputs
-
file "zoom_unpol-in.ipynb"
-
file "zoom_pol-in.ipynb"
(will both be uploaded here soon, currently have problems with visa) -
3He datafiles: "Data_files.zip"
Methodology
Have updated the zoom notebook a bit, please check.
Outputs
two different workflows for data corrections of a 3He analyzer cell which has been characterized with (a) an unpolarized incoming beam and (b) with a polarized incoming beam.
Which interfaces are required?
Integrated into reduction workflow
Test cases
Based on ZOOM example data
Existing implementations
No response
Comments
No response
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
Start by reviewing the existing zoom notebook and the proposed inputs, zoom_unpol-in.ipynb, zoom_pol-in.ipynb, and Data_files.zip, once they are available. Determine how the two workflows fit into the reduction workflow, then verify the I(Qx,Qy) plots and TotalPolarizationCorrectedData output against the ZOOM example data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100