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

Include latest lat/lon based definition for forecast outputs #45

Open
bnubald opened this issue Jul 9, 2024 · 3 comments · Fixed by #46
Open

Include latest lat/lon based definition for forecast outputs #45

bnubald opened this issue Jul 9, 2024 · 3 comments · Fixed by #46
Assignees

Comments

@bnubald
Copy link
Contributor

bnubald commented Jul 9, 2024

Update produce_op_forecasts.sh to allow new lat/lon based region and north-facing plot arguments via this script as introduced in this PR icenet-ai/icenet#282.

https://github.com/icenet-ai/icenet/blob/9a70ce688e1196aaebf60df5829e5fbb722f32c5/icenet/plotting/forecast.py#L1393-L1401

@bnubald bnubald self-assigned this Jul 9, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Jul 9, 2024
bnubald added a commit that referenced this issue Jul 9, 2024
Fixes #45: Add lat/lon region forecast out script, add help
@bnubald bnubald linked a pull request Jul 9, 2024 that will close this issue
@bnubald bnubald closed this as completed Jul 9, 2024
@bnubald bnubald reopened this Jul 9, 2024
@bnubald
Copy link
Contributor Author

bnubald commented Jul 9, 2024

While icenet-ai/icenet#283 is not fixed, the script should avoid attempting to output metric plots when lat/lon region bounds are specified, which are not currently implemented for metric computation.

Hence, as it stands, these metric plot outputs are based on either pan-Arctic or pan-Antarctic rather than user defined lat/lon region.

Add logic to skip these outputs for now.

bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Jul 9, 2024
bnubald added a commit that referenced this issue Jul 9, 2024
@bnubald
Copy link
Contributor Author

bnubald commented Jul 9, 2024

Resolved by above PR.

@bnubald bnubald closed this as completed Jul 9, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
…dates

Also add flag to not clip source data when defining a lat/lon region
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
bnubald added a commit to bnubald/icenet-pipeline that referenced this issue Aug 1, 2024
@bnubald bnubald reopened this Aug 1, 2024
@bnubald
Copy link
Contributor Author

bnubald commented Aug 1, 2024

Wanting to opt for user-specified Coordinate Reference System (CRS) instead of hard coding the CRS to use, want to allow specifying it when running the produce_op_forecasts.sh script.

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

Successfully merging a pull request may close this issue.

1 participant