FIX: interference_type.py

[jsalant22]

Fix the check for a read-only directory

Description

Example would give a warning about a read-only directory when trying to Generate Results

Issue linked

(https://tfs.ansys.com:8443/tfs/ANSYS_Development/Portfolio/_boards/board/t/EBU-EMIT/Stories/?workitem=1263233)

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.

[anspraksaph]

For this PR, I tested with PyAedt main branch (Commit hash: cc29743c5b51c81b2e7ed84c211ed955405f3e12) and Aedt 26.1, this defect is fixed.

• interference_type.py

[Samuelopez-ansys]

Hi @jsalant22 @anspraksaph

I think these EMIT examples does not fit the example structure. If I understand well they are building an UI .

Then, for me they are extension. Which are in PyAEDT.

correct me if I am wrong, in addition to, you are using pyside6, which is a dependency that it is not part of PyAEDTA.

Extensions use tkinter, which is part of the python installation.

please, could you consider migrate these Workflows to extensions? Ping me if you need more info.

examples should be end to end workflows, that you can run as python scripts or Jupyter notebook scripts

CC @SMoraisAnsys

[jsalant22]

@Samuelopez-ansys Can you send me a link to the extensions or a template? Are they part of the main PyAedt repo?

[Samuelopez-ansys]

@jsalant22 For more than 1 year :)

https://aedt.docs.pyansys.com/version/stable/User_guide/extensions.html

Template:

https://aedt.docs.pyansys.com/version/stable/User_guide/pyaedt_extensions_doc/templates/getting_started.html

And how to create a a new one step by step:

https://aedt.docs.pyansys.com/version/stable/Getting_started/Contributing.html#extension-development-guide

[jsalant22]

@jsalant22 Thanks! This example and UI is ~2 years old, that's why we didn't implement as an extension.

We'll look into converting it though!