(0014896)
Ken Moreland (manager)
2009-02-11 11:28

This is not a problem with the reader as reported. Rather, this is a problem with the data in the attached multipleProcessorRestartExample.zip file. Look carefully at the time values for the exampleRestart.e-s.0002.2.* files. The have values that range 0-6 when in fact they should range 3-9 (as the time values in restartFiles.e-s.000 do). Because the time values in the data are wrong, it is impossible for the restart reader to resolve the appropriate time step to load (the old computer adage "garbage in, garbage out").

Fix the time step values in exampleRestart.e-s.002.2.* and it should work just fine.

(0015007)
Alan Scott (manager)
2009-02-16 21:52

Correcting the multiple processor file example.

(0015008)
Alan Scott (manager)
2009-02-16 21:54

The zip file that shows the problem is multipleProcessorRestartExampleGood.zip (meaning correct files, not correct behavior)

(0015031)
Alan Scott (manager)
2009-02-17 13:16

I tried running the multiple block dataset (attached), and it seems to have the time steps loaded correctly, but puts out the following errors:

Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 6003
vtkPExodusIIReader (0B060BD8): No arrays named "thickness" of the specified type (14).

Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 5079
vtkExodusIIReaderPrivate (0B061328): You requested array -1 in a collection of only 2 arrays.

Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 5894
vtkPExodusIIReader (0B060BD8): No objects named "Unnamed block ID: 9 Type: quad Size: 129" of the specified type (1).

Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 2760
vtkExodusIIReaderPrivate (0B061328): You requested Element block -1 in a collection of only 2 objects.

(0015033)
Ken Moreland (manager)
2009-02-17 13:19

The problem is again in the data set. Now the time values are right, but the variable names are wrong. In the first data set, the variable names are in lower case. In the second data set, the variable names are in upper case. The errors you are getting are from the assumption that all data sets have the same variables with the same names.

(0015097)
Alan Scott (manager)
2009-02-17 19:41

Sounds correct to me. Grrr - the dataset was made from the same source, and the tools I used changed the case of the variables. Nuts.

Tested Client/Server on numerous pvservers.

Issue History
Date Modified	Username	Field	Change
2009-02-10 20:03	Alan Scott	New Issue
2009-02-10 20:03	Alan Scott	File Added: singleProcessorRestartExample.zip
2009-02-10 20:04	Alan Scott	File Added: multipleProcessorRestartExample.zip
2009-02-11 09:17	Ken Moreland	Status	backlog => tabled
2009-02-11 09:17	Ken Moreland	Assigned To	=> Ken Moreland
2009-02-11 11:28	Ken Moreland	Note Added: 0014896
2009-02-11 11:28	Ken Moreland	Status	tabled => @80@
2009-02-11 11:28	Ken Moreland	Resolution	open => not fixable
2009-02-16 21:52	Alan Scott	Note Added: 0015007
2009-02-16 21:52	Alan Scott	Status	@80@ => tabled
2009-02-16 21:54	Alan Scott	File Added: multipleProcessorRestartExampleGood.zip
2009-02-16 21:54	Alan Scott	Note Added: 0015008
2009-02-17 13:16	Alan Scott	Note Added: 0015031
2009-02-17 13:19	Ken Moreland	Note Added: 0015033
2009-02-17 13:19	Ken Moreland	Status	tabled => @80@
2009-02-17 16:52	Utkarsh Ayachit	Category	3.6 => Pending
2009-02-17 19:41	Alan Scott	Note Added: 0015097
2009-02-17 19:41	Alan Scott	Status	@80@ => closed
2009-05-13 14:05	Utkarsh Ayachit	Target Version	=> 3.6
2009-05-13 14:05	Utkarsh Ayachit	Fixed in Version	=> 3.6
2011-06-16 13:10	Zack Galbreath	Category	=> (No Category)

Notes
(0014896) Ken Moreland (manager) 2009-02-11 11:28	This is not a problem with the reader as reported. Rather, this is a problem with the data in the attached multipleProcessorRestartExample.zip file. Look carefully at the time values for the exampleRestart.e-s.0002.2.* files. The have values that range 0-6 when in fact they should range 3-9 (as the time values in restartFiles.e-s.000 do). Because the time values in the data are wrong, it is impossible for the restart reader to resolve the appropriate time step to load (the old computer adage "garbage in, garbage out"). Fix the time step values in exampleRestart.e-s.002.2.* and it should work just fine.

(0015007) Alan Scott (manager) 2009-02-16 21:52	Correcting the multiple processor file example.

(0015008) Alan Scott (manager) 2009-02-16 21:54	The zip file that shows the problem is multipleProcessorRestartExampleGood.zip (meaning correct files, not correct behavior)

(0015031) Alan Scott (manager) 2009-02-17 13:16	I tried running the multiple block dataset (attached), and it seems to have the time steps loaded correctly, but puts out the following errors: Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 6003 vtkPExodusIIReader (0B060BD8): No arrays named "thickness" of the specified type (14). Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 5079 vtkExodusIIReaderPrivate (0B061328): You requested array -1 in a collection of only 2 arrays. Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 5894 vtkPExodusIIReader (0B060BD8): No objects named "Unnamed block ID: 9 Type: quad Size: 129" of the specified type (1). Warning: In ..\..\..\..\src\ParaView3\VTK\Hybrid\vtkExodusIIReader.cxx, line 2760 vtkExodusIIReaderPrivate (0B061328): You requested Element block -1 in a collection of only 2 objects.

(0015033) Ken Moreland (manager) 2009-02-17 13:19	The problem is again in the data set. Now the time values are right, but the variable names are wrong. In the first data set, the variable names are in lower case. In the second data set, the variable names are in upper case. The errors you are getting are from the assumption that all data sets have the same variables with the same names.

(0015097) Alan Scott (manager) 2009-02-17 19:41	Sounds correct to me. Grrr - the dataset was made from the same source, and the tools I used changed the case of the variables. Nuts. Tested Client/Server on numerous pvservers.

Relationships