Not able to create a solver output file

[RGPATCHI]

When running a simple MAPDL PyAnsys script in PyCharm, I am interested in redirecting the solver output to a directory (so that I can review it later on). I used the below two commands to set the current working directory and set the solver output file.

Once I run the model, I see that the file myoutput.out was created in the working directory, but its blank.

mapdl.cwd(r'D:\Test\mapdl_run')
mapdl.run('/output,myoutput.out')

Please let me know if its possible to have a solver output file (similar to a batch MAPDL run). This will be very useful.

[chart-magnum]

Would this APDL code be of help?

*cfopen,myoutput,out,,append
*vwrite,
('    syin','    syou','    sxmn','    symn','    seqv')

*vwrite,syin,syou,sxmin,symin,seqv
(5F8.1)

*cfclos,myoutput,out

[mikerife]

Hi @RGPATCHI not sure if this is 100% true as I am still wrapping my head around PyMAPDL and MAPDL as a Service. But I don't think that is possible as MAPDL as a Service is not the same as interactive/batch mode. I think that ".tmp.out" is created when an MAPDL instance is launched from PyMAPDL. But it does not capture the whole output file as we (MAPDL users) are used to as some PyMAPDL commands seem to redirect to temp output files.

If you are looking to capture the solve part of the output file try this:

solve_1 = mapdl.solve()
print(solve_1)

That will give the output respecting the /n (new lines). Or you could dump the contents of solve_1 to a file Pythonically.

Mike

p.s. is pythonically even a word?

[germa89]

For some of us, it is a word. Pythonically speaking.

[germa89]

As @mikerife mentioned, the output when MAPDL is running using the gRPC API is quite spread over different files.
When we issue a command in PyMAPDL, the MAPDL instance receives the equivalent MAPDL commands, which they are written to a temporary output file. This output file is read by MAPDL and send back to the PyMAPDL. This file later deleted. Not all the commands presents this behavior.
Therefore the output of commands (file.out) can be spread among:

• .__tmp__.out which is used when MAPDL is launched.
• anstmp.out which is the one generated by each MAPDL command.
• _input_tmp_.out which is the output from everytime issue mapdl.input, or using mapdl.non_interactive.
• The "each-thread" output files (file1.out, file2.out, etc).
• Other out files which are created when we issue mapdl.run("/out, new_file'') (there should be none)

Therefore there is no way (currently) of obtaining a file similar to the output file given by a batch run.

[pmaroneh]

For debugging purposes, it would be very useful to have some way of getting the MAPDL commands sent to the MAPDL instances as well as concatenated .out file. Is this something you could consider in the future ?

[germa89]

Hi @pmaroneh , the MAPDL commands sent can be recorded using log_apdl (https://mapdldocs.pyansys.com/api/_autosummary/ansys.mapdl.core.launch_mapdl.html?highlight=log_apdl).

The concatenated out files is more complicated, because it is difficult to keep track of all the out files. We would like to, but it is not easy thing.