aqwa-batch-execution-license-architecture
Sub-skill of aqwa-batch-execution: License Architecture (+3).
Best use case
aqwa-batch-execution-license-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of aqwa-batch-execution: License Architecture (+3).
Teams using aqwa-batch-execution-license-architecture 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/license-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How aqwa-batch-execution-license-architecture Compares
| Feature / Agent | aqwa-batch-execution-license-architecture | 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: License Architecture (+3).
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
# License Architecture (+3)
## License Architecture
- Base solver (`ansys` feature): **4 cores free** with Mechanical Enterprise licence
- Beyond 4 cores: requires HPC Pack (`aa_r_hpc`) or Ansys HPC licence
- AQWA uses **OpenMP (shared-memory only)** — all cores must be on a single node
- MPI / multi-node is not supported
## Environment Variables
```bash
export ANSYSLMD_LICENSE_FILE=1055@license-server.domain.com
export ANSYSLI_SERVERS=2325@license-server.domain.com
export OMP_NUM_THREADS=8 # Must match NUM_CORES in Deck 0 (or WB setting)
ulimit -s unlimited # Required for large models
```
## SLURM Job Script — Standalone
```bash
#!/usr/bin/env bash
#SBATCH --job-name=aqwa_line
#SBATCH --partition=compute
#SBATCH --nodes=1 # AQWA is SMP — single node only
#SBATCH --ntasks=1
#SBATCH --cpus-per-task=8
#SBATCH --mem=32G
#SBATCH --time=04:00:00
#SBATCH --output=aqwa_%j.out
#SBATCH --error=aqwa_%j.err
module load ansys/v251 # Module name is site-specific
export ANSYSLMD_LICENSE_FILE=1055@license-server
export ANSYSLI_SERVERS=2325@license-server
export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK}
AQWA_EXE=/ansys_inc/v251/aqwa/bin/lnx64/Aqwa
WORK_DIR=/scratch/${USER}/${SLURM_JOB_ID}
mkdir -p ${WORK_DIR}
cp analysis.dat ${WORK_DIR}/
cd ${WORK_DIR}
${AQWA_EXE} std analysis
if [ -f analysis.res ]; then
echo "SUCCESS"
cp analysis.lis analysis.res analysis.plt analysis.ah1 ${SLURM_SUBMIT_DIR}/
else
echo "FAILED — check analysis.mes:"
cat analysis.mes
exit 1
fi
```
## SLURM Job Script — Workbench (runwb2)
```bash
#!/usr/bin/env bash
#SBATCH --job-name=aqwa_wb
#SBATCH --nodes=1
#SBATCH --cpus-per-task=8
#SBATCH --mem=32G
#SBATCH --time=08:00:00
module load ansys/v251
export ANSYSLMD_LICENSE_FILE=1055@license-server
export ANSYSLI_SERVERS=2325@license-server
RUNWB2=/ansys_inc/v251/Framework/bin/Linux64/runwb2
${RUNWB2} -B \
-F "/path/to/project.wbpj" \
-R "/path/to/solve.wbjn"
exit $?
```
Minimal `solve.wbjn` (IronPython 2.7):
```python
SetScriptVersion(Version="0.1.0")
Open(FilePath=r"/path/to/project.wbpj")
system1 = GetSystem(Name="AQW") # Name set by user in WB project
system1.Update(AllDependencies=True)
Save(Overwrite=True)
```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.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
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
label-driven-prompt-generation-architecture
Pattern for building automation scripts that classify GitHub issues into prompt templates using label-based routing and extract contextual data for batch processing
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.