aqwa-batch-execution-locating-the-executable
Sub-skill of aqwa-batch-execution: Locating the Executable (+4).
Best use case
aqwa-batch-execution-locating-the-executable is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of aqwa-batch-execution: Locating the Executable (+4).
Teams using aqwa-batch-execution-locating-the-executable should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/locating-the-executable/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How aqwa-batch-execution-locating-the-executable Compares
| Feature / Agent | aqwa-batch-execution-locating-the-executable | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of aqwa-batch-execution: Locating the Executable (+4).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Locating the Executable (+4)
## Locating the Executable
```bash
# Find the AQWA executable (path varies by installation)
find /ansys_inc -name "Aqwa" -type f 2>/dev/null
# Typical Linux path (v2025 R1)
AQWA_EXE=/ansys_inc/v251/aqwa/bin/lnx64/Aqwa
# Confirm it exists and is executable
ls -la ${AQWA_EXE}
```
> Directory is `lnx64` on most installations. Verify on your site — may also be `lnamd64`.
## Running AQWA
```bash
# Standard (fresh) run — program type determined by .DAT JOB card
${AQWA_EXE} std <jobname>
# Restart run (continue from previous stage)
${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
```bash
# Create a .com file listing jobnames, one per line
echo -e "stage1\nstage2\nstage3" > mylist.com
# Run all jobs in sequence
${AQWA_EXE} std mylist.com
```
## Checking Exit Status and Success
```bash
${AQWA_EXE} std analysis
# Exit code is unreliable — check output files instead:
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
```bash
#!/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) ==="
# JOB card in ${JOBNAME}.DAT must read: JOB analysis LINE
${AQWA_EXE} std ${JOBNAME}
check_run ${JOBNAME}
echo "=== Stage 3: AQWA-NAUT (time domain) ==="
# Separate .DAT with JOB card: JOB analysis NAUT + RESTART 3 3
cp ${JOBNAME}.dat ${JOBNAME}_naut.dat
# (edit RESTART record to 3 3 and JOB code to NAUT before running)
${AQWA_EXE} restart ${JOBNAME}_naut
check_run ${JOBNAME}_naut
echo "Pipeline complete."
```Related Skills
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
batch-syntax-repair-from-injection-errors
Detect and fix systematic syntax errors caused by line-injection scripts that split multiline constructs
batch-syntax-fix-with-regex-line-based-fallback
Fix repeated syntax errors across many files using regex, then fall back to line-based parsing when regex fails
batch-syntax-fix-regex-iteration
Iteratively fix widespread syntax errors across many files using regex refinement when initial patterns fail
batch-syntax-fix-pattern
Identify and repair cascading import/syntax errors across multiple files using regex-based line-scanning and verification
batch-regex-fix-import-syntax
Detect and fix mid-import blank-line syntax breaks across multiple files using line-based regex
plan-governance-vs-execution-boundary-for-adversarial-review
Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.
interactive-issue-execution-worktree-guardrails
Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.
gtm-prospect-pipeline-phased-execution
Phased execution pattern for