Ticket #6220 (closed: fixed)
Cannot load MDEW files into ParaView
Reported by: | Owen Arnold | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | critical | Milestone: | Release 2.4 |
Component: | VATES | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Reuter |
Description
Seems to throw at the point of opening the file (when using LoadMD file-backed).
We really ought to get this fixed. As the default behaviour is to run LoadMD filebacked.
Attachments
Change History
comment:3 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
Tester: This will have to be tested manually by following the steps below. Note that we have no automated testing framework for ParaView (not possible without GUI tests). Also, the particular component modified, has not been written to be fully MVP (perhaps it should be), in which case unit tests could be provided.
- Open ParaView ensuring that PV_PLUGIN_PATH env variable has been set to point to the Mantid pv_plugins directory. Look in the menu Tools->ManagePlugins and you should see the MantidParaview... type plugins have been loaded.
- Open a MDEW nexus file. I suggest using the SEQ_MDEW.nxs file in the system tests Data directory. This should automatically bring up the reader.
- Ensure that the "Load All Into Memory" option on the PV properties dialog is turned OFF. Hit 'Apply' on the reader and it should load the MDEW file. You should see a screen similar to the one in the attachment.
comment:4 Changed 8 years ago by Owen Arnold
refs #6220. Fixed. Can now load in PV File Backed.
The prolem actually occured with the new reader. When the PV framework was deciding which reader to user (running canReadFile) it passed over the vtkNexusPeaksReader. The canReadFile implementation here opened the nexus file, but did not close it. Thefore it could not be reopened when the correct reader was finally chosen by ParaView.
Changeset: 2a10441677a88cc17003f49ae55f066011c715ad
comment:5 Changed 8 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
refs #6220. Fixed. Can now load in PV File Backed.
The prolem actually occured with the new reader. When the PV framework was deciding which reader to user (running canReadFile) it passed over the vtkNexusPeaksReader. The canReadFile implementation here opened the nexus file, but did not close it. Thefore it could not be reopened when the correct reader was finally chosen by ParaView.