scipp / scipp/ess

Zoom test-data: explanations & read-out

Open
#422 0 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

The example polarization data from ZOOM (attached) (long 3He runs for data reduction with glassy carbon as non-magnetic sample (GC) for reference):
1) I^(DB, unpol-in, cell):
#691 693 695 697
2) I^(++, +-, -+, --):
#690 692 694 696
--> dont have these, ask Diego again (but sample data from users, so maybe not accessible)
--> maybe can use GC measurements in folder "3He_GC" for sample-measurements?
3) I^(DB, unpol-in, cell)_background:
#698
--> for background subtraction
--> they have made an extra measurement, whereas we chose to just take the bg and some edge of the detector at certain Q
4) I^(DB, depol, cell):
#699
5) I^(DB, no-cell)
--> missing compared to our workflow!
--> just for normalization, maybe possible to set to 1?
6) Probably related to the "unpolarized SANS" workflow:
#706
--> "TRANS Reference of DB with GC"
--> sample transmission correction

Note: each ZOOM-file contains all 4 spin-values that we need to extract out to match to our workflow, see note above
I_DB_depol_Cell.zip
I_DB_unpol_in_cell_BG.zip
I_DB_unpol_in_Cell.zip

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 inspecting the attached I_DB_depol_Cell.zip, I_DB_unpol_in_cell_BG.zip, and I_DB_unpol_in_Cell.zip, then compare their measurements with the unpolarized SANS workflow described in the issue. Document how the listed ZOOM files and spin values map to the workflow, and resolve or record the missing no-cell and spin-resolved data questions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Documentation
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.