Closed csevast closed 6 years ago
Good catch. Fixed in 0.31.1 https://pypi.org/project/pyansys/0.30.1/
It is tested in the new release and it is ok.
Christos
Just so you know, I'm still not completely satisfied with the CORBA interface. Either ANSYS didn't put a lot of time into their software, or there's some fundamental limitations to the interface. Any command that changes the stdin or stdout breaks connection to the server or doesn't work. This includes the following commands that I know of:
I'm going to have to find a workaround within ANSYS or write a wrapper for these commands that redirects the output through the CORBA interface using Python. Any help would be greatly appreciated.
Thanks for testing the changes and updates thus far!
Alex
Dear Alex,
The /INPUT is very important for me because I am using it intensively in my APDL scripting. I am not sure that I can help you for the moment because I am abroad for holidays. After August I will start again. In meantime I found the following broken commands in pyansys github page examples:
""" Loading and Plotting an ANSYS Archive File
-- disp = result.GetNodalResult(0, True) # uses 0 based indexing ++ disp = result.NodalSolution(0) # uses 0 based indexing
Loading and Plotting an ANSYS Result File
-- result.PlotNodalResult(0, 'x', label='Displacement') ++ result.PlotNodalSolution(0, 'x', label='Displacement')
Reading a Full File
++ from pyansys import examples
-- fobj = pyansys.FullReader('file.full') ++ fobj = pyansys.FullReader(examples.fullfile)
++ import numpy as np
-- print '{:.3f} Hz'.format(f[i]) ++ print('{:.3f} Hz'.format(f[i])) """
Sincerely Christos
Dear Alex,
I tried the /INPUT command, let say ansys.Input('test.inp", "C:\tmp"), in interactive mode, it was successful and there was no connection breakdown. May be I didn't understand the problem.
Christos
On 8 August 2018 at 09:59, Alex Kaszynski notifications@github.com wrote:
Just so you know, I'm still not completely satisfied with the CORBA interface. Either ANSYS didn't put a lot of time into their software, or there's some fundamental limitations to the interface. Any command that changes the stdin or stdout breaks connection to the server or doesn't work. This includes the following commands that I know of:
- /INPUT
- VWRITE
- CDREAD
I'm going to have to find a workaround within ANSYS or write a wrapper for these commands that redirects the output through the CORBA interface using Python. Any help would be greatly appreciated.
Thanks for testing the changes and updates thus far!
Alex
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/akaszynski/pyansys/issues/34#issuecomment-411321420, or mute the thread https://github.com/notifications/unsubscribe-auth/AYDNp1qVf2_rAyl6T7RB7i9gXG5U9hXSks5uOppvgaJpZM4VwzbD .
That’s good news. I check again on my end. Thanks for testing it out! Let me know if you encounter any issues.
On Fri, Aug 10, 2018 at 21:00, Christos Sevastiadis < notifications@github.com> wrote:
Dear Alex,
I tried the /INPUT command, let say ansys.Input('test.inp", "C:\tmp"), in interactive mode, it was successful and there was no connection breakdown. May be I didn't understand the problem.
Christos
On 8 August 2018 at 09:59, Alex Kaszynski notifications@github.com wrote:
Just so you know, I'm still not completely satisfied with the CORBA interface. Either ANSYS didn't put a lot of time into their software, or there's some fundamental limitations to the interface. Any command that changes the stdin or stdout breaks connection to the server or doesn't work. This includes the following commands that I know of:
- /INPUT
- VWRITE
- CDREAD
I'm going to have to find a workaround within ANSYS or write a wrapper for these commands that redirects the output through the CORBA interface using Python. Any help would be greatly appreciated.
Thanks for testing the changes and updates thus far!
Alex
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/akaszynski/pyansys/issues/34#issuecomment-411321420 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AYDNp1qVf2_rAyl6T7RB7i9gXG5U9hXSks5uOppvgaJpZM4VwzbD
.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/akaszynski/pyansys/issues/34#issuecomment-412175744, or mute the thread https://github.com/notifications/unsubscribe-auth/ALbTP1HR8vKm9VdNDcO39xHGGL1kkFD3ks5uPdhlgaJpZM4VwzbD .
Dear Alex,
I tried to start the interactive_plotting mode of pyansys in my old laptop with Windows 7 and the following error raised.
""" In [7]: ansys = pyansys.ANSYS(run_location=path, interactive_plotting=True) Cached ANSYS executable not found Found ANSYS at C:\Program Files\ANSYS Inc\v181\ANSYS\bin\winx64\ansys181.exe Use this location? [Y/n]y
Exception Traceback (most recent call last)