-
Notifications
You must be signed in to change notification settings - Fork 0
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
[py2f]: Add dycore wrapper and datatest #508
base: main
Are you sure you want to change the base?
Conversation
Fixes for running dycore on gpu --------- Co-authored-by: Jonas Jucker <[email protected]> Co-authored-by: Nicoletta Farabullini <[email protected]>
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
launch jenkins spack |
model/atmosphere/dycore/src/icon4py/model/atmosphere/dycore/nh_solve/solve_nonhydro.py
Outdated
Show resolved
Hide resolved
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
launch jenkins spack |
launch jenkins spack |
cscs-ci run default |
cscs-ci run default |
launch jenkins spack |
Granule dycore which runs on CPU and GPU in ICON (not verifying yet), and passes datatests in icon4py.
cscs-ci run default |
Resolved conflicts and also disabled Fortran integration tests, since we need to pass connectivities now inorder for the granule to run correctly.
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
2 similar comments
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
cscs-ci run default |
Mandatory Tests Please make sure you run these tests via comment before you merge!
Optional Tests To run benchmarks you can use:
To run tests and benchmarks with the DaCe backend you can use:
In case your change might affect downstream icon-exclaim, please consider running
For more detailed information please look at CI in the EXCLAIM universe. |
Description
Adds dycore wrapper and datatest for single and multitimestep runs. The Fortran integration test is skipped for now as we need to pass the correct connectivities from Fortran in order to initialise the ICON grid on the Python side. In the future this may be achieved using serialised connectivities and using Serialbox to read them in on the Fortran side.