Ticket #8832 (closed: fixed)
Indirect Bayes: ResNorm workflow is slightly broken for file based input
Reported by: | Samuel Jackson | Owned by: | Samuel Jackson |
---|---|---|---|
Priority: | major | Milestone: | Release 3.2 |
Component: | Indirect Inelastic | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Reuter |
Description
There's an option to use ResNorm as input to Quasi in Bayes. This is working fine from a workspace, but if you save the output of ResNorm using the option on the interface, then load it into Quasi you get and error.
This is simply because we're looking for a workspace that isn't present in the saved file. We should be able to fix this by editing the output of ResNorm to save files properly.
Also, the ResNorm system test for Quasi will need to be updated account for these changes.
Change History
comment:1 Changed 7 years ago by Samuel Jackson
- Summary changed from Indirect Bayes: ResNorm workflow is slightly broken for files based input to Indirect Bayes: ResNorm workflow is slightly broken for file based input
comment:2 Changed 7 years ago by Samuel Jackson
- Status changed from new to inprogress
Refs #8832 Fix workspace file name.
Changeset: fb738e87f6e7b0bf1ca2e9e14e856ef370054b97
comment:3 Changed 7 years ago by Samuel Jackson
To Tester
You'll need to build this on Windows and in Release mode. On indirect bayes, run ResNorm and save it to file, then select the same file using the ResNorm option on the Quasi interface and run Quasi. This should now work.
comment:4 Changed 7 years ago by Samuel Jackson
- Status changed from inprogress to verify
- Resolution set to fixed
comment:5 Changed 7 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
comment:6 Changed 7 years ago by Michael Reuter
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/bugfix/8832_resnorm_workflow'
Full changeset: d60d321a93a1a49112fb9039c871799cf5eeac37