1. 20 Jul, 2015 1 commit
  2. 19 Jul, 2015 4 commits
  3. 18 Jul, 2015 8 commits
  4. 17 Jul, 2015 1 commit
  5. 13 Jul, 2015 3 commits
    • Ben Boeckel's avatar
      Testing: fix unused variable warnings · 46f1b60a
      Ben Boeckel authored
    • Utkarsh Ayachit's avatar
      BUG #14897: Fix periodic boundary issues with vtkNetCDFCAMReader. · 23dff2bd
      Utkarsh Ayachit authored
      vtkNetCDFCAMReader did not deal with periodicity of the domain
      correctly. There were cases (as demonstrated by the report BUG) where
      the cells we incorrectly split. Fixed the code to be more robust to the
      potential ways in which the points in the cells are defined. Also
      includes some performance tweaks e.g. using vector instead of map.
      This deprecates the SetCellLayerRight/GetCellLayerRight API on the
      reader. This API is no longer needed since the reader makes an informed
      decision when deciding which side to place the cells that overlap the
      periodic boundary.
    • Dan Lipsa's avatar
      ENH: CanReadFile does not fail for newer file version. · 4e531cd0
      Dan Lipsa authored
      CanReadFile does not fail for newer file versions to enable clients (ParaView)
      to distinguish between reader failures caused by a mismatch between the file
      and the reader, and reader failures that cannot be fixed by changing the reader.
      A warning will be printed when reading a file with a newer version than the reader.
      Legacy readers already behave this way.
  6. 10 Jul, 2015 3 commits
  7. 09 Jul, 2015 1 commit
  8. 08 Jul, 2015 2 commits
  9. 07 Jul, 2015 2 commits
  10. 06 Jul, 2015 1 commit
    • Dan Lipsa's avatar
      BUG: Get rid of error printouts from TestRIBExporter · 96baf8e8
      Dan Lipsa authored
      This fixes:
      ERROR: In /Common/ExecutionModel/vtkImageAlgorithm.cxx, line 137
      vtkOpenGLTexture (0x7fa67b434bc0): Definition of Execute() method should be in subclass and you should really use the ExecuteData(vtkInformation *request,...) signature instead
      ERROR: In /home/danlipsa/src/VTK/IO/Image/vtkTIFFWriter.cxx, line 137
      vtkTIFFWriter (0x2028280): Unsupported data type: double
      ERROR: In /home/danlipsa/src/VTK/IO/Image/vtkTIFFWriter.cxx, line 248
      vtkTIFFWriter (0x2028280): Could not get data from input.
      ERROR: In /home/danlipsa/src/VTK/IO/Image/vtkTIFFWriter.cxx, line 410
      vtkTIFFWriter (0x2028280): Problem writting trailer.
  11. 01 Jul, 2015 1 commit
  12. 30 Jun, 2015 1 commit
  13. 29 Jun, 2015 3 commits
  14. 26 Jun, 2015 1 commit
  15. 24 Jun, 2015 3 commits
    • David Gobbi's avatar
      Fix blank slices that appear in some TIFF volumes. · 32f5e6d9
      David Gobbi authored
      The logic for skipping subfiles that aren't part of the primary image
      (e.g. subfiles that contain reduced-resolution slices) was incorrect.
      When the reader encountered such subfiles, it would simply move on to
      the next slice of the image, without setting the voxel values for the
      current slice.  Now, the "slice" counter and the "page" counter are
      distinct from one another, since not all pages become image slices.
    • David Gobbi's avatar
      Close the DICOM file immediately after reading it. · 3c9d9626
      David Gobbi authored
      The vtkDICOMImageReader would keep the last file open until the reader
      itself was destructed.  On Windows, this often means that the file cannot
      be deleted or moved until the application closes.
    • Marcus D. Hanwell's avatar
      Fix bug with bad TIFF tag on char/short format · ce110d71
      Marcus D. Hanwell authored
      The writer only supports the writing of unsigned (the default),
      change the volume to match the behavior of the single image. This
      could be improved further in follow up commits if support for signed
      types is needed.
  16. 23 Jun, 2015 3 commits
    • Utkarsh Ayachit's avatar
      Expose mode-shape-range meta-data to downstream filters. · ea532fa5
      Utkarsh Ayachit authored
      Filters downstream from vtkExodusIIReader has access to mode_shape in
      FieldData, but there was no way of getting information for the range of
      the mode shapes. This changes added support for a new "mode_shape_range"
      array that provides this meta-data.
      Also adding "mode_shape" and "mode_shape_range" arrays only when
      HasModeShapes is true. Otherwise, these variables are meaningless.
    • Utkarsh Ayachit's avatar
      Cleanup initialization of TimeStepRange/ModeShapeRange. · 636fc932
      Utkarsh Ayachit authored
      vtkExodusIIReader now initializes TimeStepRange and ModeShapeRange in
      just 1 place consistently i.e. in a method called in
      Also making the reader not change the values of TimeStepRange and
      ModeShapeRange based on whether the HasModeShapes is true/false. This
      makes it hard for applications to consistently access this information
      since it would change based on the value of HasModeShapes.
    • Utkarsh Ayachit's avatar
      Remove vtkExodusIIReader::UpdateTimeInformation(). · e66cef8c
      Utkarsh Ayachit authored
      This method is never called by anything. Hence, removing it to avoid
  17. 18 Jun, 2015 1 commit
    • David Gobbi's avatar
      Allow NIFTI reader and writer to handle planar RGB files. · 90dfa378
      David Gobbi authored
      The NIFTI format uses packed RGB, but the older Analyze format, in its
      earliest incarnations, used planar RGB.  For the sake of compatibility
      with these old Analyze files, or with NIFTI files that were created from
      them without a planar-to-packed conversion, a PlanarRGB option has been
      added to the vtkNIFTIImageReader and the vtkNIFTIImageWriter.
  18. 12 Jun, 2015 1 commit
    • Utkarsh Ayachit's avatar
      BUG #15321: Fix mode_shape array. · 27984c3d
      Utkarsh Ayachit authored
      'mode_shape' array placed in the output of vtkExodusIIReader was
      directly using the timestep index. It should be offset by 1 (since
      it starts with 1, not 0). Fixed that.