Skip to content

Improve cdo_sellonlat for extpar_aot_to_buffer.py#445

Merged
stelliom merged 3 commits intomasterfrom
improve-cdosel
Mar 10, 2026
Merged

Improve cdo_sellonlat for extpar_aot_to_buffer.py#445
stelliom merged 3 commits intomasterfrom
improve-cdosel

Conversation

@stelliom
Copy link
Contributor

@stelliom stelliom commented Mar 10, 2026

Description

This PR modifies the function cdo_sellonlat so that it supports coarse raw dataset. With these changes we can ensure that the selected lonlat-box always contains the full target domain when remapping the data with CDO.

Workflow for merging PRs

Please read these instructions carefully and follow the steps below before requesting a review by the maintainers. This way we can ensure a smoother review process and your changes will be merged sooner.

Additionally, if this is the first PR you open in EXTPAR make sure to read the "Information for EXTPAR Developers" section in the documentation.

Checklist

  • Provide a detailed description of your changes in the "Description" section above.
  • If you implemented a new feature:
    • Document it in the correct Markdown file(s) under the docs/ directory.
    • Add a new test or make sure your changes are already tested.
  • Your code follows the style guidelines.
  • Your changes only touch the files/lines relevant for you.
  • All four required checks pass (see "Testing and debugging" for more details).
  • No conflicts with the base branch.

If all the points above are satisfied you can ask for a review by selecting stelliom as a reviewer.

For any questions please ping @stelliom on this PR.

Testing and debugging

The most important test for PRs is the one labeled "EXTPAR Testsuite on Jenkins". This checks that the results of all testcases (described by the namelists in test/testsuite/data) did not change compared to the references.

You can launch the testsuite by writing launch jenkins as a comment in the PR that you want to test. Once completed, the result of the testsuite will be shown on the PR (failure or success).

If you need more details on the testsuite results (e.g., if you are trying to debug an error or you are simply unsure why the tests fail) you can launch the testsuite with launch jenkins(debug). This will run the tests as usual, but, once completed, you will be given a URL (via a comment on the PR) to access the logfiles and namelists of all tests that were run.

@stelliom
Copy link
Contributor Author

launch jenkins

@stelliom stelliom enabled auto-merge (squash) March 10, 2026 13:26
@stelliom
Copy link
Contributor Author

launch jenkins

@stelliom stelliom merged commit 917d0d9 into master Mar 10, 2026
5 checks passed
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 this pull request may close these issues.

1 participant