The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
Catalyst ordering of initialization code failure
We have a failure if Catalyst initializes itself in different orders. This should NOT matter. From Jeff:
We had, essentially,
processor = vtkCPProcessor::New();
pipeline = vtkCPPythonScriptPipeline::New();
processor->Initialize();
pipeline->Initialize(catalyst_python_file_name.c_str());And I discovered it was dying after "vtkCPPythonScriptPipeline::New();"
I switched the order thus, to match the example:
processor = vtkCPProcessor::New();
processor->Initialize();
pipeline = vtkCPPythonScriptPipeline::New();
pipeline->Initialize(catalyst_python_file_name.c_str());And it started working.
Since it worked in 5.6, I suspect some change in vtkCPProcessor and/or vtkCPPythonScriptPipeline which triggered an error in my ordering that did not previously exist, and none of the tests or examples used my (previously working) ordering.