Pass lat-lon points to BallTree instead of lon-lat #439
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.
Description
The haversine distance metric for sklearn's BallTree requires the points to be passed in lat-lon format (see docs). We were passing those in lon-lat format, causing large errors (smoothing/"dripping" artifacts) around 90E and 90W longitude lines.
Passing the points in lat-lon format seems to solve the issue.
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
docs/directory.If all the points above are satisfied you can ask for a review by selecting
stelliomas a reviewer.For any questions please ping
@stelliomon 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 jenkinsas 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.