Skip to content

Conversation

@henry2004y
Copy link
Owner

This change renames the AMReXParticleData class to AMReXParticle in src/flekspy/amrex/particle_data.py and updates all references across the codebase, including tests, documentation, and samples. This rename aims for conciseness and better alignment with other class names in the library.

Breaking Changes:

  • AMReXParticleData is now AMReXParticle. Users should update their code to use the new class name.

This change renames the `AMReXParticleData` class to `AMReXParticle` in `src/flekspy/amrex/particle_data.py` and updates all references across the codebase, including tests, documentation, and samples. This rename aims for conciseness and better alignment with other class names in the library.

Breaking Changes:
- `AMReXParticleData` is now `AMReXParticle`. Users should update their code to use the new class name.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @henry2004y, 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 focuses on a significant refactoring effort to rename the AMReXParticleData class to AMReXParticle. This change is driven by the goal of enhancing naming consistency and conciseness within the flekspy library. The update is comprehensive, touching all relevant files from core class definitions to imports, documentation, and tests, ensuring that the new, more intuitive class name is uniformly adopted throughout the project.

Highlights

  • Class Renaming: The AMReXParticleData class has been renamed to AMReXParticle to improve conciseness and align with existing naming conventions within the library.
  • Codebase-Wide Updates: All references to the old class name have been systematically updated across the entire codebase, including documentation, sample scripts, and unit tests, ensuring consistency.
  • Breaking Change: Users who directly import or instantiate AMReXParticleData will need to update their code to use the new AMReXParticle class name.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@codecov
Copy link

codecov bot commented Jan 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.34%. Comparing base (9c43e99) to head (c80c63a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #180   +/-   ##
=======================================
  Coverage   78.34%   78.34%           
=======================================
  Files          31       31           
  Lines        4341     4341           
=======================================
  Hits         3401     3401           
  Misses        940      940           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@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 primarily renames the AMReXParticleData class to AMReXParticle across the entire codebase. This change is reflected in imports, class definitions, docstrings, code examples in docs/amrex_data.ipynb, sample scripts like samples/vdf_matrix.py, and all relevant test files (tests/test_amrex_3d_plots.py, tests/test_amrex_loader.py, tests/test_fleks.py, tests/test_gmm_parameters.py). The flekspy/__init__.py file was also updated to correctly export and load the newly named class. There were no review comments provided for these changes.

@henry2004y henry2004y merged commit fc8fb30 into main Jan 2, 2026
3 checks passed
@henry2004y henry2004y deleted the rename-amrexparticledata-to-amrexparticle-15348158834557875116 branch January 2, 2026 23:23
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.

1 participant