orcawave-qtf-analysis-when-to-use-full-qtf-vs-newman
Sub-skill of orcawave-qtf-analysis: When to Use Full QTF vs Newman (+2).
Best use case
orcawave-qtf-analysis-when-to-use-full-qtf-vs-newman is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of orcawave-qtf-analysis: When to Use Full QTF vs Newman (+2).
Teams using orcawave-qtf-analysis-when-to-use-full-qtf-vs-newman 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/when-to-use-full-qtf-vs-newman/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How orcawave-qtf-analysis-when-to-use-full-qtf-vs-newman Compares
| Feature / Agent | orcawave-qtf-analysis-when-to-use-full-qtf-vs-newman | 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 orcawave-qtf-analysis: When to Use Full QTF vs Newman (+2).
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
# When to Use Full QTF vs Newman (+2)
## When to Use Full QTF vs Newman
| Scenario | Recommendation |
|----------|----------------|
| Initial design | Newman approximation |
| Mooring design | Full QTF |
| Shallow water (d < 100m) | Full QTF required |
| Deep water (d > 300m) | Newman often sufficient |
| Bi-directional seas | Full QTF |
| Long-crested seas | Newman acceptable |
| SPM/turret systems | Full QTF |
## Computational Considerations
1. **Frequency Resolution**: Use 20-30 frequencies minimum for accurate QTF
2. **Heading Pairs**: Exploit symmetry to reduce computation
3. **Memory**: Full QTF matrices can be large; consider frequency range
4. **Validation**: Compare Newman vs Full for at least one condition
5. **Mesh Quality**: QTF more sensitive to mesh than first-order
## Integration with Mooring Analysis
```python
from digitalmodel.orcawave.qtf import QTFMooringIntegration
# Prepare QTF for mooring analysis
integration = QTFMooringIntegration()
# Load QTF results
integration.load_qtf("results/qtf/fpso_full.yml")
# Convert to mooring analysis format
integration.export_for_mooring_analysis(
output_file="mooring/qtf_loading.yml",
format="OrcaFlex",
include_mean_drift=True,
include_slow_drift=True,
sea_state={
"hs": 4.0,
"tp": 10.0,
"gamma": 3.3
}
)
```Related Skills
mnt-analysis-cleanup
Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.
digitalmodel-orcawave-orcaflex-proof-workflows
Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
digitalmodel-orcawave-orcaflex-workflow
Current-state workflow for navigating and extending digitalmodel OrcaWave/OrcaFlex capabilities across code, tests, issues, queue tooling, and licensed-machine boundaries.
orcawave-orcaflex-semantic-proof-wave-closeout
Close out an OrcaWave/OrcaFlex semantic-proof wave after a PR merges, split unrelated CI blockers, and seed the next semantic-proof issue wave without duplicating existing issues.
full-branch-cleanup-and-worktree-hygiene
Track all dirty/untracked workspace-hub changes, merge stale branches into main, clean remote/local branches, and remove stale worktrees while preserving tracked nested gitlinks.
repo-architecture-analysis
Scan a Python repo's package structure, count classes/functions, classify module maturity (PRODUCTION/DEVELOPMENT/SKELETON/GAP), and generate architecture reports with Mermaid diagrams. Use when asked to analyze codebase structure, find untested packages, or assess module maturity.
viv-analysis
Assess vortex-induced vibration (VIV) for risers and tubular members with natural frequency and safety factor calculations. Use for VIV susceptibility analysis, natural frequency calculation, vortex shedding assessment, and tubular member fatigue from VIV.
structural-analysis
Structural analysis for marine and offshore structures per DNV/API/ISO codes. Use when performing ULS/ALS limit state checks, column buckling, beam deflection, tubular joint capacity (DNV-RP-C203), or stiffened panel analysis. Covers section properties, combined loading, and ALS dented pipe assessment.
signal-analysis
Perform signal processing, rainflow cycle counting, and spectral analysis for fatigue and time series data. Use for analyzing stress time histories, computing FFT/PSD, extracting fatigue cycles (ASTM E1049-85), and batch processing OrcaFlex signals.
orcawave-to-orcaflex
Integration specialist for converting OrcaWave diffraction results to OrcaFlex vessel types. Handles hydrodynamic database generation, RAO import, viscous damping addition, and coordinate system transformations.
orcawave-qtf-analysis
Second-order wave force QTF computation in OrcaWave. Use when computing mean drift forces, difference-frequency or sum-frequency QTFs, slow-drift response, or applying Newman approximation for offshore structures.