[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #63704] isosurface returns incorrect results f

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #63704] isosurface returns incorrect results for data bigger than small
Date: Mon, 30 Jan 2023 12:38:35 -0500 (EST)

Update of bug #63704 (project octave):

                  Status:               Confirmed => Ready For Test         
         Planned Release:                    None => 8.1.0 (current stable) 


Follow-up Comment #2:

In Octave 6 and before, entering hexadecimal integers resulted in a double
precision floating point number. Since Octave 7, the result in unsigned
integer types matching the number of entered digits.

Many mixed operations between integer type values and double precision
floating point numbers result in integer type values.
Those exhibit saturation behavior when they exceed their respective limits.
That led to the observed issues when isosurfaces with many vertices where
created in Octave version 7 or later.

I pushed the following change to the stable branch of Octave to cast a matrix
with hexadecimal input to "double" to revert to the behavior of that function
in version 6 and before:

This should be part of the upcoming Octave 8.

Marking as ready for test.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]