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

Computing nodal correction - possible bug ? #142

Open
simonweppe opened this issue Dec 3, 2024 · 0 comments
Open

Computing nodal correction - possible bug ? #142

simonweppe opened this issue Dec 3, 2024 · 0 comments

Comments

@simonweppe
Copy link

Hi team,

Just came across a potential bug when trying to compute nodal correction.

In tides.py there are some MAJOR and MINOR cons declared at the beginning and combined into ALL_CONSTITUENTS

This is later checked in get_nodal_correction (https://github.com/schism-dev/pyschism/blob/main/pyschism/forcing/bctides/tides.py#L275). If a cons is not in ALL_CONSTITUENTS (e.g. "L2"), this returns self._nodal_factors[constituent], which seems is not initialized. So it fails, although the correction information is indeed available further below https://github.com/schism-dev/pyschism/blob/main/pyschism/forcing/bctides/tides.py#L351

The function 'add_constituents' that should initialize self._nodal_factors is never called it seems.

Keen to hear your thoughts.
Best
Simon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant