Skip to content

Settling configurations in mobility #10

@robertladwig

Description

@robertladwig

Currently running GLM 3.0.0 with AED2 1.3.0 and tested this on a Mac and a Windows machine. It seems that the settling configuration in the aed2_mobility subroutines is not functioning as intended. Changing the settling configuration won't affect the model outcome, as it seems that GLM is always using the DEFAULT CASE with vvel = data%w_pom and vvel_cpom = data%w_cpom (instead of for instance Stoke's Law).

My guess is that the keywords from aed2.h aren't read in properly, as AED2 doesn't recognize the settling/migration keyword.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions