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
I noticed something funny when extracting cross sections diagonally through MuRAT outputs using the cross sections function. I essentially have 3 data arrays with the same grid, two arrays are physical properties and one is categorial. If I extract cross sections from an uneven latitude (eg. -2.81), the function changes the values inside the categorial array from integers (-5,-4,-3-,-2,-1) to floating numbers and then paraview cannot read it as categorial. This does not happen when cutting from an even latitude point (e.g. -2.82). It does also not happen when extracting cross sections in depth.
Possible fix: give wanted output (floating numbers, integers) as input in the function?
The text was updated successfully, but these errors were encountered:
I noticed something funny when extracting cross sections diagonally through MuRAT outputs using the cross sections function. I essentially have 3 data arrays with the same grid, two arrays are physical properties and one is categorial. If I extract cross sections from an uneven latitude (eg. -2.81), the function changes the values inside the categorial array from integers (-5,-4,-3-,-2,-1) to floating numbers and then paraview cannot read it as categorial. This does not happen when cutting from an even latitude point (e.g. -2.82). It does also not happen when extracting cross sections in depth.
Possible fix: give wanted output (floating numbers, integers) as input in the function?
The text was updated successfully, but these errors were encountered: