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.

Sign up for GitHub

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

Jump to bottom

longitude/latitude #252

Open
penguian opened this issue Aug 18, 2020 · 1 comment
Open

longitude/latitude #252

penguian opened this issue Aug 18, 2020 · 1 comment
Assignees
@JhanSrbinovsky
Labels
component: JAC readiness major new
Milestone
6. Report

Comments

@penguian
Copy link
Collaborator

keyword_latitude_keepgit owner:[email protected] type_JAC readiness | by [email protected]

Treatment of latitude/longitude needs to be properly addressed in particular for JAC standalone, global runs, especially where sin(latitude_C) is used to define Antarctica etc. Online, sin(latitude_C) can be passed from the model a it is a defined quantity [In the signed format appropriate to how it is used e.g in definition of the Antarctic circle]. This also has to be reconciled/consistent with the CABLE offline treatment.

Issue migrated from trac:252 at 2023-11-27 11:32:55 +1100
@penguian
Copy link
Collaborator Author

penguian commented Feb 7, 2023

@[email protected] changed keywords from latitude to latitude keepgit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JhanSrbinovsky JhanSrbinovsky

Labels
component: JAC readiness major new
Projects
None yet
Milestone
6. Report
Development

No branches or pull requests
2 participants
@penguian @JhanSrbinovsky