AMReX: Software Framework for Block Structured AMR
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 75%
Response Time: -
First Timer Success: 47%
AMReX-Codes/amrex has a recorded first-timer success rate of 46.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AMReX-Codes/amrex respond to incoming external pull requests in approximately 0.0 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 67.8 places AMReX-Codes/amrex in the A tier.
The external contributor pull request merge rate for AMReX-Codes/amrex is 75.4%, based on public PR activity from non-core contributors.
AMReX-Codes/amrex currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in AMReX-Codes/amrex. Prompt code reviews with positive guidance for new contributors.
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/AMReX-Codes/amrex?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
The current TinyProfiler implementation on GPU only gives reliable numbers if used with host-triggered GPU synchronizations, which can be severly hurtful to performance #3763 #4953 BLAST-WarpX/warpx#6593. We need to discuss: what do we actually want to measure? start-to-end of specific kernels? the ratio of compute vs communication? Do we care if they overlap with other kernels / data copies? what level of details & kernels / routines do we really care about in which situation? Developer tooling? do we try to replace a tracer like Nsight Systems or a Profiler (performance debugging) or User tooling? do we want to have a good-enough idea of the dominating costs of an AMReX simulation (production runs), given a complex, real-world mesh/particle load & load balance? If we can answer these questions a bit more clearly, we could redesign on which level we actually add profile annotations (or add verbosity levels for production vs. development) redesign how we measure, e.g., we could i
There are too many BLPROFILE annotations in the MultiGrid solver that, if used with synchronizing TinyProfiler for accurate measurements #3763, hurt performance a lot for small grids: BLAST-WarpX/warpx#6593 (comment) BLAST-WarpX/warpx#6593 (comment)
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 AMReX-Codes/amrex, 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 AMReX-Codes/amrex acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.4% were successfully merged into the primary branch.
AMReX-Codes/amrex has a recorded first-timer success rate of 46.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.8 places AMReX-Codes/amrex in the Welcoming tier.
The external pull request merge rate is 75.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AMReX-Codes/amrex currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AMReX-Codes/amrex 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.