Ticket #1630 (closed: fixed)
Read data from MDWorkspace into Visualisation datasets
| Reported by: | Nick Draper | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | critical | Milestone: | Iteration 28 |
| Component: | VATES | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Ronald Fowler |
Description
Read attribute values, such as signal, error and number of contributing pixels into visualisation datasets.
Change History
comment:2 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 27 to Iteration 28
Bulk move of tickets at the end of iteration 27
comment:4 Changed 10 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
Factories in VATES now handle this behaviour. see #1624. The image part of the MDWorkspace is passed to various concrete implementations of vtkDataSetFactory. These handle the generation of vtkDataSets from MDWorkspace MDImages in various ways. These Factories are injected from the top-level visualisation plugin where decisions on usage are made by the user. There is more scope to provide additional features here in future. Note that only signal is currently handled to save on memory size. If error and npix actually need to be visualized then we may add this feature under a separate ticket in the future.
comment:5 Changed 9 years ago by Ronald Fowler
- Status changed from verify to verifying
- Tester set to Ronald Fowler
comment:6 Changed 9 years ago by Ronald Fowler
- Status changed from verifying to closed
Inspection of vtkStructuredGridFactory and vtkThresholdingUnstructuredGridFactory show that the signal data is transferred to the returned vtkFloatArray for use in visualisation. The unit tests on these classes work and show that the correct data is returned. The signal data is normally double while the vtk data is of type float. This should not be a problem for any expected signal levels.
Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.