Ticket #7701 (closed: fixed)
EQSANS: make sure transmission workspaces are created
Reported by: | Mathieu Doucet | Owned by: | Mathieu Doucet |
---|---|---|---|
Priority: | major | Milestone: | Release 3.0 |
Component: | SANS | Keywords: | PatchCandidate |
Cc: | Blocked By: | ||
Blocking: | Tester: | Martyn Gigg |
Description
The transmission workspaces that are computed and used in the EQSANS reduction don't end up in the ADS. Make sure that is the case.
Change History
comment:2 Changed 7 years ago by Mathieu Doucet
- Status changed from inprogress to verify
- Resolution set to fixed
To test:
- Start the EQSANS reduction UI and do a reduction, making sure to enter files in the transmission fields. It would be a good idea to try runs 1466 and 3293 since they will exercise two different paths in the transmission calculation. You can use the same run for both data and the two transmission runs (which will produce transmission = 1.0).
- Start the BIOSANS reduction UI and test it with direct beam transmission.
In both cases above a transmission workspace should be produced. It may have a weird name, which is expected.
comment:4 Changed 7 years ago by Martyn Gigg
- Status changed from verify to verifying
- Tester set to Martyn Gigg
comment:5 Changed 7 years ago by Mathieu Doucet
Re #7701 Add transmission as output (cherry picked from commit c753a09acd8ff461fecd44584c448395793c3a85)
Changeset: b8c305b5318eb2f09e99b8ee0e8ccfd26f17eed4
comment:6 Changed 7 years ago by Mathieu Doucet
Re #7701 Fix transmission workspace name in frame skipping mode
Changeset: 41740403423680433d88aa618b1c6789d7b50f1e
comment:8 Changed 7 years ago by Mathieu Doucet
Re #7701 Fix transmission workspace name in frame skipping mode (cherry picked from commit 41740403423680433d88aa618b1c6789d7b50f1e)
Changeset: ce13fe3da975e886f9c625490b50a412084f03fe
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 8546
Re #7701 Add transmission as output
Changeset: c753a09acd8ff461fecd44584c448395793c3a85