integer_compression_codec: stored size anchors are impossible for the documented Varint starter

Abierto
  • ¿Algo no está bien?
#52 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
testing-qa

Línea de trabajo

Read baseline_results.json and scoring_scheme.md, then reproduce the reported starter run with the listed sforge build and judge_local.py commands. Compare the per-dataset encoded sizes with the stored anchors and trace how the scoring calculation uses them. Decide how to handle the scale change while preserving the stated throughput anchors, then verify the starter and top-file scores against the issue's reported ranges.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Task

integer_compression_codec

Claim

The stored size anchors in baseline_results.json can't come from the documented baseline. scoring_scheme.md says the baseline is the Varint starter, and Varint writes at least 8 bits per integer, yet five of eight anchors are below 8 (5.13 on docids) and all eight are below the starter's real size. Each dataset is off by a different factor, 1.23 to 8.23.

Impact

Every score uses these anchors. With the starter's exact sizes, the starter's raw score goes from 0.24-0.25 to 0.83-0.88 (documented 1.0) and our top file from 73.78 to raw 167.38-167.51, which clips on the 0..100 scale, so a fix needs a scale decision.

Evidence and how to reproduce

On community f92857a3, after python -m sforge build --task integer_compression_codec, grade the starter with python3 tools/judge_local.py --task-dir edgebench/tasks/integer_compression_codec --image edgebench.judge.integer_compression_codec:d5de821d0a38 --empty --out result.json and read metrics.per_dataset[].encoded_bytes in the structured result inside log_tail: encoded_bytes * 8 / n is 38.98 on docids, against the stored 5.13, on every run.

Limits

Throughput anchors stay as they are (Known issue 2). All real submissions here come from one agent's two runs.

Lenguaje dominante
Python
Estrellas
474
Forks
20
Merge medio
3 d 6 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ByteDance-Seed/EdgeBench

Todos los issues de ByteDance-Seed/EdgeBench

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.