Skip to content

2026-04-27-trade-offs-in-llm-compute-for-reasoning-intensive-information-retrieval#174

Open
nilesh2797 wants to merge 24 commits intoiclr-blogposts:mainfrom
nilesh2797:main
Open

2026-04-27-trade-offs-in-llm-compute-for-reasoning-intensive-information-retrieval#174
nilesh2797 wants to merge 24 commits intoiclr-blogposts:mainfrom
nilesh2797:main

Conversation

@nilesh2797
Copy link
Copy Markdown
Contributor

OpenReview Submission Thread

Checklist before opening a PR

  • I am opening a pull request against the main branch of the 2026 repo.

  • My post and all associated references to it are all lowercase, i.e

      2026-04-27-Sample-Test.md               -> 2026-04-27-sample-test.md
      assets/img/2026-04-27-Sample-Test/ 	-> assets/img/2026-04-27-sample-test/
    
  • The title of my PR is exactly the name of my markdown file

    • i.e. _posts/2026-04-27-[submission-name].md would require a PR name 2026-04-27-[submission-name]
  • I have anonymized my post: my author's list is Anonymous, and there is no potential
    content which can reveal my/my collaborators identities.

  • My post matches the formatting requirements, including (but not limited to):

    • I have ONLY MODIFIED files in the following locations (failure to do so will result in
      your PR automatically being closed!):
      • a Markdown (or HTML) file in _posts/ with the format _posts/2026-04-27-[submission-name].md (or .html)
      • static image assets added to assets/img/2026-04-27-[submission-name]/
      • interactive HTML figures added to assets/html/2026-04-27-[submission-name]/
      • citations in a bibtex file in assets/bibliography/2026-04-27-[submission-name].bib
    • I have a short 2-3 sentence abstract in the description field of my front-matter
    • I have a table of contents, formatted using the toc field of my front-matter
    • My bibliography is correctly formatted, using a .bibtex file as per the sample post

Any other comments

@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 8, 2025

⚠️ We have detected a problem with your submission! ⚠️

You can only add/change/remove files related to your post, i.e. files that match one of these patterns: <_posts/SLUG.md, assets/img/SLUG/..., assets/html/SLUG/..., assets/bibliography/SLUG.bib>. But we found that you changed the following: <cost_vs_ndcg_model1.html>. Also, make sure your PR's title (2026-04-27-trade-offs-in-llm-compute-for-reasoning-intensive-information-retrieval) matches your post's slug!

Please make the aforementioned changes and re-submit :)

@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 8, 2025

⚠️ We have detected a problem with your submission! ⚠️

You can only add/change/remove files related to your post, i.e. files that match one of these patterns: <_posts/SLUG.md, assets/img/SLUG/..., assets/html/SLUG/..., assets/bibliography/SLUG.bib>. But we found that you changed the following: <_posts/2026-04-27-distill-example.md>. Also, make sure your PR's title (2026-04-27-trade-offs-in-llm-compute-for-reasoning-intensive-information-retrieval) matches your post's slug!

Please make the aforementioned changes and re-submit :)

@busycalibrating busycalibrating added accepted PR matches an accepted blog post manual accept labels Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted PR matches an accepted blog post manual accept

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants