netCDF CF reader fails to read time steps when some are corrupted
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
ParaView expects time values to be monotonically increasing (rationally enough). However, we have run into some netCDF files using the CF convention that have some mangled time values at the end. The netCDF/CF reader blindly adds these non-monotonic time values to the time steps list and uses them for a time range. This cause bad behavior in ParaView (in our case, ignoring all time values from the reader). The attached file demonstrates this behavior. It has time values but ParaView does not show any time in the data.
Although you could argue that these netCDF files are malformed, the reader should manage them better by ignoring any time values that appear out of sequence so that those that are in sequence are correct.