Who it is forA maintainer or research engineer who wants to extend the dataset to new venues or check how the gallery was built.
The problemAdding a new conference or auditing the selection rules requires running the full pipeline from proceedings index to manual review.
The outcomeA regenerated figures.json and figures.js built from a candidate pool, following the documented pipeline order.
What you need first
- A modern web browser
- Git and Python 3 if you want to run the gallery locally
- An API key from a model provider you choose, only for FigureForge generation
- The title and abstract of your paper, or one sentence describing its input, method and output
Steps
- Run
pip install -r requirements.txt - Run
python scripts/build_pool.pyto build the ICLR, ICML and NeurIPS candidate pool - Run
python scripts/extract_all.pyto download PDFs and crop Figure 1, thenpython scripts/score_select.py 980to score and select - Run
python scripts/assemble_gallery.py 1000to generate figures.json and figures.js - Run
python scripts/enum_sheets.py iclrand review the contact sheets page by page, as docs/METHODOLOGY.md describes
Prompt for your agent
In a clone of qwdwqfwq/topconf-paper-figure-gallery, install requirements and run the build_pool, extract_all and score_select scripts in that order for a dry run on <venue>. Expected output: a selection count printed by score_select. Verify the count is non-zero and that no figure is copied from the gallery without its source link.
Caveat. The pipeline downloads publisher PDFs, and the README says the images belong to their authors and publishers, so check the image policy before publishing any output.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page