Skip to content

docs: disclose frozen OpticStudio Student integration limitation #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Charlie-Wang-03 merged 1 commit into from
Oct 12, 2026
Merged

docs: disclose frozen OpticStudio Student integration limitation #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/known-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@
- Electromagnetic transient, Rocky two-way coupling, and selected SPH modes retain explicit `BLOCKED` states tied to documented edition/API limits.
- Several legacy cases are `NOT_RUN` because no unambiguous suite evidence could be attributed during migration.

## Evaluated integration — OpticStudio Student (not in catalog)

In a 2026 R1 Ansys Student environment, OpticStudio 26.1 was discovered and its normal process-start canary passed. The official optiSLang batch runtime created the OpticStudio integration node and a headless project, but model loading stopped when the current Student license rejected the node's required ZOS-API access. No OpticStudio optical calculation or physics validation was executed. Optics is not one of the implemented 11 domains or 134 catalog cases. This exploration is frozen: the project does not claim a runnable OpticStudio Student automation integration.

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Add durable evidence for the OpticStudio outcome

This paragraph publishes concrete execution outcomes—successful discovery and canary, project creation, and a license rejection—but a repo-wide search for OpticStudio, ZOS-API, and optiSLang finds no manifest or result artifact supporting them; this paragraph is the only relevant record. Because the integration is deliberately excluded from the catalog, the existing static gates still pass and readers cannot verify this frozen blocked outcome from the repository's sources of truth. Add a sanitized, project-relative result record or remove the run-specific claims before publication.

AGENTS.md reference: AGENTS.md:L3-L3

Useful? React with 👍 / 👎.


## Catalog release qualifications

These outcomes are intentionally published as limitations. They do not become `PASS` during release preparation. Publication is blocked only if the evidence is missing or inconsistent, a declared threshold is weakened, the current/historical meaning is misleading, the limitation is undisclosed, or privacy/proprietary-content gates fail.
Expand Down
Loading