fix init

[jan-janssen]

Summary by CodeRabbit

• New Features
  • Added band structure and density of states plotting functions to the available phonopy workflows. These features are now accessible as part of the public interface.

[coderabbitai]

Walkthrough

The changes update the atomistics.workflows package initialization to include plot_band_structure and plot_dos as part of its phonopy-related public API. These functions are now imported from the helper module and added to the list of exported workflow functions.

Changes

File(s)	Change Summary
atomistics/workflows/init.py	Added plot_band_structure and plot_dos to imports and exports.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

Two new plots join the band,
In workflows now they proudly stand.
Bands and DOS, a visual treat,
For science rabbits—oh, so neat!
With every hop, the features grow,
In atomistics, onward we go!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch init

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

atomistics/workflows/__init__.py (1)

53-55: Consider keeping phonopy_workflows alphabetical for quick scanning

The newly‐added entries are correct, but the list is now a mixed ordering of analysis, getter, and plot helpers.
Keeping the list alphabetically sorted (or otherwise consistently grouped) helps future maintainers spot duplicates and missing exports faster.

     "analyse_results_for_quasi_harmonic_approximation",
     "get_thermal_properties_for_quasi_harmonic_approximation",
+    "plot_band_structure",
+    "plot_dos",
-    "plot_band_structure",
-    "plot_dos",

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e2b80a1 and 7d67623.

📒 Files selected for processing (1)

• atomistics/workflows/__init__.py (2 hunks)

🔇 Additional comments (1)

atomistics/workflows/__init__.py (1)

66-68: Confirmed: plot_band_structure and plot_dos are correctly exposed
Both functions are defined in atomistics/workflows/phonons/helper.py and imported in atomistics/workflows/__init__.py, so the public API will include them as intended.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.31%. Comparing base (e2b80a1) to head (7d67623).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #507   +/-   ##
=======================================
  Coverage   85.31%   85.31%           
=======================================
  Files          43       43           
  Lines        2587     2587           
=======================================
  Hits         2207     2207           
  Misses        380      380           

☔ 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.