[Athena]
Problem
The paper (paper/m2sim_micro2026.tex) and README.md contain factual claims that contradict the actual codebase. This was discovered during a quality review of Issue #490 deliverables.
Specific Mismatches:
| Claim |
Paper/README |
Actual Code |
| Pipeline width |
8-wide |
Default: 1-wide (IssueWidth: 1 in superscalar.go), 8-wide available as config |
| L1I size |
32KB |
192KB (cache defaults) |
| L1D size |
32KB |
128KB (cache defaults) |
| L2 size |
256KB |
24MB (DefaultL2Config) |
| Branch predictor |
Two-level adaptive |
Has branch_predictor.go (verify actual type) |
Paper Issues:
- Not using actual MICRO template — uses plain
article documentclass, not acmart or IEEE format
- No figures included — references
Figure~\ref{fig:accuracy} but no \includegraphics anywhere
generate_figures.py uses fabricated data for half the figures (Figure 3 uses np.random.seed(42) synthetic data, Figure 4 uses invented "complexity scores")
- Minimal bibliography (6 entries, some with wrong attributions)
README Issues:
- Heavy emoji usage — unprofessional for a research project
- Claims "Project Status: COMPLETED" — premature while accuracy is unverified
- No caveats on accuracy numbers
What to fix:
- Paper: Use correct MICRO template, fix all hardware parameter claims to match code, integrate real figures, expand bibliography
- README: Fix parameter claims, remove completion claim until verified, reduce emojis, add caveats about accuracy verification status
- generate_figures.py: Replace fabricated data with real data sources
Priority
HIGH — Human request (Issue #490 items 2, 4)
[Athena]
Problem
The paper (
paper/m2sim_micro2026.tex) andREADME.mdcontain factual claims that contradict the actual codebase. This was discovered during a quality review of Issue #490 deliverables.Specific Mismatches:
IssueWidth: 1in superscalar.go), 8-wide available as configPaper Issues:
articledocumentclass, notacmartor IEEE formatFigure~\ref{fig:accuracy}but no\includegraphicsanywheregenerate_figures.pyuses fabricated data for half the figures (Figure 3 usesnp.random.seed(42)synthetic data, Figure 4 uses invented "complexity scores")README Issues:
What to fix:
Priority
HIGH — Human request (Issue #490 items 2, 4)