-
Notifications
You must be signed in to change notification settings - Fork 21
[Phys][GRSPH] Add metric terms #1552
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
base: main
Are you sure you want to change the base?
Conversation
|
Thanks @y-lapeyre for opening this PR! You can do multiple things directly here: Once the workflow completes a message will appear displaying informations related to the run. Also the PR gets automatically reviewed by gemini, you can: |
Summary of ChangesHello @y-lapeyre, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request introduces calculations for the Kerr metric, including the covariant and contravariant metric tensors and their derivatives. The use of tag dispatching (e.g., struct Kerr {}) to select the metric is a good design choice.
However, the implementation has several significant issues that need to be addressed:
- Critical bugs: There are uninitialized variables in
get_cartesian_cov_metric_implandget_cartesian_contrav_metric_impldue to incorrect coordinate unpacking, which will lead to undefined behavior. - Reusability: Metric parameters like spin and mass are hardcoded, which limits the use of these functions to a single specific black hole. These should be parameterized.
- Correctness: The implementation for the contravariant metric contains a comment highlighting a known singularity issue that has not been addressed. This could lead to incorrect results or numerical instability.
- Code Quality: There are some areas for improvement in code quality, such as very long and hard-to-read lines for the derivative calculations, and an unprofessional comment.
While I understand the sentiment that these GR formulae might not be touched again, ensuring their correctness, readability, and reusability from the start is crucial for the long-term health of the codebase. Please see the detailed comments for specific suggestions.
tdavidcl
left a comment
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.
Looks very nice, what do you want to use in place of Tvec in practice ? Mat4x4 from the math library with mdspan ? (I'm fine with the template signature)
Workflow reportworkflow report corresponding to commit a6c2863 Light CI is enabled. This will only run the basic tests and not the full tests. Pre-commit check reportPre-commit check: ✅ Test pipeline can run. Doxygen diff with
|
Is it ok with tags like this or should I use templates for the choice of metric?
I think of putting all terms of all metrics in this file. Yes it will be long, but at the end of the day it's just GR formulae we will never touch again.