CFSDat timevalues with Ensight reader incorrect
Summary
CFSDat with the ensight gold reader reads in values of low precision for the time values in .case files. The values are rounded to 6 decimals in the reader. Increasing the precision above 8 crashes some testcases. Also, the startTime is automatically set to 0.0 if deleteOffset is not specified.
This issue has been partially fixed in commit 69c5cf71
Example Input or way to reproduce
Any ensight file with a time step like 3.269312757
What is the current bug behavior?
Error message despite providing correct inputs
What is the expected correct behavior?
No error message, reading in values correctly and at double precision
Possible fixes
see !113 (merged)
Edited by Patrick Heidegger