Contribute

Everything goes through GitHub issues.

• To add a missing result, use the new result form. Give the instance, the energy as printed, its error bar, the method, and where in the paper it is. A missing field shows as n/a and does not block the row (rules §3).
• To add a missing instance, use the new instance form. For a lattice model, give the Hamiltonian, cluster, boundaries, couplings and sector. For the homogeneous electron gas, give the dimension, cell, electron numbers, rs and twist (rules §12.1). In both cases, give the paper that defines it.
• To correct a row, send its error bar or its cost, or comment on it, open the row on the Table page and click the pencil at its end. It opens the about-a-row form with the row filled in. Rows are corrected in place; git keeps the history.
• If you know an error bar we could not find, tell us. 609 sampled energies on 201 instances are listed without one, because the source we read gives none. They rank like any other row; with an error bar, results that agree within it share a rank (rules §6).
• To object to a row, open an issue on a technical ground, for example a wrong symmetry sector, a misdeclared bound_type or an error bar with no autocorrelation correction. Rules §10 lists the grounds and gives the process.
• To add what a number cost, give the GPU or CPU hours with the device, the parameter count, or the wall-clock time. 488 energies state GPU or CPU hours or a parameter count; the energy-versus-cost figures use them (format). Parameter, sample and iteration counts together, or a DMRG run's sweep schedule, let the site estimate a FLOP count where no hours are stated.