Python: Example of JIT-compiled Fortran execute from Python #112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c21105a to
c450a31
Compare
This is to circumvent a bug in numpy's f2py following the upgrade to meson.
This allows the Fortran JIT to use native numpy Fortran array layout and let's JIT-based types be instantiated and passed to data loads.
This re-uses the data load utilities and only executed over a single block, but hey, it's something. ;)
c450a31 to
d522f94
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides a first example of how the Just-in-Time (JIT) compilation infrastructure from
loki.buildcan be used to on-the-fly compile the CLOUDSC kernel and invoke it form Python with Numpy arrays.This change requires two main steps:
cloudscf2pysub-package to account for the transposed Fortran array layout.The latter step is by no means clean, but highlights the challenges for JIT-compiling self-contained IFS-style kernels/parametrisations.
Please note that the linkage to the common sub-library also requires a dynamic library build!
A few other small updates and clean-ups:
transposefunctionality for input reads and validation steps