{% extends "base.html" %} {% block title %}Benchmarks — Nullius{% endblock %} {% block crumb %}/ benchmarks{% endblock %} {% block head %}{% endblock %} {% block body %} {% set listed = cat.listed_benchmarks %} {#- a route's name, the same on the filter chips and on the cards' bubbles #} {% set run_labels = {'harbor': 'Harbor', 'standard': 'Nullius'} %} {% set run_names = {'harbor': 'Harbor', 'standard': 'the Nullius standard'} %} {% set count = namespace(datasets=0) %}{% for b in listed %}{% set count.datasets = count.datasets + b.datasets|length %}{% endfor %}
{{ listed|length }} benchmarks · {{ count.datasets }} datasets
Two ways a benchmark runs here. Pick its route, then follow it.
Any agent over ACP, the benchmark's own code as its driver: a standard.json and a driver.py in {{ catalogue_dir }}/benchmarks/<key>/, its controls proven with cli prove. A paper's own scripts run as its Original setup.
The steps: docs/standard.md, "Import by hand", "A benchmark".
In Harbor's registry or Hub: name it, read it from Harbor, check the entry, save.
Add a Harbor benchmarkNo benchmark matches.