We should write the scan variable to the MFILE
Open
Nobody has claimed this yet.
papercut
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
Description
As mentioned in #4482 we should write the scan variable to the mfile and then use that in plotting
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 reading issue #4482, then trace where the scan variable is produced, where the MFILE is written, and how plotting currently obtains it. Confirm the expected MFILE entry and plotting behavior with the existing workflow; done means the scan variable is persisted and plotting uses that persisted value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100