Contact
Two ways in, and what to include so a reply is useful.
[email protected] reaches the person who runs the experiments. There is no contact form on this site, because a static site has no server to submit one to, and adding a third party form would mean adding a third party script.
GitHub
Anything involving a workflow file, an experiment record or a reproduction failure is better as an issue on the experiments repository. The files are there, so a thread can point at the exact line that differs from your setup.
What to include
Reports about a measurement need the configuration to be actionable. Without these, the most likely answer is a request for them:
- GPU or SoC, and VRAM or unified memory in GB.
- Operating system and driver version.
- Runtime version, model build and quantization.
- The exact error text, copied rather than paraphrased.
- The article and the step it happened on.
What gets a reply
Corrections, reproduction failures and questions about how a measurement was taken get answered. Requests to test a specific model or hardware combination are read and go into the backlog, though hardware here is limited to two machines, so most of those cannot be promised.
Sponsorship offers, guest posts, link exchanges and requests to place affiliate links in existing articles are declined. The reasons are in the editorial policy.