Writing Temporal Data: Difference between revisions
(New page: One of the ParaView 3.2 deliverables includes adding an option to the vtkExodusIIWriter to write out multiple timesteps (all of them, for now). First I'd like to share the design/implement...) |
No edit summary |
||
| Line 3: | Line 3: | ||
When File --> Save Data is selected in the GUI, and the writer factory finds the appropriate vtkSMWriterProxy, we'll then check to see if this writer has a boolean property called "WriteAllTimeSteps". If it does, the user will be asked in a dialog box whether to write out all timesteps or just the current one. The "WriteAllTimeSteps" property in the writer then gets set accordingly. | When File --> Save Data is selected in the GUI, and the writer factory finds the appropriate vtkSMWriterProxy, we'll then check to see if this writer has a boolean property called "WriteAllTimeSteps". If it does, the user will be asked in a dialog box whether to write out all timesteps or just the current one. The "WriteAllTimeSteps" property in the writer then gets set accordingly. | ||
I've modelled the changes to vtkExodusIIWriter after vtkExtractDataOverTime. If the input information object contains a TIME_STEPS() key, it's used to set the writer's NumberOfTimeSteps data member. If the WriteAllTimeSteps flag is set, then the request is executed for each timestep. | I've modelled the changes to vtkExodusIIWriter after vtkExtractDataOverTime. If the input information object contains a TIME_STEPS() key, it's used to set the writer's NumberOfTimeSteps data member. If the WriteAllTimeSteps flag is set, then the request is executed for each timestep, thus WriteData() gets called on each timestep. | ||
Latest revision as of 22:07, 22 May 2007
One of the ParaView 3.2 deliverables includes adding an option to the vtkExodusIIWriter to write out multiple timesteps (all of them, for now). First I'd like to share the design/implementation with the group for feedback. But I'd also like to raise the question of whether some of this functionality should actually be in vtkWriter.
When File --> Save Data is selected in the GUI, and the writer factory finds the appropriate vtkSMWriterProxy, we'll then check to see if this writer has a boolean property called "WriteAllTimeSteps". If it does, the user will be asked in a dialog box whether to write out all timesteps or just the current one. The "WriteAllTimeSteps" property in the writer then gets set accordingly.
I've modelled the changes to vtkExodusIIWriter after vtkExtractDataOverTime. If the input information object contains a TIME_STEPS() key, it's used to set the writer's NumberOfTimeSteps data member. If the WriteAllTimeSteps flag is set, then the request is executed for each timestep, thus WriteData() gets called on each timestep.
