Ticket #3348 (closed: fixed)
Paraview: plugin for loading MDEventWorkspace .nxs files
Reported by: | Janik Zikovsky | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | major | Milestone: | Iteration 30 |
Component: | VATES | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Reuter |
Description
The Saving/Loading of MDEventWorkspaces to .NXS files is making progress.
It would be useful to have a Paraview plugin that loads MDEventWorkspaces from those .nxs files directly instead of going through the EventNexus format files. So far in my tests it has been faster to load a file than doing the conversion from scratch.
The algorithm to do the loading is called (for now) LoadMDEW. Owen, could you implement this? Does it cause a problem that the files have the same extension (.nxs)? We can change the extension for MDEW nxs files if that's needed.
Change History
comment:2 Changed 9 years ago by Owen Arnold
Confirmed that Paraview will attempt to pick up another reader (handling the same extension type) if file loading one is diallowed via CanReadFile small example.
comment:6 Changed 9 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
comment:7 Changed 9 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
Agree that this would be an improvement. Should be very simple to implement. PV provides a CanReadFile method. (At the moment I've set this to always be true on existing readers). My understanding is that this gives the ability to select amonst readers when the same file exension is presented. If this works, we would need some way of determining what type of data lies in the file (without reading the whole file) so that true/false can be returned.