Opened 8 years ago
Closed 6 years ago
#45 closed defect (fixed)
Postproc crashes when reading 2D result with partial profile cut
Reported by: | ghorwin | Owned by: | ghorwin |
---|---|---|---|
Priority: | critical | Milestone: | 2.0.16 |
Version: | 2.0.x | Keywords: | |
Cc: | Operating System: | all |
Description
Simulation geometry 2D:
- selecting a profile cut that spans only one row gives a 3D data format
- the extractor 2Dfrom3D (time-cut of profile) is being used
Problem:
- when cut is being made over entire width of construction, x-coordinates of selected elements also span all columns, thus for all selected elements and their individual column indexes a coordinate exist.
*But*: when only part of the line is selected, i.e. only a few elements in that line, than the x-coordinate vector will only have as many elements. When associating the corresponding value the column-index of some selected values will be out of range and cause an access violation.
Options:
- either change detection of data format to use whole geometry (i.e. any 2D geometry would result in a 4D file) and consequently profile cuts would always require a value cut at exactly this location/coordinate (also requires error handling when trying to plot a 2D color map from such a profile output)
- fix 2Dfrom3D Extractor to recognize this situation and do an additional reverse lookup in order to avoid access violation.
Change History (4)
comment:1 by , 7 years ago
Milestone: | → Future |
---|
comment:2 by , 7 years ago
Milestone: | Future → 2.0.16 |
---|
comment:3 by , 7 years ago
Version: | 2.1 → 2.0.x |
---|
comment:4 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Related to ticket #146. Fixed.