-
Notifications
You must be signed in to change notification settings - Fork 24
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
Feature #3012 ugrid for 3D points (PointXYZ) #3035
Conversation
…s_XYZ_km. Added llh_to_ecef APIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hsoh-u while the SonarQube scan did not fail, I did check the results on server and found.
- the develop branch has 18,253 code smells overall
- this PR 3035 scan increases them to 18,275
- And flags 24 smells in the New Code
I looked through those 24 and see that several are easily fixed. Please take a look and resolve whichever can be easily done (especially using empty()
, removing unused vars, removing commented out code, and so on).
Generally, I'd like with each PR to:
- Reduce the Overall number of code smells.
- Review the New Code code smells and fix the ones that are easily fixed.
In my opinion, the ones about complexity and the number of nested loops are very difficult to fix. So it's OK to add news ones of those... as long as you reduce easy ones elsewhere to make sure the total number of smells is reduced.
… test executables in the test_util/libcode/vx_grid directory.
…mells in New Code and hopefully reduce the Overall number of code smells.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve of these changes.
Note the following:
- I updated the
.gitignore
settings with these changes. - I made changes to the
vx_grid
library to reduce the SonarQube code smells with these changes. - I reviewed the code changes and don't see any obvious problems.
- I tested the code in seneca
/d1/projects/MET/MET_pull_requests/met-12.1.0/beta1/MET-feature_3012_ugrid_3D
by rerunning the tests listed in the PR and confirmed that they run without error.
I note that there are no testing or documentation updates but that's fine because this is just adding internal test code. We'll update the tests and docs when the functionality is ready to be used in one of the MET applications.
The total number of SonarQube code smells are reduced from 18,253 in the develop branch down to 18,222 for this feature branch.
Expected Differences
Added two test utilities for 3D KDTree. The lat/lon in degree is converted to km as ECEF (Earth Centered Earth Fixed). KDTree was tested with PointXYZ
If yes, please describe:
Added two test utilities at
internal/test_util/libcode/vx_grid
search_3d_kdtree
: standalone KDTree for 3 dimensional point data (lat/lon/hgh)search_3d_kdtree_api
: The KDTree for 3 dimensional point data (lat/lon/hgh) is implemented atsrc/libcode/vx_grid
search_3d_kdtree
llh_to_ecef
(lat/lon/height or altitude to Earth Centered Earth Fixed in km)Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
If yes, please describe:
Pull Request Testing
The build is ready at seneca (/d1/personal/hsoh/git/pull_request/MET_feature_3012_ugrid_3D/internal/test_util/libcode/vx_grid):
The same arguments for search_3d_kdtree and search_3d_kdtree_api :
Unit test for
llh_to_ecef
:Test with other input if available
Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]
Do these changes include sufficient testing updates? [No]
Will this PR result in changes to the MET test suite? [No]
If yes, describe the new output and/or changes to the existing output:
Will this PR result in changes to existing METplus Use Cases? [No]
If yes, create a new Update Truth METplus issue to describe them.
Do these changes introduce new SonarQube findings? [No]
If yes, please describe:
Please complete this pull request review by [Fill in date].
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: Coordinated METplus-X.Y Support project for bugfix releases or MET-X.Y.Z Development project for official releases