1. 03 Mar, 2020 2 commits
  2. 31 Jul, 2019 3 commits
  3. 25 Jul, 2019 2 commits
  4. 19 Jun, 2019 2 commits
  5. 18 Jun, 2019 3 commits
  6. 17 May, 2019 3 commits
  7. 17 Apr, 2019 1 commit
  8. 16 Apr, 2019 1 commit
    • David E. DeMarle's avatar
      changes for paraview export now feature · 951de993
      David E. DeMarle authored
      add a way to skip the automatic time stepping that the old
      paraview gui interface used so that we can call it like catalyst
      does, one step at a time.
      
      make cinema keep track of all of the files and keys written so that
      paraview's export to D table can unroll the A-C information into
      a flat table
      951de993
  9. 21 Feb, 2019 4 commits
  10. 14 Jan, 2019 2 commits
  11. 03 Oct, 2018 4 commits
  12. 02 Oct, 2018 2 commits
    • David E. DeMarle's avatar
      Merge topic 'use_exact_times' · 5826ba64
      David E. DeMarle authored and Kitware Robot's avatar Kitware Robot committed
      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
  13. 28 Sep, 2018 1 commit
  14. 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
  15. 07 May, 2018 2 commits
  16. 11 Apr, 2018 1 commit
  17. 10 Apr, 2018 1 commit
  18. 19 Jan, 2018 2 commits
  19. 12 Jan, 2018 2 commits