Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug mistmatch in fort.13 header order and user-defined values #240

Open
krober10nd opened this issue Jul 11, 2021 · 0 comments
Open

bug mistmatch in fort.13 header order and user-defined values #240

krober10nd opened this issue Jul 11, 2021 · 0 comments
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@krober10nd
Copy link
Collaborator

  • If your fort.13 header attributes are in a different order than the user-defined attribute data below the header, transferring the nodal attributes will not work with msh.map_mesh_properties
  • For now, please check the order of m.f13.defval.Atr.AttrName and m.f13.userval.Atr.AttrName is the same and edit the header of the fort.13 to match whatever the order is m.f13.userval.Atr.AttrName
  • A future solution would be to not use ASCII text for the fort.13 but this depends on the adcirc development group.
@krober10nd krober10nd added wontfix This will not be worked on bug Something isn't working labels Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant