Ticket #2858 (closed: invalid)
SaveISISNexus - Will write unreadable files
Reported by: | Michael Whitty | Owned by: | Nick Draper |
---|---|---|---|
Priority: | major | Milestone: | Release 2.5 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Unsure whether this is really an issue, as Roman tells me that this algorithm isn't really a part of Mantid as such. Tickets are better than emails though.
If SaveISISNexus ( #2608 ) can not find particular log files when loading the raw, it will generate a Nexus file that can then not be read. This can be seen by testing it with pretty much any of the raw files in Test\Data.
Do we need to guard against this, and have it throw rather than saving a useless file that the user may think is what they want?
Change History
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 29 to Iteration 30
"New" tickets moved at the code freeze of iteration 29
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:4 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:7 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:9 Changed 8 years ago by Nick Draper
- Status changed from new to verify
- Resolution set to invalid
This was a very special purpose algorithm that is not considered part of Mantid
comment:10 Changed 8 years ago by Nick Draper
test
comment:12 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 3705