AgentSkillsCN

BU SCC Ops

当用户提出“在BU SCC上运行”“启动SCC交互式会话”“提交qsub作业”“选择SCC资源”“设置DenseGen CPU资源”“在SCC GPU上运行Evo2”或“在SCC上设置Notify监视器作业”时，应使用此技能。

SKILL.md
--- frontmatter
name: BU SCC Ops
description: This skill should be used when the user asks to "run on BU SCC", "start an interactive SCC session", "submit a qsub job", "pick SCC resources", "set DenseGen CPU resources", "run Evo2 on SCC GPUs", or "set up Notify watcher jobs on SCC".
version: 0.1.0

BU SCC Ops Skill

Use this skill to run dnadesign workloads on BU SCC with explicit scheduler resources, predictable job behavior, and clear Notify wiring.

Scope

Use this skill for:

  • •interactive SCC sessions (qrsh, OnDemand shell)
  • •batch job submission (qsub) for DenseGen, Evo2, and Notify watcher flows
  • •choosing resource requests by workload type
  • •preflight validation commands before long runs

Do not use this skill for:

  • •non-SCC environments
  • •generic local development workflow decisions

Workflow

  1. •Identify workload class first.
  2. •Pick interactive or batch mode.
  3. •Apply resource profile from references/resource-profiles.md.
  4. •Use template command from docs/bu-scc/agent-cheatsheet.md.
  5. •Run preflight checks before expensive jobs.
  6. •Submit and monitor with qstat + log tail.
  7. •Keep interactive/OnDemand usage within BU policy limits for high-resource sessions.

Workload classes

  • •DenseGen solver runs:
    • •CPU only
    • •request -pe omp <N> and -l mem_per_core=<...>
    • •ensure densegen.solver.threads <= N
  • •Notify watcher:
    • •lightweight CPU watcher
    • •long walltime, minimal slots
  • •Evo2 inference:
    • •GPU required (-l gpus=1 -l gpu_c=8.9)
    • •load CUDA/GCC modules in script
  • •large transfer/prefetch:
    • •transfer-node queue (-l download)
    • •no compute-heavy workloads

Required checks

Before submitting DenseGen jobs:

  • •uv run dense validate-config --probe-solver -c <config.yaml>
  • •uv run dense inspect config --probe-solver -c <config.yaml>

Before relying on Notify:

  • •confirm events source is USR .events.log
  • •do not wire Notify to DenseGen outputs/meta/events.jsonl
  • •run resolver preflight: uv run notify setup resolve-events --tool <tool> --config <config.yaml>
  • •ensure events are schema-valid (must include event_version)

Command references

Load only the needed references:

  • •docs/bu-scc/agent-cheatsheet.md for copy/paste commands
  • •docs/bu-scc/quickstart.md for bootstrap flow
  • •docs/bu-scc/install.md for environment bootstrap details
  • •docs/bu-scc/batch-notify.md for runbook details
  • •docs/bu-scc/jobs/README.md for template-specific submits
  • •references/resource-profiles.md for workload-to-resource defaults