1. 08 Jan, 2019 2 commits
  2. 18 May, 2018 1 commit
    • Kitware Robot's avatar
      ExternalData: Convert content links from MD5 to SHA512 · d6d05b2a
      Kitware Robot authored
      Populate a script with `map_<md5>=<sha512>` variable settings and
      then run the following to convert the content link files:
      
          git ls-files -- '*.md5' | while read f; do
            md5="$(cat "$f")"
            sha512="$(eval echo \${map_$md5})"
            rm "$f"
            echo $sha512 > ${f%.md5}.sha512
          done
      d6d05b2a
  3. 20 Dec, 2017 1 commit
  4. 23 Sep, 2016 1 commit
    • Kitware Robot's avatar
      Reindent using the reindentation script. · f830ff47
      Kitware Robot authored
      This commit reindents the code with the following utility:
      Utilities/Maintenance/vtk-reindent-code.py
      
      This utility changes the positions of the braces so that they are no
      longer indented relative to the code block they reside in.
      
      The bash command line used was the following:
      
      for d in Charts Common Deprecated Domains Examples Filters GUISupport \
               Geovis IO Imaging Infovis Interaction Parallel Rendering \
               Testing Views Web Wrapping; do
        for e in cxx cxx.in txx txx.in hxx hxx.in h h.in c c.in; do
          find "${d}" -name "*.${e}" -exec \
            python Utilities/Maintenance/vtk_reindent_code.py {} +
        done
      done
      f830ff47
  5. 09 Sep, 2016 1 commit
    • Haocheng LIU's avatar
      VTK Bug #16736: Add large data support&test for vtkMPIImageReader · 27eb09b1
      Haocheng LIU authored
      The "ReadSlice" method in 'vtkMPIImageReader' can only read raw data if
      the dataset is within 2^31 elements. Using the same technique in Merge
      Request !1510, we can use a while loop to extend its ability to read the large
      data slice by slice. A test file is also added for vtkMPIImageReader
      class.
      27eb09b1
  6. 08 Mar, 2016 1 commit
  7. 29 Jan, 2016 1 commit
    • Berk Geveci's avatar
      Refactored and update the way algorithms are updated. · f020ebb6
      Berk Geveci authored
      The way algorithms were updated (made to execute) with
      request meta-data (such as update extent) was very error
      prone and counter-intuitive. Added new methods to make
      updating with meta-data easier. I also deprecated a number
      of methods to set request meta-data. This will encourage
      developers to migrate to the new API which is less error-
      prone.
      f020ebb6
  8. 31 Mar, 2015 1 commit
    • Dan Lipsa's avatar
      Redesign "vtkGhostLevels" arrays and related ghost functionalties. · 4dee0274
      Dan Lipsa authored
      Co-authored-by: default avatarYuanxin Liu <leo.liu@kitware.com>
      Co-authored-by: Berk Geveci's avatarBerk Geveci <berk.geveci@kitware.com>
      
       -The semantics of each unsigned char in the ghost arrays changes:
        Instead of storing a numeric value representing how far a cell is
        from the boundary, it is now a bit field specified by
        vtkDataSetAttributes::CellGhostTypes and
        vtkDataSetAttributes::PointGhostTypes.  The bit field is consistent
        with VisIt specs.
      
      - Previously, filters strip all ghost cells they request from upstream
        before finalizing the output. This is no longer done.
      
      - vtkUniform grids previously supported blanking through member arrays
        vtkUniformGrid::CellVisibility and
        vtkUniformGrid::PointVisibility. These arrays are removed and the
        blanking functionality are supported through the new ghost arrays
        instead.
      
      - the "vtkGhostLevel" arrays for cell and point data are renamed to
        vtkDataSetAttributes::GhostArrayName() ("vtkGhostType").
      
      - the version for VTK Legacy files is increased to 4.0 and the version for
        VTK XML files is increased to 2.0. When reading older files we
        convert vtkGhostLevels array to vtkGhostType.
      4dee0274
  9. 21 May, 2014 1 commit
    • Berk Geveci's avatar
      Refactored how pieces and extents are handled. · 1a0b4e9d
      Berk Geveci authored
      Refactoring the way VTK goes between piece and structured
      extents. Before, extent translators were used when the pipeline
      moved from structured to unstructured data converting piece
      request to extent request. This caused many problems with filters
      that altered extents, mainly a lot of redundant IO due to
      repartitioning of different extents. This became extremely
      cumbersome to manage when running distributed. The new behavior
      pushes the extent translation all to way to the readers and
      only when readers are able to read a subset. This works much
      better. The only downside is that filters need to be able to
      handle data extents different than update extents. Most filters
      can do this but many imaging filters cannot. Those that are
      needed in parallel will have to be updated.
      
      As part of this work, I also removed MAXIMUM_NUMBER_OF_PIECES
      and added CAN_HANDLE_PIECE_REQUEST. MAXIMUM_NUMBER_OF_PIECES had
      reduced to being a boolean. 1 for serial sources, -1 for parallel
      sources. I removed it and added a CAN_HANDLE_PIECE_REQUEST instead.
      This key, produced by a source, tells the executive that a source is
      able to handle piece request. It is a source only key produced in
      RequestInformation and is not propagated downstream. If this key is
      not present, the executive will only execute the source for piece 0
      to produce the entire data. It is then up to the user to add a filter
      that splits the data for other piece requests. The only exception to
      this is when CAN_PRODUCE_SUB_EXTENT is present, in which case the
      executive will split using an extent translator AT THE source - not
      downstream.
      
      Conflicts:
      	Filters/FlowPaths/vtkParticleTracerBase.cxx
      
      Change-Id: I8db4040289ff87331adeecded4a738313d9b52df
      1a0b4e9d
  10. 16 Apr, 2014 1 commit
  11. 14 Aug, 2013 1 commit
    • Marcus D. Hanwell's avatar
      Add support for private dependencies in VTK · 57901457
      Marcus D. Hanwell authored
      A simple implementation of private dependencies, with some of the most
      obvious private dependencies moved over. This should be used for all
      dependencies that are not exposed in the public API of the classes in
      the module.
      
      The target_link_libraries call defaults to private due to the way CMake
      implements the link logic. The private dependency logic can help reduce
      link line and include directory length for private links where the
      dependency's API is not exposed in the module. Also added code to ensure
      include directories are not duplicated for modules in the build tree.
      
      Change-Id: If4535338e8d5e9957d7bcce7d3ab0eadec21d2c4
      57901457
  12. 04 Jun, 2013 1 commit
    • Brad King's avatar
      Convert VTKData test inputs to ExternalData content links · 3797f83d
      Brad King authored
      Add to the Testing/Data directory ExternalData content links mirroring
      the content and layout we use from the VTKData/Data directory.
      
      Add a CMake/vtkLegacyData.cmake module, included from CMakeLists.txt and
      Testing/External/CMakeLists.txt, to call ExternalData_Expand_Arguments
      for all data directories added from VTKData/Data.  This will bulk-fetch
      all test input data currently used by tests of any module, enabled or
      not.  We can make the DATA{} references more granular later.
      
      Add a VTK_TEST_DATA_DIR variable to refer to the directory we tell the
      ExternalData module to populate the real data files.  Replace references
      to VTK_DATA_ROOT in test command lines (after -D) with references to
      VTK_TEST_DATA_DIR.  Drop the VTK_DATA_ROOT CMake option and stop using
      the VTKData repository.
      
      Remove the TESTING_DATA option from the vtk_add_test_cxx API and remove
      the VTK_DATA_ROOT option from the vtk_add_test_mpi API since all test
      input data are now handled through ExternalData and Testing/Data content
      links.
      
      Change-Id: Id02490b76ea2e161b9038188264a4830485039d8
      3797f83d
  13. 17 May, 2013 1 commit
  14. 14 May, 2013 1 commit
    • Brad King's avatar
      Use ExternalData to reference test baselines · 42baebf3
      Brad King authored
      Teach vtk_add_test_* to use ExternalData_add_test to add tests and use
      DATA{} syntax to reference test baseline images.  Also update direct
      add_test calls in several modules.
      
      Change-Id: I1ddcec1c109ea9ca7840be9b6ccf015393039cba
      42baebf3
  15. 07 Aug, 2012 1 commit
    • Brad King's avatar
      Do not reference VTK_(SOURCE|BINARY)_DIR from module tests · a6393ad6
      Brad King authored
      The module Testing directories may not refer to VTK_SOURCE_DIR or
      VTK_BINARY_DIR directly since they need to build under the
      Testing/External project outside of VTK.  Since commit 13e19ed9 (Define
      VTK_TEST_OUTPUT_DIR to name Testing/Temporary directory, 2012-04-10) all
      module Testing directories must use VTK_TEST_OUTPUT_DIR to reference
      Testing/Temporary.  Reference the CompareFileMD5.cmake script using a
      relative path within the VTK source tree.
      
      Change-Id: Ia84e16ff246c5b6b0a05ae1e7e0467a0197e241a
      a6393ad6
  16. 31 May, 2012 1 commit
    • Chris Harris's avatar
      Move ParallelIso test to vtkIOMPIImage module · 9516a26c
      Chris Harris authored
      The ParallelIso test requires MPI so should really be part of
      of a module that has this requirment. It tests the MPI image
      reader so fits nicely in the vtkIOMPIImage module.
      
      Change-Id: If09dee8a92507a8fd8b231aaf807fa2f14c48a9d
      9516a26c