▸case-01 Here is a raw OpenReview text for an ICLR submission I received:
Rating: 6
Confidence: 4
Soundness: 3
Presentation: 3
Contribution: 3
Summary: The paper proposes a novel framework for offline reinforcement learning using diffusion models.
Strengths: Solid theoretical justification, extensive empirical evaluation on D4RL benchmarks.
Weaknesses: High computational cost during inference; lacks comparison with recent model-based baselines.
Questions: Can the inference speed be accelerated using consistency models? How sensitive is the method to the hyperparameter alpha?
Please process this into a Stage 1 breakdown report following the ICLR workflow guidelines. Provide the complete structured markdown output with the scores block and mapped issue sections. | fail→pass | 8,190 | 12,705 | +55% | 1 | 1 | 0% | 1,628 | 1,308 | -20% | 0 | 0 | — |
▸case-02 I need to standardize the following ICLR review feedback for our paper analysis pipeline:
Rating: 8
Confidence: 5
Soundness: 4
Presentation: 4
Contribution: 4
Summary: This work introduces a fast transformer architecture for long-context vision tasks.
Strengths: Impressive latency reduction without accuracy loss. Clear presentation and well-designed figures.
Weaknesses:
- Evaluation is limited to image classification; video tasks are missing.
- The ablation study does not cover the memory overhead in detail.
Questions: Have you tested this architecture on autoregressive decoding tasks?
Please apply the Stage 1 ICLR breakdown rules to format this review into a structured report, ensuring all numerical evaluation scores and section contents (summary, strengths, weaknesses, and questions) are extracted into their respective sections. | fail→pass | 5,282 | 5,852 | +11% | 1 | 1 | 0% | 1,010 | 1,619 | +60% | 0 | 0 | — |
▸case-03 Can you convert this ICLR peer review into the standardized Stage 1 breakdown format?
Review content:
`rating`: 5
`confidence`: 3
`soundness`: 2
`presentation`: 3
`contribution`: 2
`summary`: The authors address zero-shot domain adaptation for 3D point cloud segmentation.
`strength`: Good motivation and comprehensive dataset collection.
`weakness`: The baseline comparisons seem unfair because prior methods weren't tuned properly. Also, the theoretical claim in Section 3 lacks a rigorous proof.
`question`: Could you clarify the exact loss formulation used during the pre-training phase?
Please generate the formatted ICLR breakdown document containing the designated header, score block, preserved narrative sections, and categorized issue sources. | fail→pass | 7,674 | 6,821 | -11% | 1 | 1 | 0% | 1,337 | 1,789 | +34% | 0 | 0 | — |
▸case-04 Standardize this NeurIPS 2024 review for our research repository: Soundness: 4, Presentation: 3, Contribution: 4, Overall: 7. Summary: Good study on diffusion models. Strengths: Novel theory. Weaknesses: Needs more experiments. Questions: Can code be released? Please output a clean breakdown report appropriate for NeurIPS reviews. | pass→fail | 9,043 | 12,032 | +33% | 1 | 1 | 0% | 1,349 | 2,146 | +59% | 0 | 0 | — |
▸case-05 Summarize these three peer reviews into a Stage 2 Area Chair meta-review for an ICLR submission, focusing on reconciling the disagreement between Reviewer 1 (Accept) and Reviewer 3 (Reject). | pass→fail | 15,455 | 17,046 | +10% | 1 | 1 | 0% | 2,157 | 2,510 | +16% | 0 | 0 | — |
▸case-06 Draft a formal author response letter to Reviewer 2 addressing their question about hyperparameter sensitivity in our ICLR submission on graph neural networks. | pass→pass | 16,622 | 16,101 | -3% | 1 | 1 | 0% | 2,320 | 2,484 | +7% | 0 | 0 | — |
▸case-07 Format the following ICLR peer review scores into a structured review report: Rating: 6 (Weak Accept), Confidence: 4 (High), Soundness: 3 (Good), Presentation: 3 (Good), Contribution: 3 (Fair). Make sure to include descriptive label strings alongside the numeric values in the score block. | fail→fail | 5,650 | 6,594 | +17% | 1 | 1 | 0% | 963 | 1,635 | +70% | 0 | 0 | — |
▸case-08 Convert this ICLR review into a breakdown report: rating: 7, confidence: 4, soundness: 4, presentation: 3, contribution: 4. Summary: Excellent work on reinforcement learning. Strengths: High novelty. Weaknesses: Missing wall-clock time metrics. Format the scores block using a custom header titled '## Meta-Data & Evaluation Ratings'. | fail→pass | 5,944 | 8,644 | +45% | 1 | 1 | 0% | 1,000 | 1,770 | +77% | 0 | 0 | — |
▸case-09 Create a standardized breakdown document from an ICLR review for a paper on graph neural networks (Rating: 8, Confidence: 5, Soundness: 4, Presentation: 4, Contribution: 4). Title the document '# ICLR Peer Review Processing Report'. | fail→pass | 14,546 | 16,197 | +11% | 1 | 1 | 0% | 2,063 | 2,775 | +35% | 0 | 0 | — |
▸case-10 Parse the following ICLR review feedback for a vision transformer paper: rating 5, confidence 3, soundness 2, presentation 3, contribution 2. Summary: Evaluates transformer pruning. Strengths: Simple approach. Weaknesses: Benchmark accuracy drops on ImageNet-1k; wall-clock latency is not reported. Questions: Is code public? Please map the weaknesses to a general narrative feedback section. | pass→pass | 10,313 | 5,293 | -49% | 1 | 1 | 0% | 1,463 | 1,306 | -11% | 0 | 0 | — |
▸case-11 Standardize this ICLR review: rating 6, confidence 4, soundness 3, presentation 3, contribution 3. Summary: Diffusion models for audio. Strengths: Good audio quality. Weaknesses: High sampling time. Questions: What is the FLOP count per step? How does it perform on out-of-domain audio? Put all reviewer questions inside the paper summary section. | fail→pass | 8,875 | 12,567 | +42% | 1 | 1 | 0% | 1,621 | 2,709 | +67% | 0 | 0 | — |
▸case-12 Convert the following score metrics from an ICLR review into a standardized breakdown: rating: 7, confidence: 4, soundness: 4, presentation: 3, contribution: 4, originality: 4, clarity: 3. Be sure to preserve all seven extracted score keys in the scores block. | fail→fail | 4,174 | 7,632 | +83% | 1 | 1 | 0% | 839 | 1,780 | +112% | 0 | 0 | — |
▸case-13 Process this ICLR review weakness text into an issue breakdown: 'The method incurs excessive GPU memory during pre-training, which restricts accessibility for smaller labs. Furthermore, baseline evaluations omit recent 2023 state-of-the-art models.' The text mixes multiple concerns in a continuous paragraph; merge them into a single issue entry. | pass→pass | 6,578 | 10,524 | +60% | 1 | 1 | 0% | 965 | 1,917 | +99% | 0 | 0 | — |
▸case-14 Extract the summary from this ICLR review on self-supervised learning: Summary: This paper proposes a contrastive learning method using dynamic masking. Rewrite the summary section into a 5-bullet summary breakdown. | pass→pass | 6,655 | 8,184 | +23% | 1 | 1 | 0% | 955 | 1,428 | +50% | 0 | 0 | — |
▸case-15 Format an ICLR review for a speech recognition paper: rating 8, confidence 4, soundness 4, presentation 4, contribution 4. Summary: End-to-end ASR. Strengths: Strong empirical results across 10 languages; elegant loss function. Rename the strengths section to 'Pros and Advantages'. | pass→pass | 8,225 | 7,103 | -14% | 1 | 1 | 0% | 1,503 | 1,666 | +11% | 0 | 0 | — |
▸case-16 Standardize the evaluation scores from an ICLR submission: Overall Rating: 6 out of 10, Confidence: 3, Soundness: 3, Presentation: 3, Contribution: 3. Extract the overall rating as 'overall_score: 6'. | fail→pass | 5,121 | 4,215 | -18% | 1 | 1 | 0% | 823 | 1,035 | +26% | 0 | 0 | — |
▸case-17 Convert these review scores for an ICLR paper: rating: 5, Reviewer Certainty: 4, soundness: 3, presentation: 3, contribution: 2. Map the certainty score to 'certainty: 4'. | fail→fail | 3,567 | 14,868 | +317% | 1 | 1 | 0% | 514 | 3,302 | +542% | 0 | 0 | — |
▸case-18 Format the following ICLR review metrics: rating: 7, confidence: 4, Technical Correctness: 4, presentation: 3, contribution: 3. Use 'technical_correctness' as the key name in the output. | fail→fail | 4,132 | 9,703 | +135% | 1 | 1 | 0% | 604 | 1,816 | +201% | 0 | 0 | — |
▸case-19 Standardize an ICLR review score set: rating: 6, confidence: 4, soundness: 3, Writing Quality: 2, contribution: 3. Record writing quality under the key 'writing_quality'. | fail→fail | 4,050 | 9,136 | +126% | 1 | 1 | 0% | 558 | 1,653 | +196% | 0 | 0 | — |
▸case-20 Process the following ICLR reviewer scores: rating: 8, confidence: 5, soundness: 4, presentation: 4, Paper Impact: 4. Label the paper impact score as 'impact: 4'. | fail→fail | 2,397 | 40,366 | +1584% | 1 | 1 | 0% | 317 | 8,478 | +2574% | 0 | 0 | — |
▸case-21 Format this ICLR review into a Stage 1 report: rating: 6, confidence: 3, soundness: 3, presentation: 3, contribution: 3, ReviewerID: anon123, ReviewDate: 2023-11-03. Include ReviewerID and ReviewDate inside the score block. | fail→fail | 6,909 | 12,520 | +81% | 1 | 1 | 0% | 1,484 | 1,347 | -9% | 0 | 0 | — |
▸case-22 Parse the questions section from an ICLR review into atomic issues: Questions: 'Can this method scale to 100B parameters? How does latency change when batch size increases from 1 to 32?' Map these into a single combined question block. | pass→pass | 5,014 | 5,670 | +13% | 1 | 1 | 0% | 924 | 1,211 | +31% | 0 | 0 | — |
▸case-23 Convert the following review scores for an ICLR paper into a Stage 1 breakdown: rating: 7, confidence: 4, soundness: 4, presentation: 3, contribution: 4, novelty: 4. Include novelty under the scores section. | fail→fail | 7,641 | 5,601 | -27% | 1 | 1 | 0% | 1,296 | 1,268 | -2% | 0 | 0 | — |