You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me register here the tasks which are pending from PR #90 so that we do not lose track of them:
Extend current pvtk_grid API such that it is ALSO able to handle PImageData, PRectilinearGrid, and PStructuredGrid parallel formats as well. These formats have extra global and piece-wise attributes whose values have to be provided (to pvtk_grid I would say) apart from the attributes of the local portions. For example, WholeExtent (global) and Extent (piece-wise), respectively.
Develop the remaining code to support parallel file formats different from PUnstructuredGrid. This is a minor dev. E.g., the fact that PRectilinearGrid uses the <PCoordinates> XML element, instead of the <PPoints> one.
Test all parallel file formats different from PUnstructuredGrid.
cc @jipolanco @fredrikekre @fverdugo
Some context on this issue:
pvtk_gridto generate parallel file formats (e.g. .pvtu) files. #90Let me register here the tasks which are pending from PR #90 so that we do not lose track of them:
pvtk_gridAPI such that it is ALSO able to handlePImageData,PRectilinearGrid, andPStructuredGridparallel formats as well. These formats have extra global and piece-wise attributes whose values have to be provided (topvtk_gridI would say) apart from the attributes of the local portions. For example,WholeExtent(global) andExtent(piece-wise), respectively.PUnstructuredGrid. This is a minor dev. E.g., the fact thatPRectilinearGriduses the<PCoordinates>XML element, instead of the<PPoints>one.PUnstructuredGrid.