Skip to content

Conversation

@alarshi
Copy link
Contributor

@alarshi alarshi commented Jan 21, 2025

Same as #791 , but to the current remote :)

@alarshi
Copy link
Contributor Author

alarshi commented Jan 21, 2025

Thank you for the review, @MFraters . I addressed your suggestions in the recent commit.

Copy link
Member

@MFraters MFraters left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small comment, otherwise good to go

```
The main file that is responsible for creating and accessing the GWB world is `source/world_builder/world.cc`. When creating a new GWB world it uses the parameterizations from the worldbuilder (`*.wb`) input file. External programs, such as `gwb-dat` or `gwb-grid` or other software such as ASPECT or SEPRAN, can then use the provided interfaces to ask about certain properties (e.g. temperature, composition) on any location.

GWB determines where a given point lies in the World amongst the specified tectonic features. This happens mostly through utility functions, which computes the distance of point from a feature. These and several other utility functions are defined in the `source/world_builder/utilities.cc`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
GWB determines where a given point lies in the World amongst the specified tectonic features. This happens mostly through utility functions, which computes the distance of point from a feature. These and several other utility functions are defined in the `source/world_builder/utilities.cc`.
GWB determines where a given point lies in the World amongst the specified tectonic features. This happens mostly through utility functions, which compute the distance of point from a feature. These and several other utility functions are defined in the `source/world_builder/utilities.cc`.

@github-actions
Copy link

github-actions bot commented Jan 21, 2025

Benchmark Main Feature Difference (99.9% CI)
Slab interpolation simple none 1.135 ± 0.010 (s=367) 1.135 ± 0.011 (s=429) -0.3% .. +0.2%
Slab interpolation curved simple none 1.119 ± 0.010 (s=388) 1.118 ± 0.009 (s=419) -0.2% .. +0.2%
Spherical slab interpolation simple none 1.099 ± 0.008 (s=393) 1.101 ± 0.010 (s=428) +0.0% .. +0.4%
Slab interpolation simple curved CMS 1.165 ± 0.012 (s=384) 1.165 ± 0.010 (s=391) -0.3% .. +0.2%
Spherical slab interpolation simple CMS 1.444 ± 0.012 (s=303) 1.444 ± 0.012 (s=323) -0.2% .. +0.2%
Spherical fault interpolation simple none 1.099 ± 0.007 (s=411) 1.100 ± 0.008 (s=410) -0.1% .. +0.2%
Cartesian min max surface 2.760 ± 0.041 (s=170) 2.756 ± 0.045 (s=159) -0.7% .. +0.4%
Spherical min max surface 7.328 ± 0.064 (s=67) 7.343 ± 0.103 (s=58) -0.5% .. +0.9%

Address suggestions from the PR.

Grammar fix.
@alarshi alarshi force-pushed the add-code-structure branch from e01ff7c to dc40a30 Compare January 21, 2025 18:12
@alarshi
Copy link
Contributor Author

alarshi commented Jan 21, 2025

Thank you for the review! I addressed your comments in the latest commit.

@alarshi alarshi merged commit 36d23e2 into GeodynamicWorldBuilder:main Jan 21, 2025
36 of 37 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.

2 participants