Embedded language for high-performance array computations
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 50%
Response Time: 1h
First Timer Success: -
AccelerateHS/accelerate has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AccelerateHS/accelerate respond to incoming external pull requests in approximately 1.2 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 42.8 places AccelerateHS/accelerate in the B tier.
The external contributor pull request merge rate for AccelerateHS/accelerate is 50.0%, based on public PR activity from non-core contributors.
AccelerateHS/accelerate currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active Haskell repository in AccelerateHS/accelerate with ongoing community development and issue triage.
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/AccelerateHS/accelerate?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (62% approval). Large PRs (>500 lines) take ~6 hours (22% approval). Keep your diff compact for rapid review.
On the new pipeline, atrace is not implemented on the PTX platform. atrace (& friends) provide tracing like in Debug.Trace, exported from Data.Array.Accelerate.Debug.Trace. In the rewrite of the compiler, they still need to be implemented for the PTX backend. To work on this issue, you need to work on the new pipeline of Accelerate, available via the branch new-pipeline on my fork (https://github.com/ivogabe/accelerate/tree/new-pipeline). Install cbc and clang as command line tools and add them to the PATH. Write an Accelerate program that uses atrace, and run this program on the PTX backend. You will get errors about missing implementations for atrace in certain functions, which should all be addressed for this issue.
I have looked into the necessary updates to ensure the utility packages work with Accelerate 1.4. I have looked only at the packages listed in the Accelerate README. Overview lens-accelerate: works on master branch, needs major version bump due to re-export of Control.Lens (see also tmcdonell/lens-accelerate#1). accelerate-io: works on master branch. Release due to code changes (no API changes): accelerate-io accelerate-io-vector accelerate-io-JuicyPixels accelerate-io-array accelerate-io-bytestring needs release with major version bump (removed equations from type family). Others do not need changes. linear-accelerate needs release (fix in Num instances, already on master). Also need to relax lens upper bound to 6. accelerate-fft: OverloadedStrings language extension required in llvm-cpu codegen, due to change in dependency. Updated in AccelerateHS/accelerate-fft#14. Installation instructions would be nice to have, since it requires FFTW to be installed (for the native backend
When the new-pipeline got Windows support (ivogabe#13), we disabled the Parlaylib allocator and switched to the system allocator. This was needed as we couldn't link to the functions from Parlaylib. This may have been caused by a mistake in the Cabal configuration. (ivogabe#19). We should test this again. Hopefully we can just remove the compile-time switch between the system allocator and the ParlayLib allocator from the code, and always use ParlayLib. @Doppie23 or @MikevanHuizen2912, if one of you still has Accelerate running on Windows and has some time to test this, it would be greatly appreciated if you could test this! Otherwise @TravisCardwell or I will test this whenever we feel like booting into Windows.
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 AccelerateHS/accelerate, 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 AccelerateHS/accelerate acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
AccelerateHS/accelerate has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 42.8 places AccelerateHS/accelerate in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AccelerateHS/accelerate 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 AccelerateHS/accelerate 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.