Skip to content
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

FEAT: Identify coupling 5649 #5659

Open
wants to merge 33 commits into
base: main
Choose a base branch
from
Open

FEAT: Identify coupling 5649 #5659

wants to merge 33 commits into from

Conversation

amichel0205
Copy link
Contributor

@amichel0205 amichel0205 commented Jan 15, 2025

Description

Please provide a brief description of the changes made in this pull request.

Issue linked

Please mention the issue number or describe the problem this pull request addresses.

Checklist

  • I have tested my changes locally.
  • I have added necessary documentation or updated existing documentation.
  • I have followed the coding style guidelines of this project.
  • I have added appropriate tests (unit, integration, system).
  • I have reviewed my changes before submitting this pull request.
  • I have linked the issue or issues that are solved by the PR if any.
  • I have agreed with the Contributor License Agreement (CLA).

@amichel0205 amichel0205 added the enhancement New features or code improvements label Jan 15, 2025
@amichel0205 amichel0205 self-assigned this Jan 15, 2025
@ansys-reviewer-bot
Copy link
Contributor

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

@amichel0205 amichel0205 changed the title Identify coupling 5649 FEAT:Identify coupling 5649 Jan 15, 2025
Copy link

codecov bot commented Jan 15, 2025

Codecov Report

Attention: Patch coverage is 86.11111% with 5 lines in your changes missing coverage. Please review.

Project coverage is 79.98%. Comparing base (be8f391) to head (3785fbb).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5659      +/-   ##
==========================================
- Coverage   85.21%   79.98%   -5.23%     
==========================================
  Files         156      156              
  Lines       61070    61106      +36     
==========================================
- Hits        52038    48876    -3162     
- Misses       9032    12230    +3198     

@amichel0205 amichel0205 changed the title FEAT:Identify coupling 5649 FEAT: Identify coupling 5649 Jan 15, 2025
@amichel0205 amichel0205 requested review from Samuelopez-ansys and hui-zhou-a and removed request for hui-zhou-a and SMoraisAnsys January 27, 2025 07:59
Copy link
Contributor

@hui-zhou-a hui-zhou-a left a comment

Choose a reason for hiding this comment

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

@amichel0205 please use a valid s-parameter for testing.

tests/system/general/test_44_TouchstoneParser.py Outdated Show resolved Hide resolved
Copy link
Member

@Samuelopez-ansys Samuelopez-ansys left a comment

Choose a reason for hiding this comment

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

Hi @amichel0205 ,

I think the argument log_file_name should be the last one and not the first one, because it is only used when you want to save it.

In addition, you should change the name, to output_file, we are trying to make consisten name of variables in all PyAEDT, the methods, the description could be something like:

Output file path to save .... . If None no file is saved.

The same for start_at_frequency, should be start_frequency keeping consistency.

@Samuelopez-ansys Samuelopez-ansys enabled auto-merge (squash) February 3, 2025 14:59
Copy link
Member

@Samuelopez-ansys Samuelopez-ansys left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@SMoraisAnsys SMoraisAnsys left a comment

Choose a reason for hiding this comment

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

I left some refactoring proposition.

@amichel0205 amichel0205 requested review from SMoraisAnsys and removed request for hui-zhou-a February 4, 2025 09:38
Copy link
Contributor

@hui-zhou-a hui-zhou-a left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features or code improvements
Projects
None yet
4 participants