Agentic FPGA Backend Optimization Competition
- Home
- Contest Details
- Optimization Example
- Eval. Environment
- Alpha Submission
- Beta Submission
- Final Submission
- Benchmarks
- Scoring Criteria
- FAQ
- GitHub Repo
- Contact
Sponsored by
; contest hosted at the FPL'26 conference.
Hosted on GitHub Pages using the Dinky theme
Alpha Submission
In order to ensure that the contest environment is able to support all entries ahead of the beta and final submission deadline, a mandatory step for continued participation in the contest is the submission of an early "alpha" release. The performance of this alpha submission will have zero effect on the final submission score; instead, the organizers will endeavour to work with contestants to ensure that the runtime environment is as desired. Contestants will receive private feedback from the organizers assessing the performance of just their submission on the released benchmark suite (plus a hidden benchmark) when run on the contest runtime environment.
Key Details
- Alpha submission is mandatory for continued participation in the contest
- Performance of alpha submissions will be shared privately with contestants and will not impact the final score
- Alpha submissions will be evaluated on the contest runtime environment
Submission Format
Contestants are required to submit an archive containing a clone of the contest
repository which has been modified to run their submission. Zip files are
preferred, but .tar.gz archives are also accepted. Submission archives are
limited to a maximum size of 4 GB (2^32 bytes). The following code block
illustrates the commands that will be run on the verification instance to
evaluate a submission:
unzip submission.zip # or: tar -xzf submission.tar.gz
cd fpl26_optimization_contest
make setup
make run_optimizer DCP=benchmark1.dcp
make run_optimizer DCP=benchmark2.dcp
make run_optimizer DCP=...
The make setup target is one of the initial steps that teams can update to
install any additional packages or perform any other one-time preparation
required before their submission is run. The make run_optimizer target
will then be invoked once per benchmark DCP in the evaluation suite.
The exact instructions for uploading the submission archive will be emailed directly to teams.
Closed-Source Submissions
While contestants are strongly encouraged to open-source their solutions at the conclusion of the contest, there is no requirement to do so. In such cases, it is still necessary to use the flow described above to produce a binary only submission.