Skip to content

Export mesh exception for Q3D API #1231

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

Merged
merged 9 commits into from
Jun 1, 2022
Merged

Conversation

Samuelopez-ansys
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented May 30, 2022

Codecov Report

Merging #1231 (8a8c442) into main (ca3415b) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1231      +/-   ##
==========================================
+ Coverage   77.59%   77.62%   +0.03%     
==========================================
  Files          96       96              
  Lines       37710    37778      +68     
==========================================
+ Hits        29261    29326      +65     
- Misses       8449     8452       +3     

@@ -250,7 +250,7 @@ def plot(
)

@pyaedt_function_handler()
def export_mesh_stats(self, setup_name, variation_string="", mesh_path=None):
def export_mesh_stats(self, setup_name, variation_string="", mesh_path=None, setup_type="CG"):
Copy link
Contributor

Choose a reason for hiding this comment

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

is it good to put Q3D specific parts into general function?

@maxcapodi78
your thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

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

Another option could be to create a different method only for Q3D...

Copy link
Contributor

Choose a reason for hiding this comment

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

don't know. However, changing signature just because of Q3D.
from other side over-complicating things is also not good

Copy link
Member Author

Choose a reason for hiding this comment

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

Hi @maxcapodi78 , could you check if this PR makes sense? Or should I create a different method for Q3D? Thanks!

Copy link
Member Author

Choose a reason for hiding this comment

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

I have created an overridden method in q3d.py, to keep the original one. But the Codacy is complaining because I added one parameter that is not available in the original method, any suggestion? should I rename the method in q3d.py to avoid this issue? Thanks! @maxcapodi78 @beliaev-maksim

@Samuelopez-ansys Samuelopez-ansys merged commit ae89691 into main Jun 1, 2022
@Samuelopez-ansys Samuelopez-ansys deleted the issue_exportmesh_q3d branch June 1, 2022 14:27
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.

2 participants