Download numerical weather prediction datasets (HRRR, RAP, GFS, IFS, etc.) from NOMADS, NODD partners (Amazon, Google, Microsoft), ECMWF open data, and the University of Utah Pando Archive System.
C-Rank Grade: B (Solid) - 57/100
External PR Merge Rate: 100%
Response Time: 2h
First Timer Success: 100%
blaylockbk/Herbie has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in blaylockbk/Herbie respond to incoming external pull requests in approximately 2.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.7 places blaylockbk/Herbie in the B tier.
The external contributor pull request merge rate for blaylockbk/Herbie is 100.0%, based on public PR activity from non-core contributors.
blaylockbk/Herbie currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Download numerical weather prediction datasets (HRRR, RAP, GFS, IFS, etc.) from NOMADS, NODD partners (Amazon, Google, Microsoft), ECMWF open data, and the University of Utah Pando Archive System.
Collaborative maintainer environment in blaylockbk/Herbie. Reviews community pull requests with focus on project quality.
Discussions in blaylockbk/Herbie focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/blaylockbk/Herbie?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~12 hours (45% approval). Keep your diff compact for rapid review.
Discussed in #538 Originally posted by williamhobbs May 7, 2026 I managed to miss this until today, so maybe others missed it as well. From https://www.linkedin.com/posts/ifs50r1-opendata-aifs-share-7458166864892968961-5Tp7: 📢 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗻𝗮𝗺𝗶𝗻𝗴 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗮𝗵𝗲𝗮𝗱 𝗳𝗼𝗿 𝗮𝗹𝗹 𝗘𝗖𝗠𝗪𝗙 𝗱𝗮𝘁𝗮 👇 IFS Cycle 50r1 goes live from the 06 UTC run on 12 May 2026, and it comes with naming changes that affect anyone with hard-coded stream or type values in their code. 𝗧𝗵𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀: 📌 stream=scda → stream=oper (the 06 and 18 UTC runs join the main stream) 📌 stream=enfo, type=cf → stream=oper, type=fc (ENS Control and ex-HRES become one forecast) 📌 For waves: stream=scwv → stream=wave, and stream=waef, type=cf → stream=wave, type=fc To make sure I’m understanding correctly, for init dates 2026-05-12 06:00 and later, where we would h
Readthedocs now uses uv natively https://about.readthedocs.com/blog/2026/04/uv-native-support/
I'm having trouble with the new eccodeslib dependency in the Herbie conda-forge feedstock. conda-forge/herbie-data-feedstock#31 Not sure what to do about it yet, but it's preventing publishing the latest release on conda-forge.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to blaylockbk/Herbie, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of blaylockbk/Herbie acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
blaylockbk/Herbie has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.7 places blaylockbk/Herbie in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, blaylockbk/Herbie currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for blaylockbk/Herbie are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.