Report of test of widgets for DREAM
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
EDIT by @jl-wynen: Added links to issues
Feedback of test of workflow-widget-dream.ipynb (Dec 3rd 2024)
- The header should be corrected since it refers to LoKI. It could be replaced by
This notebook illustrates how we can use ESSreduce’s workflow widgets to generate a graphical interface for running a Diffraction reduction workflow using simulated data for DREAM.
-
Which entries are compulsory or optional? (https://github.com/scipp/ess/issues/107)
-
Only csv files are supported for loading. And there is no indication on the supported format. (https://github.com/scipp/ess/issues/106)
-
A kind of file uploader would be useful.
-
What are the "Extended Outputs"? The list of items does not seem to be all linked with DREAM or Diffraction (like Monitor1,2...6)
-
For the bank name, the interface failed when I typed the name with a capital letter. It could be useful for future versions to have "RadioButtons", "Select" or "SelectMultiple" from ipywidgets to avoid misspelling issues. (https://github.com/scipp/ess/issues/499)
-
It is difficult to see if there are any processes running or if the interface is stuck (https://github.com/scipp/ess/issues/105)
-
Selecting "DreamGeant4ProtonChargeWorkflow" and ReducedTofCIF as typical output, I get an error
(https://github.com/scipp/ess/issues/104)
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 with workflow-widget-dream.ipynb and review the listed feedback against linked issues 104, 105, 106, 107, and 499. Determine which items remain unresolved and whether this report should be split; the work is done when each actionable concern is resolved or tracked in a separate issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- documentation, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100