| name | aqwa-batch-execution-locating-the-executable |
| description | Sub-skill of aqwa-batch-execution: Locating the Executable (+4). |
| version | 1.1.0 |
| category | engineering |
| type | reference |
| scripts_exempt | true |
Locating the Executable (+4)
Locating the Executable
find /ansys_inc -name "Aqwa" -type f 2>/dev/null
AQWA_EXE=/ansys_inc/v251/aqwa/bin/lnx64/Aqwa
ls -la ${AQWA_EXE}
Directory is lnx64 on most installations. Verify on your site — may also be lnamd64.
Running AQWA
${AQWA_EXE} std <jobname>
${AQWA_EXE} restart <jobname>
<jobname> is the .DAT file base name without extension.
All output files are written to the working directory as <jobname>.*.
Command File for Sequencing Multiple Jobs
echo -e "stage1\nstage2\nstage3" > mylist.com
${AQWA_EXE} std mylist.com
Checking Exit Status and Success
${AQWA_EXE} std analysis
if grep -qi "error\|fatal\|abort" analysis.mes 2>/dev/null; then
echo "AQWA FAILED — check analysis.mes and analysis.lis"
exit 1
elif [ -f analysis.res ] && [ -f analysis.plt ]; then
echo "AQWA SUCCEEDED"
else
echo "AQWA INCOMPLETE — check analysis.mes"
exit 1
fi
Full Two-Stage Pipeline Script
#!/usr/bin/env bash
set -euo pipefail
AQWA_EXE=/ansys_inc/v251/aqwa/bin/lnx64/Aqwa
JOBNAME=${1:-analysis}
check_run() {
local job=$1
if grep -qi "error\|fatal" ${job}.mes 2>/dev/null; then
echo "FAILED: ${job}"; cat ${job}.mes; exit 1
fi
[ -f ${job}.res ] || { echo "FAILED: no .res for ${job}"; exit 1; }
echo "OK: ${job}"
}
echo "=== Stage 1: AQWA-LINE (diffraction) ==="
${AQWA_EXE} std ${JOBNAME}
check_run ${JOBNAME}
echo "=== Stage 3: AQWA-NAUT (time domain) ==="
cp ${JOBNAME}.dat ${JOBNAME}_naut.dat
${AQWA_EXE} restart ${JOBNAME}_naut
check_run ${JOBNAME}_naut
echo "Pipeline complete."