1. 10 Apr, 2019 1 commit
    • David E. DeMarle's avatar
      make show raster better · 4bd86971
      David E. DeMarle authored
      With NaN's for background and values no longer bound to 0..255
      (i.e. We can rely on floating point textures from OpenGL now),
      let's automatically scale and bias to get something visual.
      4bd86971
  2. 09 Apr, 2019 1 commit
    • David E. DeMarle's avatar
      changes for ParaView 5.7 export now · f2454630
      David E. DeMarle authored
      We add a way to call the export from paraview gui path with each
      new timestep as is done for Catalyst instead of the usual export
      all timesteps now behavior. This lets a higher level script decide
      what to write and when.
      
      We add a way for the store to keep track of and return a list of
      new files written. This lets us unroll cinema A-C databases into
      a cinema D table.
      f2454630
  3. 14 Jan, 2019 2 commits
  4. 03 Oct, 2018 4 commits
  5. 02 Oct, 2018 2 commits
    • David E. DeMarle's avatar
      Merge topic 'use_exact_times' · 5826ba64
      David E. DeMarle authored
      472f6c21 Use full precision instead of format strings for times
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Merge-request: !121
      5826ba64
    • David E. DeMarle's avatar
      Use full precision instead of format strings for times · 472f6c21
      David E. DeMarle authored
      With corresponding change in the ParaView level caller, this eliminates
      this Catalyst warning:
      vtkPVTrivialProducer (0x51724d0): Requesting time 9.6 but only 9.6 is available
      
      and the values in the parameter are now as exact as they can be
      in text form. Note also that the filenames are changed in spec A
      output. As I recall the formatting was done for the original javascript
      viewer client which couldn't handle precise numbers or perhaps filenames.
      No one is actively using or developing that project anymore so this
      change is fine.
      472f6c21
  6. 28 Sep, 2018 1 commit
  7. 23 May, 2018 2 commits
    • Nicolas Vuaille's avatar
      Write camera metadata for each timestep · d5e8848f
      Nicolas Vuaille authored
        * cinemareader.py expects one camera metadata per timestep (cf line 353)
        * exporting with catalyst does not provide it as the animation scene
         has no timestepValues. So manually duplicate camera metadata.
      d5e8848f
    • Nicolas Vuaille's avatar
      Fix timesteps values reading · 1dc8dd91
      Nicolas Vuaille authored
        * When exporting from PV, Time values are stored as string in
        scientific format. When reading back, values are sorted as char and not as
        numerical values, so it breaks the mapping with timestep.
      1dc8dd91
  8. 07 May, 2018 2 commits
  9. 11 Apr, 2018 1 commit
  10. 10 Apr, 2018 1 commit
  11. 19 Jan, 2018 2 commits
  12. 12 Jan, 2018 2 commits
  13. 10 Jan, 2018 2 commits
  14. 09 Jan, 2018 2 commits
  15. 04 Jul, 2017 2 commits
  16. 30 Jun, 2017 1 commit
  17. 29 Mar, 2017 1 commit
  18. 27 Mar, 2017 2 commits
  19. 22 Feb, 2017 2 commits
  20. 21 Feb, 2017 3 commits
  21. 20 Feb, 2017 4 commits