Skip to content

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

New issue
New issue
Open
Open
bug mistmatch in fort.13 header order and user-defined values#240
Labels
bugSomething isn't workingwontfixThis will not be worked on
@krober10nd

Description

@krober10nd
krober10nd
opened on Jul 11, 2021
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingwontfixThis will not be worked on

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions