icfpc-aws-compute

Runs CPU-heavy ICFPC explorations as AWS Batch Spot array jobs and downloads results.

1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-aws-compute-d-experts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: icfpc-aws-compute
Source: https://github.com/d-experts/public-icfpc-2026/tree/main/member-18/.agents/skills/icfpc-aws-compute
Command: npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-aws-compute-d-experts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large ICFP Contest searches—layout exploration, module synthesis, batch public-case checks—are too slow or memory-heavy for one local machine. This Skill snapshots the repository working tree to S3 and runs the work as parallel AWS Batch EC2 Spot array jobs, then collects every per-index artifact. ## Core Features & Use Cases - Environment health checks: Verifies the CloudFormation stack, compute environment, job queue, and job definition are healthy before submitting work. - Cost and sharding guidance: Estimates vCPU-hours and USD cost, and decides whether work should run locally or as an array job with per-shard vCPU/memory sizing. - Job lifecycle management: Submits array jobs, monitors status, waits for completion, downloads complete per-index results, and cancels only your own jobs. - Use Case: You have 128 independent layout-search seeds that would take hours locally. The Skill bundles them into one array job of 128 single-vCPU children, runs them on Spot capacity, and downloads all 128 result directories. ## Quick Start Use the icfpc-aws-compute skill to run this layout search as an AWS Batch Spot array job and download all results.

Frequently Asked Questions about icfpc-aws-compute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a large parallel search on AWS Batch Spot instances?▼

Snapshot the repository working tree to S3 and submit an AWS Batch array job where each independent seed maps to an array index. Use $ICFPC_ARRAY_INDEX inside the command and write outputs to $ICFPC_OUTPUT_DIR, then wait and download all per-index results.

When should I run ICFPC searches locally instead of on AWS Batch?▼

Run locally when the estimated completion is under 15 minutes, total work is under 1 vCPU-hour, or there are few independent shards. AWS Batch is recommended with 8 or more independent single-thread shards and local estimates over 30 minutes.

How do I estimate AWS Spot cost for a Batch array job?▼

Compute vCPU-hours as max(8, array × vcpus) times estimated child hours, then multiply by 0.022 USD per vCPU-hour and a 1.2 safety factor. For jobs over 100 vCPU-hours, recheck current Spot prices with describe-spot-price-history before submitting.

Why is my AWS Batch job stuck in PENDING or RUNNABLE state?▼

PENDING or RUNNABLE lasting several minutes is normal during scale-from-zero, since the compute environment starts at zero desired vCPUs and takes about three minutes to provision workers. Do not resubmit the same job while waiting.

Can AWS Batch jobs update the local best store or submit solutions?▼

No. Remote commands must never modify the best store or submission queue, and judge invocations must use --no-save --no-submit. Official submission happens only locally after results are downloaded and verified.