GitLab

Replace invalid use of 'is' keyword

See merge request !7

'is' checks identity, not equality. In Python 3.8, this usage results
in a warning.

Real filenames for cinema d

See merge request !6

the cinema D table generated was wrong because it contained
the implicit vector magnitude arrays and didn't take into account
that the file extension can vary based on the spec level and
the backends etc.

I took out the file existence check and it didn't seem necessary,
but it might introduce a new bug where the D tables have duplicates
or something like that.

This reverts commit a76093cc.
The approach didn't work, we would also have to pass the array
choice into the execute call for it to happen.

use paraviews currently shown array as the default to export

See merge request !5

fix a typo in the python3 code path

See merge request !4

Python3 compatibility

See merge request !3

The bulk change is that list like things are now iterator like
things, thus the list, zip, and iter* changes.

json is apparently more strict about text/binary as well.

tested the cinema tests in paraview on my linux system with
python 2 and python 3 and both tests now pass with a little
help having to do with iterated list orders being different
in python3 than python2.

Merge branch 'for/paraview' of https://gitlab.kitware.com/third-party/cinema_python into for/paraview

remove dependency on a paraview object that no longer exists

See merge request !2

Merge branch 'for/paraview' of https://gitlab.kitware.com/third-party/cinema_python into for/paraview

ParaView's export scene to cinema feature has been replaced and the class that this used to use for progress
handling is gone. This change prevents the resulting runtime failure that prevents cinema image outputs from
working. The only place progress was emitted way by the export scene to cinema feature.

We may bring it back if we want progress events from the new export now feature.

changes for paraview export now feature

See merge request !1

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

makes it possible to nest `cinema_python` within other packages e.g.
`paraview.tpl`

fix export of non time varying data

See merge request cinema/cinema_python!124

David E. DeMarle authored Oct 03, 2018 and Kitware Robot committed Oct 03, 2018

b99e9583

 correct the phi theta center of rotation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !123

original calculation was wrong

David E. DeMarle authored Oct 03, 2018 and Kitware Robot committed Oct 03, 2018

b86414fa

 Revert "Use full precision instead of format strings for times"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !122

This reverts commit 472f6c21.

The export scene path needs to be changed to use full precision
and the ParaView importer needs to be changed to read databases
with string or full precision times.

David E. DeMarle authored Oct 02, 2018 and Kitware Robot committed Oct 02, 2018

472f6c21

 Use full precision instead of format strings for times
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !121

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.

David E. DeMarle authored Sep 28, 2018 and Kitware Robot committed Sep 28, 2018

d5e8848f Write camera metadata for each timestep
1dc8dd91

 Fix timesteps values reading
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !119

  * 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.

  * 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.

David E. DeMarle authored May 07, 2018 and Kitware Robot committed May 07, 2018

0f0191ee

 use the new asynch writer in VTK to speed up writes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !118

We see close to 2x speed up in ParaView with this. Before writing
superquadric took about 26 seconds, now it takes about 13.

David E. DeMarle authored Apr 11, 2018 and Kitware Robot committed Apr 11, 2018

4748922f

 Improve A export when focal point is not center of rotation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !117

Part of ParaView bug #18042

ok actually fix the bug this time

See merge request cinema/cinema_python!116

David E. DeMarle authored Jan 12, 2018 and Kitware Robot committed Jan 12, 2018

4d8ce998

 avoid wildcard chars in filenames
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !115

A windows paraview user ran into trouble exporting a file series.
For those the pipeline browser appends an asterisk to the base
filename. File writes then fail. The simplest solution is to strip
the wildcards.