Yes indeed, we removed this behavior in the MR.
Multiple solution are still being discussed internally:
- one of them would be to have the possibility to create a local instance (of
vtkSMPToolsor of avtkSMPToolsLocalParametersclass) that would drive the number of thread locally. - or we could also consider that Initialize should be called only once at the beginning of the pipeline.
The vtkSMPTools::IsInitialized would be especially useful for this second proposition.