MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014354ParaView(No Category)public2013-10-23 13:062015-01-02 10:43
ReporterGreg Vernon 
Assigned ToUtkarsh Ayachit 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.0 
Target Version4.3Fixed in Version4.3 
ProjectSandia
Topic Name
Typeincorrect functionality
Summary0014354: vtkExodusIIReaderPrivate (000000000A41D7A0): Could not retrieve time values.
DescriptionWe have been receiving an error message regarding failure to import timesteps when importing certain ExodusII files in Paraview 3.14, 3.98.1, 4.0.1, and as recently as the 10-17-2013 Nightly Build (All 64-bit versions). Version 3.12 doesn't have this bug and is the latest version we've tried that doesn't produce this error. In our testing, the error seems to be associated with file size (approx >2GB), but we’ve been unable to determine the exact circumstances that produce the error. We have an example exodus file that generates the error, but it can be easily reproduced by replicating any .e file internally until its size exceeds about 2GB. We determined this approximate limit by parsing down larger .e files with SEACAS Algebra until the file(s) loaded successfully without error. This is a relatively urgent matter for us; 15 users are experiencing this error currently.

Issue was previously reported in 2012 by J.McQueen.
Steps To Reproduce
Additional Information
Tags2GB, Exodus, ExodusII, Sierra
Relationships
related to 0015123closed Chuck Atkins VTK Update NetCDF Version in ParaView/VTK ThirdParty 
Attached Filespdf Exodus_ERROR.pdf (130,768) 2013-10-23 13:06
https://www.vtk.org/Bug/file/9545/Exodus_ERROR.pdf
Issue History
Date ModifiedUsernameFieldChange
2013-10-23 13:06Greg VernonNew Issue
2013-10-23 13:06Greg VernonFile Added: Exodus_ERROR.pdf
2013-10-23 13:09Greg VernonTag Attached: Exodus
2013-10-23 13:09Greg VernonTag Attached: ExodusII
2013-10-23 13:09Greg VernonTag Attached: Sierra
2013-10-23 13:09Greg VernonTag Attached: 2GB
2013-10-28 15:27Greg VernonNote Added: 0031746
2014-01-29 18:04Greg VernonNote Added: 0032234
2014-09-19 12:40Greg VernonNote Added: 0033373
2014-09-19 16:47Alan ScottProjectTBD => Sandia
2014-10-20 19:09Alan ScottNote Added: 0033658
2014-10-20 19:09Alan ScottSeverityminor => major
2014-10-20 19:09Alan ScottTarget Version => 4.3
2014-10-20 20:45Alan ScottNote Added: 0033659
2014-11-04 10:02Utkarsh AyachitTarget Version4.3 => bug_fix
2014-11-06 21:28Utkarsh AyachitNote Added: 0033780
2014-11-11 15:52Utkarsh AyachitNote Added: 0033793
2014-11-13 09:46Utkarsh AyachitNote Added: 0033803
2014-11-13 09:46Utkarsh AyachitStatusbacklog => gatekeeper review
2014-11-13 09:46Utkarsh AyachitFixed in Version => git-master
2014-11-13 09:46Utkarsh AyachitResolutionopen => fixed
2014-11-13 09:46Utkarsh AyachitAssigned To => Utkarsh Ayachit
2014-11-13 09:46Utkarsh AyachitStatusgatekeeper review => customer review
2014-11-13 09:46Utkarsh AyachitRelationship addedrelated to 0015123
2014-11-14 22:56Utkarsh AyachitTarget Versionbug_fix => 4.3
2014-12-02 11:26Greg VernonNote Added: 0033866
2014-12-02 15:43Alan ScottNote Added: 0033868
2014-12-02 15:43Alan ScottStatuscustomer review => closed
2015-01-02 10:43Utkarsh AyachitFixed in Versiongit-master => 4.3

Notes
(0031746)
Greg Vernon   
2013-10-28 15:27   
An SNL individual tested this error on a Unix system and was unable to reproduce the error.
Note that our workstation OS is Windows 7 64-bit.
(0032234)
Greg Vernon   
2014-01-29 18:04   
A workaround we've discovered is to re-loadbal/decomp the exodus file into smaller pieces: decomp -processors <#cpus> exodusfile.e
(0033373)
Greg Vernon   
2014-09-19 12:40   
Tested in Paraview 4.2 - RC1 and this issue is still not resolved
(0033658)
Alan Scott   
2014-10-20 19:09   
This bug is keeping the engineers at The Kansas City Plant (a customer of Sandia) from updating ParaView. This needs to be fixed in 4.3. Ask me (Alan) for the dataset - I have it, and may pass it to Kitware.
(0033659)
Alan Scott   
2014-10-20 20:45   
I have replicated this bug. 4.2.0, local server, windows. Binary from Kitware. Problem does not show up on Linux.

Open red_sample_output_fails.e. Apply. You get the error at the end of this note. When I looked in the information tab, there are no time values.


You will receive the following error:
ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D539770): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D539770): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D539770): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D539770): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000F3DEF50): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D53DBE0): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D53DBE0): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D53DBE0): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D53DBE0): Could not retrieve time values.


ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIReader.cxx, line 3712
vtkExodusIIReaderPrivate (000000000D539770): Could not retrieve time values.
(0033780)
Utkarsh Ayachit   
2014-11-06 21:28   
Tracked down the issue:

The problem is with netcdf + MSVC. The current nefcdf packaged with ParaView uses default off_t definition. With MSVC, it's long i.e. 32 bit. It needs to be 64 bit to handle large files. Latest nefcdf version (4.3.2) seems to have appropriate rules in the CMakeLists.txt to properly define off_t on Windows.
(0033793)
Utkarsh Ayachit   
2014-11-11 15:52   
Working on updating ParaView superbuild to use latest netcdf. Let's see if that address this issue.
(0033803)
Utkarsh Ayachit   
2014-11-13 09:46   
With version v4.2.0-107-gfd2f62f, the file opens without errors on Win64. Had to update the NetCDF version in ParaViewSuperbuild to the latest (4.3.2).
(0033866)
Greg Vernon   
2014-12-02 11:26   
Customer Review: Tested with v4.2.0-133-g7e996c8 64-bit (miranda.kitware - Win7x64-VS9-nightlymaster-superbuild) and was able to open an 8+GB exodusII file without error, all timesteps were present. No obvious issues detected. Bug appears to fixed from what I can tell.
(0033868)
Alan Scott   
2014-12-02 15:43   
Tested master (Kitware most recent download, Windows 64 bit), Windows, local server. Opened Greg's test data (red_sample_output_fails.e), went to time step 13. Worked like a charm.