/ᐠ. ｡.ᐟ\ᵐᵉᵒʷˎˊ˗
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 38%
Response Time: 11h
First Timer Success: 33%
ExtremeFLOW/neko has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ExtremeFLOW/neko respond to incoming external pull requests in approximately 10.9 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 63.8 places ExtremeFLOW/neko in the A tier.
The external contributor pull request merge rate for ExtremeFLOW/neko is 38.5%, based on public PR activity from non-core contributors.
ExtremeFLOW/neko currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ExtremeFLOW/neko welcoming community pull requests and bug fixes.
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/ExtremeFLOW/neko?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (48% approval). Large PRs (>500 lines) take ~52 hours (17% approval). Keep your diff compact for rapid review.
I have done some test runs in single precision for the ABL case (using examples/shear_convection_abl and other similar setups). It seems to be broken. This issue is to track this problem and hopefully solve it. Fluid stats: Temperature stats: I don't know exactly how to tackle this, so here is some random observations: the variable that really seems to be broken is temperature. I am thinking that everything "starts" there and the propagates to the velocity fields via the Boussinesq term in the momentum equations (in ABL cases, that's how temperature is coupled to velocity) however, there are some weird stuff in the fluid statistics as well: see for instance the little wiggles above 750m in it doesn't seem to be dependent on resolution. I have tested both a coarser and finer resolution and the problem is the same the equivalent Double Precision case works perfectly the tests have been carried out on LUMI only I am thinking to start debugging this by running without temperature firs
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 ExtremeFLOW/neko, 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 ExtremeFLOW/neko acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 38.5% were successfully merged into the primary branch.
ExtremeFLOW/neko has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 63.8 places ExtremeFLOW/neko in the Welcoming tier.
The external pull request merge rate is 38.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ExtremeFLOW/neko currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ExtremeFLOW/neko 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.