Add HelioAI to the project list - #388
Open
erdoganfurkan wants to merge 1 commit into
Open
Conversation
Contributor
|
Thank you for your submission, @erdoganfurkan! Sounds like a cool project. Just wanted to let you know I've seen this, but I may not get around to reviewing it for another week or so. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds HelioAI to the PyHC project list.
HelioAI is an AI agent for heliophysics and space plasma physics. It resolves natural-language descriptions to parameter identifiers across 70+ missions using hybrid semantic and lexical retrieval over the speasy catalogue, downloads the data, runs the analysis in a sandboxed Python environment with PlasmaPy-based tools and cited method recipes, and exports each session as a self-contained, re-runnable Jupyter notebook.
pip install helioai-agent(0.2.1)Self-review against the six standards — five "Good", one "Partially met":
--strictmode, guides and developer docs, 99% of public objects documented — but docstringArgs:/examples reach only 35%/23% of the public surface, short of standard 8heliophysicsPy/pyhc-actions/phep3-compliancegreen in CIThe Documentation grade is deliberately orange: an evaluation run against the PyHC standards found docstring examples covering 23% of the public API, which does not meet standard 8's requirement for all functions and classes. Completing the
Args:/Returns:/Example:sections is the next documentation task, tracked for a 0.2.x release.Happy to adjust the entry — keywords, description, or grades — if anything looks off.