Closed GoogleCodeExporter closed 9 years ago
I think those very small values are actually what happens when Cantera treats
the sparse array as a dense array and reads uninitialized memory beyond the end
of the array (since the sparse array is much smaller than the dense one would
be).
Original comment by yarmond
on 25 Jan 2013 at 4:51
Original comment by yarmond
on 25 Jan 2013 at 4:51
Attached please find a patch to check if a property value is specified by a
sparse array. I'm not sure what the performance implications of this check
would be, or whether it is even necessary, but since this bug was here and the
fix seemed simple, I thought why not.
Bryan
Original comment by bryan.w....@gmail.com
on 5 Jan 2014 at 6:08
Attachments:
The above patch is based on r2644.
Original comment by bryan.w....@gmail.com
on 5 Jan 2014 at 6:13
This issue was closed by revision r2659.
Original comment by yarmond
on 6 Jan 2014 at 6:46
This issue was closed by revision r2694.
Original comment by yarmond
on 23 Jan 2014 at 3:06
Original issue reported on code.google.com by
yarmond
on 25 Jan 2013 at 4:50