hnerv_qlp#125
Closed
Bucky789 wants to merge 2 commits into
Closed
Conversation
|
Thanks for the submission @Bucky789! 🤏 A maintainer will review your PR shortly. To run the evaluation, a maintainer will trigger the |
Re-optimizes the frozen commaai#1 (PR commaai#112) decoder's per-pair latents by gradient descent against SegNet/PoseNet through the exact inflate chain (fp32 eval/selection), matching the commaai#1's distortion without its 607-byte sidecar. Net -611 bytes -> CPU score 0.190946 vs commaai#1's 0.191126. Decoder weights (PR commaai#95) and FEC6 selector (PR commaai#110) reused bit-for-bit; ctx container from PR commaai#112. Only the latent codes change. archive.zip and report.txt are not checked in (hosted via release, per submission rules). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y93bS67W74mXUySQa39qEz
Eval Results:
|
Collaborator
|
added to leaderboard, congrats |
Author
|
I have emailed the email address mentioned as I'm looking for a Full Stack Engineer job. |
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
submission name:
hnerv_qlp
upload zipped
archive.zipHosted as a release asset (
curl -Lworks, SHA-256 verified):https://github.com/Bucky789/comma_video_compression_challenge/releases/download/hnerv-qlp-v1/archive.zip
SHA-256
ebd513903bd598b4d73d699a11c89600bd11747f27aab26737e518096675b813, 176,525 bytes, single ZIP memberx(ZIP_STORED).report.txt
(
evaluate.pyprints the score to 2 dp as0.19; full precision is0.190946.)does your submission require gpu for evaluation (inflation)?
no — inflate is CPU-only (device pinned to CPU); deps
torch,numpy,constriction.did you include the compression script? and want it to be merged?
yes — the full offline encoder is in
submissions/hnerv_qlp/encoder/(extract → polish → pack). Happy for it to be merged.is this submission competitive or innovative? explain why
Both.
Competitive: CPU score
0.190946vs the current #1 (rhnerv_comma,0.191126) — a margin of-0.000180. Local eval reproduces the #1's published metrics to ~1e-5, so the margin is real (~18x that).rhnerv_commaInnovative: every top submission reuses PR #95's decoder and latents; the only per-pair latent tuning attempted so far is PR #101's sidecar (one dimension, a small fixed step table). This submission generalizes that to quantization-aware gradient descent over all 28 latent dimensions of every pair, decoder frozen, optimized directly against SegNet/PoseNet through the exact inflate chain. The polished latents reach the #1's distortion without its 607-byte sidecar, so the archive is 611 bytes smaller.
additional comments
No decoder training. Decoder weights (PR #95) and the FEC6 selector (PR #110) are reused bit-for-bit; the ctx container is PR #112's, with the latent section re-encoded and the sidecar dropped. One implementation note that mattered: the SegNet distortion is a discrete argmax, so fp16 and fp32 disagree on borderline pixels — selecting latents on an fp16 scorer overfits the GPU and regresses on the CPU axis (an fp16-selected build scored 0.191955). Evaluation and per-pair selection are done in fp32; training stays fp16 for speed. Full lineage and attribution in
submissions/hnerv_qlp/THIRD_PARTY_NOTICES.md(PRs #95/#98/#101/#110/#112).