When submitting an estimator that creates intermediate arrays larger than ~100 MB, the grader raises:
ValueError: result array too large: 268435456 bytes exceeds 104857600 byte limit
This originates from flopscope/_remote_array.py on the evaluation server — a module that doesn’t exist in the local flopscope installation, so the limit is invisible during local development.
After checking the starter kit docs, whestbench source, and the challenge page, I couldn’t find this constraint documented anywhere. The only documented resource limits I found are:
- FLOP budget: 272B FLOPs
- Submission tarball: 50 MiB
- Run timeout: 60s
Questions:
- Is the 100 MB per-result-array cap intentional and fixed?
- Could it be added to the docs, so participants can design their chunking strategy accordingly?