Skip to content

fix: resolve issues #4 (quality_tier unknown) and #5 (quick-start httpx)#8

Open
Sahil170595 wants to merge 1 commit into
fix/0.6.1-deps-httpxfrom
fix/0.6.1-issues-4-5
Open

fix: resolve issues #4 (quality_tier unknown) and #5 (quick-start httpx)#8
Sahil170595 wants to merge 1 commit into
fix/0.6.1-deps-httpxfrom
fix/0.6.1-issues-4-5

Conversation

@Sahil170595

Copy link
Copy Markdown
Owner

Closes #4. Closes #5.

Stacked on #7 (the 0.6.1 branch) — base is fix/0.6.1-deps-httpx, so this diff shows only the issue fixes. It auto-retargets to main once #7 merges.

#4quality_tier always unknown for llama3.1-8b

Confirmed the report: llama3.1-8b has 6 quantized quality entries but no FP16 baseline and no |FP16 lookup key, and it's the sole llama3.1-family member, so the family fallback finds nothing → unknown on every config.

Why the reporter's suggested fix (add the measured FP16 baseline) is impossible: TR125 source states FP16 for this model was never measured — 16 GB exceeds the RTX 4080 — and the research used Q8_0 as the baseline instead (experiments/research/tr125/phase2/analyze.py:15, generate_report.py:1005). Fabricating an FP16 value would break provenance.

Fix (honest, mirrors TR125): when no FP16 baseline exists, quality_tier anchors to the model's highest-precision measured quant (Q8_0). No data invented.

Verified — chimeraforge plan --model-size 8b --hardware "RTX 4090 24GB" --request-rate 2.0 --json (the issue's exact command):

before after
quality_tier unknown (all 15 configs) negligible / acceptable

#5 — quick-start agent demo fails with ModuleNotFoundError: httpx

Root cause is subtler than "httpx missing from deps": docs/quick_start.md told users pip install -r requirements.txt, but requirements.txt is a comment-only stub (deps live in pyproject.toml), so it installs nothing — and the demo hard-imports httpx. Fixed the doc to pip install -e ".[bench]" (provides httpx) and corrected the your-org placeholder clone URL.

Note on PR #6: it adds httpx to pyproject.toml core deps. That doesn't fix this repro (which uses requirements.txt + the harness, not the chimeraforge package) and would force httpx on every plan-only offline user. The clean-error path for the CLI is handled in #7; this handles the quick-start/harness path. Recommend closing #6 as superseded.

Verification

  • 487 tests pass (+1 regression: llama3.1-8b tier is never unknown); src/ lint clean.

#4: quality_tier returned "unknown" for llama3.1-8b on every config -- its FP16
was never measured (16GB exceeds the RTX 4080), so it has no FP16 baseline and
is the only member of its family (family fallback finds nothing). TR125 handled
this by using Q8_0 as the baseline; quality_tier now mirrors that, anchoring to
the model's highest-precision measured quant when no FP16 baseline exists. No
fabricated data -- the Q8_0 baseline is the documented TR125 methodology.
Verified: `plan --model-size 8b --json` now reports negligible/acceptable tiers
instead of unknown.

#5: docs/quick_start.md installed deps via `pip install -r requirements.txt`,
but requirements.txt is a comment-only stub (deps live in pyproject), so it
installed nothing and the agent demo failed with `ModuleNotFoundError: httpx`.
Switched to `pip install -e ".[bench]"` (provides httpx) and pointed the clone
URL at the real repo (was `your-org` placeholder).

487 tests pass (+1 regression); src/ lint clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant