-
Notifications
You must be signed in to change notification settings - Fork 3
Example/busbar joule heating #436
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: main
Are you sure you want to change the base?
Conversation
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.
@gmalinve Ready for review.
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.
@gchaturve: Great to have you contributing to the examples! Could you please take a look at the template we've tried to use for the examples? We still have not updated all the examples to match the template. That is an important task though.
The numbering of sections seems like a good idea, but the overall workflow should use at least H2 and H3 levels as was shown in the template: 1. Setup, 2. Solve, 3. Evaluate results.
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.
Thankyou @Devin-Crawford I'll review the template and align my example with the required H2/H3 section levels (Setup, Solve and Evaluate Results)
I'll update it shortly to ensure it matches the structure and conventions shown in the template
| @@ -0,0 +1,343 @@ | |||
| # %% [markdown] | |||
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.
Why are you adding the # %% [markdown] label everywhere ? If it's required for a specific reason, can you let me know why ? We're currently relying on jupytext and notebook related packages to handle the documentation.
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.
I have added these %% [markdown] blocks so that scripts can be opened and navigated seamlessly in VS Code/ Pycharm interactive mode. This is for ensuring both code cells & documentation cells are preserved in a notebook-like -structure while using the IDE (without requiring a full .ipynb workflow)
Purpose:
- To make example easier to run step by step in IDE's that support cell excecution
- To keep the documentation inlingned and synchronized with the code (similar to jupyter)
- To maintain consistency across different environments (may prefer VS Code over jupyter)
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.
@gchaturve : You can also run/edit in Jupyter Lab using Jupytext. That was the idea behind the formatting we've used. The files also have to be parsed and rendered as HTML so the %% may cause problems with the CI/CD. I'll defer to @SMoraisAnsys.
- Changed cell markers from # %% to # + and # - - Updated tmpdir to temp_folder for consistency - Reorganized sections to match template structure - Added temp_folder.cleanup() at end - Preserved all functionality and analysis content
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.
I have aligned example with template and updated it Waiting for the feedback !!
|
Hi @gchaturve , Thanks for taking care of the comments. On top of aligning your example with the template, I would suggest also two other things:
Giulia |
16574da to
36222a8
Compare
Description
Created a multi terminal busbar joule heating example under eddy current solution type.
Checklist
Please complete the following checklist before submitting your pull request: