Nonconvex embedded optimization: code generation for fast real-time optimization + ROS support
C-Rank Grade: D (Risky) - 24/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
alphaville/optimization-engine has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in alphaville/optimization-engine 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 24.2 places alphaville/optimization-engine in the D tier.
The external contributor pull request merge rate for alphaville/optimization-engine is 0.0%, based on public PR activity from non-core contributors.
alphaville/optimization-engine currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in alphaville/optimization-engine. Reviews community pull requests with focus on project quality.
Discussions in alphaville/optimization-engine 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/alphaville/optimization-engine?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Describe the bug PANOCEngine.linesearch() does the wrong update if MAX_LINESEARCH_ITERATIONS is reached. PANOCEngine.line_search_condition() can fail for the wrong reason. In more detail. The current code is if num_ls_iters == MAX_LINESEARCH_ITERATIONS { self.cache.tau = T::zero(); u_current.copy_from_slice(&self.cache.u_half_step); } // Sets `u_current` to `u_plus` (u_current ← u_plus) u_current.copy_from_slice(&self.cache.u_plus); If I understand the algorithm correctly, if we reach MAX_LINESEARCH_ITERATIONS, the update should use tau=0, but that isn't what is happening here. The following should fix it if num_ls_iters == MAX_LINESEARCH_ITERATIONS { self.cache.tau = T::zero(); // updating with tau = 0 self.line_search_condition(u_current)?; // No need to update u_current here } The comment above the method says /// Computes the left hand side of the
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 alphaville/optimization-engine, 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 alphaville/optimization-engine acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
alphaville/optimization-engine has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 24.2 places alphaville/optimization-engine in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, alphaville/optimization-engine 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 alphaville/optimization-engine 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.