Show efficiency numbers per task
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- data-visualization
Research direction
Start with web/src/analysis.ts and web/src/components/TaskTable.tsx to see how trial data reaches the task table. Add per-task means for the listed efficiency measures and test their aggregation. Done when the dashboard displays those measures and the aggregation test passes.
Written by the indexing model from the issue text.
Description
Context
The dashboard ignores the efficiency data in each trial (turns, tool calls, tokens, duration, provider wait).
What to do
Add per-task means to the task table or a separate section.
Done when
Efficiency is visible, with a test on the aggregation.
Where to look
web/src/analysis.ts, web/src/components/TaskTable.tsx
New here? Read CONTRIBUTING.md and comment on this issue to say you are taking it.
Generated by Claude Code
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from patsypppe/meridian
-
area: security area: tests size: S tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area: dashboard area: tests good first issue size: XS tests
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: dashboard area: tests good first issue size: S tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area: dashboard area: tests good first issue size: XS tests
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: gate area: tests good first issue size: S tests
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
All issues in patsypppe/meridian
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
neilsh/stunt-reel#220 ·
Maintainers usually reply within 1 day
-
[Issue]: use_fp4_cache is accepted but ignored; the launcher always writes FP8 recordsPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: cli priority: p3 size: S type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
finos/open-resource-broker#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days