scipp / scipp/ess

Improve zoom.ipynb notebook structure + content

Open
#405 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

esspolarization
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
  1. 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
  2. Adding new 3He files (see attachment "Data_files.zip")

To-Dos:

  1. Adding I(Qx,Qy) to the corrected datasets + plot it
  2. Adding TotalPolarizationCorrectedData to the corrected channels (currently only the UpUp contibution is taken into account)
Inputs
  1. file "zoom_unpol-in.ipynb"

  2. file "zoom_pol-in.ipynb"
    (will both be uploaded here soon, currently have problems with visa)

  3. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.