Skip to content

GitLab

A GitLab update will be applied today, 9/24. The site may be slow between 12pm - 12:45pm Fri 9/24 EDT (UTC -400).

Closed
Created by David@dhrDeveloper

Cinema: Results from exporting artifacts from interactive ParaView and Catalyst are not identical

Cinema: Results from exporting artifacts from interactive ParaView and Catalyst should be identical.

When a user defines a set of Exports from ParaView, the results of exporting should be identical in both the interactive ParaView and batch Catalyst runs (assuming both are run in serial or parallel).

Currently, the Catalyst export adds a 'cinema' subdirectory to image paths, so that the resulting sets of extracts are not identical.

To reproduce the issue:

  1. Create some pipeline in ParaView
  2. Set up an export for a cinema database, making sure that the Spec D table will be exported
  3. Catalyst->Export Now (this is the InteractiveExport dataset)
  4. Catalyst->Export Catalyst Script to save a catalyst script
  5. Run the catalyst script, using the filedriver.py script to duplicate the input in Step 1 above. (this is the CatalystExport dataset)
  6. InteractiveExport and CatalystExport results will be different. In particular, CatalystExport adds an extra subdirectory (cinema) to the file path for exports.

The results of these two operations should instead be identical sets of results.

More detail is available here, where we have created testing scripts to automate the steps above, including saving out a Catalyst script from the UI operations that created the export definitions: https://github.com/cinemascience/cinema_testing/blob/master/pv/5.7.0/readme.md

Edited by David
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information