Skip to content
Snippets Groups Projects
This project is mirrored from https://gitlab.kitware.com/vtk/vtk-m.git. Pull mirroring updated .
  1. Jan 08, 2013
    • David Thompson's avatar
      Eliminate warnings. · b431644c
      David Thompson authored
      This should also allow query selections on field data to
      be plotted over time (though ParaView does not yet support them).
      
      Change-Id: Ia7e19723c9c2fca46bbdb08b9befe3f447fb2959
      b431644c
  2. Jan 03, 2013
    • David Thompson's avatar
      Support aggregation extracting selection over time. · fa9139a5
      David Thompson authored
      Instead of breaking a selection into a separate time-history
      table for each (block,ID)-tuple, you may call
      ReportStatisticsOnly(). Then a single table per
      block of the input dataset will report the minimum, maximum,
      quartiles, and (for numerical arrays) the average and standard
      deviation of the selection over time.
      
      This adds dependencies on the FiltersGeneral and
      FiltersStatistics modules to the FiltersExtraction module.
      
      Change-Id: I42c2ef3314a3a4497bd50e1c0dd6cc9fde8ce5fb
      fa9139a5
  3. May 11, 2012
    • Yuanxin Liu's avatar
      remove vtkTemporalDataSet and push its pipeline support to filters · be247f1d
      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
      be247f1d
  4. Apr 13, 2012
    • Berk Geveci's avatar
      Fixed and added to the vtkAlgorithm's update extent API. · 70008198
      Berk Geveci authored
      Fixed: SetUpdateExtent() and its ilk were setting the update
      extent on the input. Fixed it to be on the output. This is
      more consistent with the executive API. Also updated other
      code accordingly.
      
      Change-Id: Iac92df21b8fa8dbeb58e4e27c5ffc796fadc4eaa
      Added: API to get update extent from the output.
      70008198
  5. Apr 09, 2012
    • VTK Developers's avatar
      Remove trailing whitespace from all source files · 2d323fc4
      VTK Developers authored
      Exclude ThirdParty, Utilities/MetaIO, and Utilities/KWSys as these
      are maintained outside VTK.
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      Co-Author: Brad King <brad.king@kitware.com>
      2d323fc4
    • VTK Developers's avatar
      Modularize VTK tree layout · cdd4d6fd
      VTK Developers authored
      Move source files from their former monolithic VTK location to their new
      location in modular VTK without modification.  This preserves enough
      information for "git blame -M" and "git log --follow" to connect
      modularized VTK files to their original location and history.
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      Co-Author: Brad King <brad.king@kitware.com>
      Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>
      cdd4d6fd
  6. Dec 13, 2011
  7. Sep 19, 2011
    • Berk Geveci's avatar
      Replace SetInput etc. with SetInputData etc. · 4ea36770
      Berk Geveci authored
      Since the behaviour of SetInput changed - it no
      longer connects the pipeline but sets up the data
      object as the input -, it was decided to rename
      it to SetInputData. This includes similar methods
      such as AddInputData. This commit makes on
      sweeping change that compiles.
      4ea36770
  8. May 20, 2010
    • Mark Olesen's avatar
      Remove vtk(Cxx|Type)RevisionMacro · ecbbf7f7
      Mark Olesen authored
      The CVS $Revision$ keyword replacement will no longer maintain these
      macros automatically.  They were used only to implement CollectRevisions
      and vtkObjectBase::PrintRevisions, an API that was never used.
      
      Automated as follows:
      
        pass 0:
        catch templates
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'
      
        pass 1:
        main changes
        ---------------
        $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
          echo "$file" 1>&2
          perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
        done
        $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
          echo "$file" 1>&2
          perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
        done
      
        pass 2:
        verify
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'
      
      Fixed multi-line vtkCxxRevisionMacro and templates by hand.
      ecbbf7f7
  9. Apr 23, 2010
    • Mark Olesen's avatar
      Remove vtk(Cxx|Type)RevisionMacro · 19c55e0e
      Mark Olesen authored
      The CVS $Revision$ keyword replacement will no longer maintain these
      macros automatically.  They were used only to implement CollectRevisions
      and vtkObjectBase::PrintRevisions, an API that was never used.
      
      Automated as follows:
      
        pass 0:
        catch templates
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'
      
        pass 1:
        main changes
        ---------------
        $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
          echo "$file" 1>&2
          perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
        done
        $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
          echo "$file" 1>&2
          perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
        done
      
        pass 2:
        verify
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'
      
      Fixed multi-line vtkCxxRevisionMacro and templates by hand.
      19c55e0e
  10. Jan 08, 2010
    • Utkarsh Ayachit's avatar
      ENH: Fixed BUG #10076. · acda7bc8
      Utkarsh Ayachit authored
      * Moving vtkExtractSelectedRows from InfoVis to Graphics.
      * Adding support to vtkExtractSelectedRows to optionally produce
        vtkOriginalRowIds array.
      * Extended vtkExtractSelection to use vtkExtractSelectedRows to extract rows
        from vtkTable.
      * Fixed vtkExtractArraysOverTime to work with vtkTables.
      acda7bc8
  11. Sep 09, 2009
  12. Mar 17, 2009
  13. Dec 19, 2008
  14. Dec 02, 2008
    • Jeffrey Baumes's avatar
      ENH: Flattening vtkSelection from a recursive tree to a list of vtkSelectionNode instances. · 6ce350bc
      Jeffrey Baumes authored
      * All parameters such as content type, field type, selection list are on
        vtkSelectionNode.
      * All constants are on vtkSelectionNode instead of vtkSelection.
      * The SELECTIONS content type is deprecated.
      * To create a simple single-node selection, you must create an
        instance of vtkSelectionNode and an instance of vtkSelection, and add
        the node to the selection. You may also use vtkSelectionSource.
      * vtkConvertSelection has a few new useful static functions
        To obtain the list of selected items in a data object.
      6ce350bc
  15. Aug 06, 2008
  16. Apr 29, 2008
  17. Apr 23, 2008
  18. Mar 26, 2008
  19. Mar 25, 2008
    • Utkarsh Ayachit's avatar
      ENH: Fix vtkExtractArraysOverTime to work with composite datasets. Also... · df54a2f4
      Utkarsh Ayachit authored
      ENH: Fix vtkExtractArraysOverTime to work with composite datasets. Also changing the implementation to use vtkExtractSelection filter to extract the selection. Also, it now produces a multi-block output. Thus, making is possible to extract multiple cells/points over time.
      
      ENH :Added a new vtkProbeSelectedLocations which uses vtkProbe to probe different locations indicates by the vtkSelection.
      
      BUG: Update the proxy tab information when the information is gathered by the source proxy.
      
      BUG: Don't bother doing any globalId-id conversions if the number of ids==0
      df54a2f4
  20. Feb 23, 2008
  21. Oct 19, 2007
  22. Sep 17, 2007
  23. Aug 01, 2007
  24. Jul 29, 2007
  25. May 21, 2007
  26. May 17, 2007
    • Dave Demarle's avatar
      BUG: Work around a hard to fix bug by not using... · afeffa5e
      Dave Demarle authored
      BUG: Work around a hard to fix bug by not using vtkDataSetAttribute::InterpolateAllocate/InterpolatePoint. The bug shows up, in parallel, when the point data has a globalIDS attribute, on the first probe. In that case the arrays at allocate lack the globalid array and later when the interpolate happens, the arrays become misaligned. To 'fix' I am doing the interpolation manually, array by array.
      afeffa5e
  27. May 15, 2007
    • Dave Demarle's avatar
      BUG: correct and simplify probe location over time. Now, it produces a... · 8fb62610
      Dave Demarle authored
      BUG: correct and simplify probe location over time. Now, it produces a validity array and sets values to 0 at invalid samples instead of deleting the samples. Deleting was not OK because the extent from RequestInformation must match that produced by RequestData. Also when probing a location interpolate into the point data and copy the cell data (as long as their are no name collisions).
      8fb62610
  28. May 07, 2007
  29. Apr 15, 2007
  30. Apr 08, 2007
  31. Apr 07, 2007
  32. Mar 22, 2007
Loading