Add cdo and nco

[mathomp4]

Closes #33
Closes #32

This PR adds the nco and cdo Python bindings. As @viral211 pointed out to me, if installed via pip, we don't pull down any executables, so it would use the ones from Baselibs. Seems safe!

[coderabbitai]

Walkthrough

The changes update the installation process and documentation to explicitly add two new Python packages, nco and cdo, to the project. The install_miniforge.bash script is modified to install these packages via pip, and the CHANGELOG.md is updated to document their addition under the "Unreleased" section. No changes to application logic, error handling, or exported entities are present.

Changes

Files	Change Summary
CHANGELOG.md	Updated to include nco and cdo as newly added pip packages.
install_miniforge.bash	Modified to install nco and cdo via pip in the Miniforge environment.

Assessment against linked issues

Objective	Addressed	Explanation
Add cdo-bindings (cdo) package without interfering with Baselibs (#33)	✅
Add pynco (nco) package without interfering with Baselibs (#32)	✅

Possibly related PRs

• Prepare changelog for release #30: This PR also modifies the changelog, but focuses on restructuring and formatting rather than adding new packages.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fb7d154 and 933039d.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• install_miniforge.bash (1 hunks)

🔇 Additional comments (2)

CHANGELOG.md (1)

16-18: Changelog update is clear and accurate.

The addition of nco and cdo under explicit pip packages is well-documented and follows the established changelog format.

install_miniforge.bash (1)

689-690: Addition of nco and cdo pip installs is correct and safe.

These lines correctly add the Python bindings for NCO and CDO. The approach aligns with the PR objectives and is safe, as executables are not installed via pip but are expected from Baselibs.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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