Skip to content

Conversation

@DavidFang03
Copy link
Collaborator

Tillotson EoS was originally designed for high velocity impacts [Tillotson 1962] and has been extended to geologic materials, for example [Brundage 2013]

Figure_1

Usage:

cfg.set_eos_tillotson(rho0, E0, A, B, a, b, alpha, beta, u_iv, u_cv)

@gemini-code-assist
Copy link

Summary of Changes

Hello @DavidFang03, 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 introduces the Tillotson Equation of State (EoS) into the shammodels physics simulation framework. This EoS is particularly relevant for modeling high-velocity impacts and geologic materials, as highlighted in the PR description. The changes involve integrating the new EoS into the configuration system, implementing its physical calculations, and exposing it through both C++ and Python interfaces, thereby enhancing the simulation capabilities of the project.

Highlights

  • New EoS Integration: The Tillotson Equation of State (EoS) has been added, expanding the available physical models for high-velocity impacts and geologic materials.
  • Configuration Support: The EOSConfig now includes the Tillotson EoS as a variant, along with a dedicated set_tillotson method for easy configuration of its parameters.
  • Serialization/Deserialization: JSON serialization and deserialization have been implemented for the Tillotson EoS parameters, ensuring persistence and configurability through JSON files.
  • Simulation Engine Update: The ComputeEos module has been updated to correctly calculate pressure and sound speed using the newly integrated Tillotson EoS within the simulation engine.
  • Python API Exposure: Python bindings have been added, allowing users to configure the Tillotson EoS directly from Python scripts, enhancing usability and scripting capabilities.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a 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 the Tillotson Equation of State (EoS), a feature useful for high-velocity impact simulations. The changes span across the configuration, serialization, core physics implementation, and Python bindings. The implementation is comprehensive, adding the necessary logic for the new EoS in various parts of the system.

My review focuses on improving code quality, correctness, and maintainability. I've identified a critical bug in an equality operator that misses some fields, which could lead to incorrect behavior. I've also pointed out several areas for code cleanup and improvement, such as removing redundant code, fixing typos in documentation, completing a TODO, and improving code style for better readability. These suggestions will help ensure the new code is robust and easy to maintain.

Comment on lines +175 to +183
auto [p, dpdrho, dpdu] = compute_cold();
P = p;
dP_drho = dpdrho;
dP_du = dpdu;
} else if (u > u_cv) {
auto [p, dpdrho, dpdu] = compute_hot();
P = p;
dP_drho = dpdrho;
dP_du = dpdu;

Choose a reason for hiding this comment

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

medium

The blocks for the if and else if conditions contain identical logic for unpacking the tuple and assigning values to P, dP_drho, and dP_du. This can be simplified by using std::tie to assign values directly to these variables, making the code more concise and less repetitive.

                std::tie(P, dP_drho, dP_du) = compute_cold();
            } else if (u > u_cv) {
                std::tie(P, dP_drho, dP_du) = compute_hot();
            } else {

* @tparam Tscal Scalar type
*
* The equation of state is given by:
* TODO

Choose a reason for hiding this comment

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

medium

The documentation for EOS_Config_Tillotson contains a TODO marker. This should be filled in with the equation of state to provide complete documentation for users of this struct.

@DavidFang03 DavidFang03 changed the title [Phys] Add Tillotson EoS [SPH][Phys] Add Tillotson EoS Dec 16, 2025
@github-actions
Copy link

Workflow report

workflow report corresponding to commit 62818e2
Commiter email is david.fang@ikmail.com

Light CI is enabled. This will only run the basic tests and not the full tests.
Merging a PR require the job "on PR / all" to pass which is disabled in this case.

Pre-commit check report

Some failures were detected in base source checks checks.
Check the On PR / Linting / Base source checks (pull_request) job in the tests for more detailled output

❌ Authorship update required

The following files had their author headers updated by the author update script.

Please run the script again (python3 buildbot/update_authors.py) and commit these changes.

Note: The list below is only partial. Only the first 10 files are shown.

  • /src/shampylib/src/pyShamphys.cpp

Suggested changes

Detailed changes :
diff --git a/src/shampylib/src/pyShamphys.cpp b/src/shampylib/src/pyShamphys.cpp
index dedbe873..59132730 100644
--- a/src/shampylib/src/pyShamphys.cpp
+++ b/src/shampylib/src/pyShamphys.cpp
@@ -9,6 +9,7 @@
 
 /**
  * @file pyShamphys.cpp
+ * @author David Fang (david.fang@ikmail.com)
  * @author Timothée David--Cléris (tim.shamrock@proton.me)
  * @brief
  */

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants