Skip to content

Conversation

@gchaturve
Copy link
Collaborator

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:

  • I have followed the example template and guide lines to add/update an example.
  • I have tested the example locally and verified that it is working with the latest version of AEDT.
  • I have verified that these changes to the best of my knowledge do not introduce any security vulnerabilities.

@gchaturve gchaturve self-assigned this Sep 25, 2025
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gmalinve Ready for review.

Copy link
Collaborator

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.

Copy link
Collaborator Author

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

@gchaturve gchaturve marked this pull request as ready for review September 25, 2025 16:22
@@ -0,0 +1,343 @@
# %% [markdown]
Copy link
Collaborator

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.

Copy link
Collaborator Author

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:

  1. To make example easier to run step by step in IDE's that support cell excecution
  2. To keep the documentation inlingned and synchronized with the code (similar to jupyter)
  3. To maintain consistency across different environments (may prefer VS Code over jupyter)

Copy link
Collaborator

@Devin-Crawford Devin-Crawford Oct 7, 2025

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.

@gchaturve gchaturve requested a review from SMoraisAnsys October 1, 2025 04:44
- 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
Copy link
Collaborator Author

@gchaturve gchaturve left a 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 !!

@gmalinve
Copy link
Collaborator

gmalinve commented Oct 9, 2025

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:

  • remove the .gitignore file, this is something personal to your vs environment.
  • I think there are too many print statements. For me it's ok to have print of results but not for info messages because this is already done by PyAEDT logger.
    Thanks again :)

Giulia

@gchaturve gchaturve force-pushed the example/busbar_joule_heating branch from 16574da to 36222a8 Compare October 10, 2025 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants