-
Notifications
You must be signed in to change notification settings - Fork 92
Revise README with mermaid flowcharts #762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 0.3
Are you sure you want to change the base?
Conversation
Updated the README to reflect PINA modules structure and added flowcharts for steps to follow.
Code Coverage SummaryResults for commit: 3209ce9 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
GiovanniCanali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice feature!
Unfortunately, the links in the diagram do not properly represent the structure in PINA. For instance, pina.optim does not depend upon pina.solver. The vast majority of modules depend directly on pina. Is there a way to make this without having a diagram which is too wide?
README.md
Outdated
| direction LR | ||
| PROB["<h2>pina.problem</h2> Module for defining problems via base class inheritance"] | ||
| MODEL["<h2>pina.model</h2> Module for built-in PyTorch models full architectures"] | ||
| SOLVER["<h2>pina.solve</h2>r Module for built-in solvers and abstract interfaces"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing "r" in pina.solver
Yeah, I just tried to make a diagramm similar to the API image, but the structure should be a little bit different. We can also have "invisible" edges if needed. My only focus here is changing static to dynamic! |
Updated the README to reflect PINA modules structure and added flowcharts for steps to follow.
Description
This PR replaces the static PNG diagram in the README with an equivalent Mermaid (link) diagram.
The goal is to make the architecture diagram easier to maintain and update over time, avoiding the need to regenerate image assets for small documentation changes. The new Mermaid diagram mirrors the original structure and module hierarchy and is fully compatible with GitHub rendering.
Checklist