Is your feature request related to a problem? Please describe.
For now, when converting a dataset to PLAID format, nothing prevents the user from using CGNS paths conflicting with PLAID conventions. For instance, we can have a field with the path 'Base_2_2/Zone/PointData/U_x' instead of 'Base_2_2/Zone/VertexFields/U_x' (or CellCenterFields, or FaceCenterFields, ...).
Describe the solution you'd like
In plaidcheck.py, check that the CGNS paths comply with conventions used in PLAID.
Is your feature request related to a problem? Please describe.
For now, when converting a dataset to PLAID format, nothing prevents the user from using CGNS paths conflicting with PLAID conventions. For instance, we can have a field with the path 'Base_2_2/Zone/PointData/U_x' instead of 'Base_2_2/Zone/VertexFields/U_x' (or CellCenterFields, or FaceCenterFields, ...).
Describe the solution you'd like
In plaidcheck.py, check that the CGNS paths comply with conventions used in PLAID.