feat(cryotank): 水素タンク FEM 生成の着手 (DOE + Abaqus 雛形)

[keisuke58]

概要

水素タンク SHM ラインのコード着手（設計メモ docs/HYDROGEN_TANK_SHM.md の M1 準備）。Abaqus はクラスタ実行のため、この環境で検証できる部分（DOE 生成・解析プランの dry-run）を実装し、Abaqus 依存の FEM 本体は雛形＋TODO にしています。

追加/変更

• src/generate_cryotank_doe.py（新規）— LHS ベースの DOE 生成器（Abaqus 非依存）
  • 欠陥タイプ: healthy / weld_flaw / microcrack / insulation_debond
  • 動作点: 温度（20 K / 293 K）・内圧、位置・サイズ tier、溶接欠陥は溶接線上に配置
  • フェアリング DOE と同じ JSON スキーマ（samples[].defect_params）
• src/generate_cryotank_dataset.py（新規）— Abaqus CAE 雛形
  • Abaqus import をガードし、--dry-run で非 Abaqus 環境でも解析プラン（幾何 / 極低温 Al-Li 材料 / 内圧+熱応力 / 欠陥モデル）を出力
  • 極低温での材料物性シフト（E/降伏/CTE）を関数化（design assumption 明記）
  • FEM 本体（sector part・材料・荷重・欠陥・メッシュ・Job）は M1/M2 TODO（generate_fairing_dataset.py / generate_cohesive_fairing.py / generate_czm_sector12.py を再利用）
• tests/test_cryotank_doe.py（新規）— スモークテスト 4 件（DOE 生成・境界・healthy・dry-run プラン）
• docs/HYDROGEN_TANK_SHM.md — §7/§9 を着手済みコードに合わせ更新

検証（この環境で実行）

• py_compile OK、generate_cryotank_doe.py（1件・100件）生成 OK
• generate_cryotank_dataset.py --dry-run で極低温プラン出力 OK（E が RT 比で増加、ΔK<0 を確認）
• pytest tests/test_cryotank_doe.py → 4 passed
• CI（CPU torch + core deps）でも通る想定

次段

Abaqus 雛形の M1/M2 TODO（sector part・材料割当・内圧+熱・欠陥挿入）を実装 → クラスタで healthy 1件生成 → グラフ目視（M1）。

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@keisuke58, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 84bd34e8-6056-45c2-9953-d2564d16042b

📥 Commits

Reviewing files that changed from the base of the PR and between 6f091a4 and 17510c8.

📒 Files selected for processing (4)

• docs/HYDROGEN_TANK_SHM.md
• src/generate_cryotank_dataset.py
• src/generate_cryotank_doe.py
• tests/test_cryotank_doe.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.