MantisBT - ParaView | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0011836 | ParaView | Bug | public | 2011-02-10 10:26 | 2016-08-12 09:58 |
| Reporter | Paul Edwards | ||||
| Assigned To | Kitware Robot | ||||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | moved | ||
| Platform | OS | OS Version | |||
| Product Version | Development | ||||
| Target Version | Fixed in Version | ||||
| Project | |||||
| Topic Name | |||||
| Type | |||||
| Summary | 0011836: Probe location giving incorrect results | ||||
| Description | The probe location filter is too lenient when matching a surface. If used with a multiblock dataset containing surfaces and volumes it will give incorrect results when probing near to a boundary. (this is particularly bad when the velocity is 0 at a wall for CFD solvers). | ||||
| Steps To Reproduce | You can see how high the tolerance is by creating a Wavelet source (all default values) and then using the "ProbeLocation" filter at point (10.9, 0, 0) - this is quite far out of the volume but it still returns a valid match. | ||||
| Additional Information | I've looked in vtkProbeFilter (vtkProbeFilter::ProbeEmptyPoints) and notice that the tolerance is set to: diagonal_length_squared / 1000 Could we change this to?: diagonal_length_squared / 1000000 | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-02-10 10:26 | Paul Edwards | New Issue | |||
| 2016-08-12 09:58 | Kitware Robot | Note Added: 0037921 | |||
| 2016-08-12 09:58 | Kitware Robot | Status | backlog => closed | ||
| 2016-08-12 09:58 | Kitware Robot | Resolution | open => moved | ||
| 2016-08-12 09:58 | Kitware Robot | Assigned To | => Kitware Robot | ||
| Notes | |||||
|
|
|||||
|
|
||||