Skip to content

GitLab

Switch branch/tag
  1. 14 Jan, 2019 2 commits
  3. 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 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
  7. 28 Sep, 2018 1 commit
  9. 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
  11. 07 May, 2018 2 commits
  13. 11 Apr, 2018 1 commit
  15. 10 Apr, 2018 1 commit
  17. 19 Jan, 2018 2 commits
  19. 12 Jan, 2018 2 commits
  21. 10 Jan, 2018 2 commits
  23. 09 Jan, 2018 2 commits
  25. 04 Jul, 2017 2 commits
  27. 30 Jun, 2017 1 commit
  29. 29 Mar, 2017 1 commit
  31. 27 Mar, 2017 2 commits
  33. 22 Feb, 2017 2 commits
  35. 21 Feb, 2017 3 commits
  37. 20 Feb, 2017 6 commits