- Jan 28, 2014
-
-
Dave DeMarle authored
Thanks Vadim Roytershtey and Homa Karimabadi for the test data set. Test only enabled with VTK_USE_LARGE_DATA = ON Change-Id: Ic04681dbffcc57ed27377ca5f3cae015249a7308
-
- Aug 18, 2013
-
-
Sean McBride authored
Change-Id: I94935b6fe4d5e76e453507f9387b5ca357286cab
-
- May 11, 2012
-
-
Yuanxin Liu authored
The main change is to remove the use of vtkTemporalDataSet and move the support of multiple temporal data sets from the execution pipeline to filters. To be specific, - Before, a filter can request objects from multiple time steps by setting the key UPDATE_TIME_STEPS to a vector of doubles; the resulting objects get wrapped by the pipeline into a single vtkTemporalDataSet object. - After, a filter can only ask for a single time step from the pipeline by setting the key UPDATE_TIME_STEP to a single double. The "wrapping" no longer happens. If a filter want to request multiple time steps, it needs to either inherit from vtkMultiTimeStepAlgorithm or use the CONTINUE_EXECUTION to loop the upstream pipeline and store the data from each iteration. The following key changes/constants are backward incompatible: vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEPS(() -> vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP((), vtkMultiStepAlgorithm::UPATE_TIME_STEPS() vtkStreamingDemandDrivenPipeline::PREVIOUS_UPDATE_TIME_STEPS() -> vtkStreamingDemandDrivenPipeline::PREVIOUS_UPDATE_TIME_STEP() deleted: vtkCompositeDataPipeline::REQUIRES_TIME_DOWNSTREAM() depreicated: VTK_TIME_EXTENT Change-Id: I635b6401ae4f0a7ea7c4b5c466ced40ee75963c7
-
- May 08, 2012
-
-
Chris Harris authored
Change-Id: I586db1fa8e06311d08f4bc977485cecd3a520020
-
Chris Harris authored
The #ifdef are unecessary as the TotalRank is used as a guard and the code will not run in the serial case. Change-Id: I9035dfd9738b7e35ae0ed2be4512c140f7314356
-
- May 04, 2012
-
-
Chris Harris authored
Change-Id: Ib1af2fe2ffb41d57663fed590795a3b60d2dbf78
-
Chris Harris authored
The third party module vtkVPIC can be build with or without MPI. Rather than building a MPI and non MPI version we still need the ability to switch between the two implementations. This can use done by move the reader into a separate module and providing VTK_VPIC_USE_MPI. This break with rule of not having a module change it behaviour based on compile options but unless the third party library is refactored we will have to live with this. Change-Id: Ia949e1860272ad5ddb7b9b4cb9eb8d88305a5783
-