18 November 2019
- Last edited 20 November 2019
Is there a particular reason for doing mesh in batch? Unlike CFD meshes, structural meshes are not CPU intensive generally.
Being said that :
1. Mechanical (setup cell of static structural system) does not record operations done in a Journal file similar to what you have seen in Fluent, most of these tasks can be done using ACT APIs though.
2. One way of doing this is by setting up an RSM pointing to a cluster, which will do the heavy lifting of the solution, while the local machine can just import the result file and post-process the results. If your model and results are parametric this can be very much done without learning to code using ACT or learning APDL and by integrated into GUI
3. Another way of doing these things mentioned in 2nd option above is to generate an input file from Static structural for APDL and using this generated input file one can solve using a command such as following on the cluster: "C:\Program Files\ANSYS Inc\v195\ansys\bin\winx64\MAPDL.exe" -p ansys -smp -np 2 -lch -dir "C:\myWorkingDirectory" -j "JobName" -s read -l en-us -b -i "C:\myWorkingDirectory\input.dat" -o "C:\myWorkingDirectory\solverOut.out"
option 2 is basically automation of option 3. Note in both cases mesh would be done on the local machine and it will be transferred to the cluster to solve.
4. final way is to generate and create your own APDL input file using command reference for APDL
Choosing your option will depend on your exact requirement and comfort level with Python or APDL.
Guidelines on the Student Community
How to access ANSYS help links