-
Notifications
You must be signed in to change notification settings - Fork 12
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
Python implementation #100
base: main
Are you sure you want to change the base?
Conversation
Reviewer's Guide by SourceryThis pull request implements a pure Python version of the solid Earth tides calculation functionality, previously implemented in Fortran. The implementation includes core calculation functions and wrappers to maintain API compatibility with the existing codebase. The changes are organized into a new Class diagram for the new py_solid moduleclassDiagram
class py_solid {
+calc_solid_earth_tides_grid(datetime, dict, float, bool, bool) np.ndarray
+plot_solid_earth_tides_grid(np.ndarray, np.ndarray, np.ndarray, datetime, str, bool, bool)
+calc_solid_earth_tides_point(float, float, datetime, datetime, int, bool, bool) tuple
+plot_solid_earth_tides_point(np.ndarray, np.ndarray, np.ndarray, np.ndarray, list, str, bool, bool)
+plot_power_spectral_density4tides(np.ndarray, float, str, int, int)
}
class solid {
+solid_point(LLH, date, int) tuple
+solid_grid(datetime, npt.ArrayLike, npt.ArrayLike) npt.ArrayLike
}
class LLH {
+float lat
+float lon
+float hte
+geoxyz() XYZ
}
class XYZ {
+float x
+float y
+float z
+enorm8() float
+rot3(float) XYZ
+rot1(float) XYZ
+rge(LLH) XYZ
+lhsaaz() XYZ
}
py_solid --> solid
solid --> LLH
solid --> XYZ
LLH --> XYZ
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
PR summaryThis Pull Request introduces a Python-only implementation of the SuggestionTo further improve this PR, consider adding documentation or comments within the code to explain the purpose and functionality of key functions and classes, especially in the newly added Python modules. This will enhance code readability and maintainability for future developers. Additionally, ensure that the new implementation is thoroughly tested across different environments to confirm its reliability as a drop-in replacement. Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect. Current plan usage: 0.00% Have feedback or need help? |
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.
Hey @piyushrpt - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding a note in the documentation about which implementation (Fortran vs Python) is recommended for different use cases, e.g. performance vs portability.
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟡 Testing: 2 issues found
- 🟡 Complexity: 1 issue found
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
# reference | ||
# calculated based on version 0.3.2.post6 on Jun 24, 2024 | ||
# env: macOS with python-3.10, numpy-1.24 | ||
# install: manual compilation via f2py | ||
tide_e_80_100 = np.array( | ||
[[0.01628786, 0.01630887, 0.01633078, 0.01635247, 0.01637394], | ||
[0.01633248, 0.01635348, 0.01637538, 0.01639706, 0.01641851], | ||
[0.01638009, 0.01640107, 0.01642296, 0.01644462, 0.01646606], | ||
[0.01642767, 0.01644864, 0.01647052, 0.01649217, 0.01651359], | ||
[0.01647523, 0.01649619, 0.01651805, 0.01653968, 0.01656109]], |
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.
suggestion (testing): Consider parameterizing test reference data
The reference data arrays could be moved to a separate test data file or fixture to improve maintainability and readability. This would also make it easier to update reference values in the future.
# tests/test_data/grid_reference.py
import numpy as np
TIDE_E_80_100 = np.array([
[0.01628786, 0.01630887, 0.01633078, 0.01635247, 0.01637394],
[0.01633248, 0.01635348, 0.01637538, 0.01639706, 0.01641851],
[0.01638009, 0.01640107, 0.01642296, 0.01644462, 0.01646606],
[0.01642767, 0.01644864, 0.01647052, 0.01649217, 0.01651359],
[0.01647523, 0.01649619, 0.01651805, 0.01653968, 0.01656109]
])
# compare | ||
assert np.allclose(tide_e[::80, ::100], tide_e_80_100) | ||
assert np.allclose(tide_n[::80, ::100], tide_n_80_100) | ||
assert np.allclose(tide_u[::80, ::100], tide_u_80_100) |
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.
suggestion (testing): Add tolerance values to np.allclose assertions
Consider explicitly specifying rtol and atol values in np.allclose() to make the test's precision requirements clear. This helps catch subtle numerical differences that may be important for this scientific calculation.
# compare | |
assert np.allclose(tide_e[::80, ::100], tide_e_80_100) | |
assert np.allclose(tide_n[::80, ::100], tide_n_80_100) | |
assert np.allclose(tide_u[::80, ::100], tide_u_80_100) | |
# compare | |
assert np.allclose(tide_e[::80, ::100], tide_e_80_100, rtol=1e-10, atol=1e-12) | |
assert np.allclose(tide_n[::80, ::100], tide_n_80_100, rtol=1e-10, atol=1e-12) | |
assert np.allclose(tide_u[::80, ::100], tide_u_80_100, rtol=1e-10, atol=1e-12) |
return xcorsta | ||
|
||
|
||
def detide(xsta: XYZ, |
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.
issue (complexity): Consider refactoring the tidal computation code to extract shared calculations into helper classes and functions
The code would benefit from extracting shared calculations and improving organization while preserving the core algorithms. Suggested changes:
- Extract shared trigonometric calculations into helper functions:
def calc_tidal_angles(t: float) -> TidalAngles:
"""Calculate common angles used in tidal computations"""
s = 218.31664563 + 481267.88194 * t - 0.0014663889 * t * t \
+ 0.00000185139 * t ** 3
h = 280.46645 + 36000.7697489 * t + 0.00030322222 * t * t \
+ 0.000000020 * t ** 3 - 0.00000000654 * t ** 4
# ... other shared angle calculations
return TidalAngles(s=s, h=h, ...)
- Create a TidalComponents class to handle coordinate transforms:
class TidalComponents:
def __init__(self, xsta: XYZ):
self.rsta = xsta.enorm8()
self.sinphi = xsta.z / self.rsta
self.cosphi = np.sqrt(xsta.x**2 + xsta.y**2) / self.rsta
self.sinla = xsta.y / self.cosphi / self.rsta
self.cosla = xsta.x / self.cosphi / self.rsta
def transform_tide(self, dr: float, de: float, dn: float) -> XYZ:
"""Transform tidal components to XYZ coordinates"""
return XYZ(
dr * self.cosla * self.cosphi - de * self.sinla
- dn * self.sinphi * self.cosla,
dr * self.sinla * self.cosphi + de * self.cosla
- dn * self.sinphi * self.sinla,
dr * self.sinphi + dn * self.cosphi
)
- Break detide() into smaller focused functions:
def compute_love_corrections(components: TidalComponents,
sun_moon: SunMoonPositions) -> XYZ:
"""Compute corrections for love number frequency dependence"""
diurnal = st1idiu(components, sun_moon)
semidiurnal = st1isem(components, sun_moon)
latitude = st1l1(components, sun_moon)
return diurnal + semidiurnal + latitude
These changes maintain the exact same calculations while reducing code duplication and improving maintainability.
Thank you for the PR, @piyushrpt! I am occupied by work this week, but I will try to get to this PR, mainly the testing, as said in #99, at the weekend. @scottstanie, please feel free to step in whenever you got a chance. |
All the unit tests etc have been updated. All we now need is someone to setup a bunch of tests - random times, locations etc and compare the 2 sets of numbers. There is no rush to this. The python code can also be further cleaned up as suggested by the bot here - but that would make the python implementation look significantly different from the original fortran code - which may / may not be desired. I will leave it up to you both - no strong preferences. |
pysolid.py_solid
is the python only implementation ofpysolid
pysolid
point_pyimpl.py
andgrid_pyimpl.py
have been added to tests. These essentially are same as the original tests except they usepy_solid
and have a couple of minor changes related to the function signatures inpy_solid
.Summary by Sourcery
Implement a Python-only version of the 'pysolid' library, named 'py_solid', to replace the original implementation. Update import statements to use relative paths and add new tests to verify the functionality of the new implementation.
New Features:
Enhancements:
Tests: