Automated modeling and machine learning framework FEDOT
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 82%
Response Time: 11h
First Timer Success: 33%
aimclub/FEDOT 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 aimclub/FEDOT respond to incoming external pull requests in approximately 10.5 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 61.7 places aimclub/FEDOT in the A tier.
The external contributor pull request merge rate for aimclub/FEDOT is 81.8%, based on public PR activity from non-core contributors.
aimclub/FEDOT currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in aimclub/FEDOT 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/aimclub/FEDOT?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~50 hours (37% approval). Keep your diff compact for rapid review.
Summary Introduce TensorData and TensorOutputData classes to unify data representation around torch.Tensor, and update preprocessing and model interfaces to support batched, multi-dimensional data. Motivation Current InputData/OutputData are tied to NumPy/Pandas, which limits performance and scalability for deep learning models. A tensor-first approach will better support GPU acceleration, batch processing, and complex data types. High-level architecture Core tensor types: TensorData (aka TensorBatch): primary input container TensorOutputData (aka TensorBatchOut): primary prediction/output container Backend & dataloader integration: TensorData.backend_name + backend property (torch-only initially) TensorData.dataset / TensorData.dataloader via TensorDataset / DataLoader, configurable by dataloader_kwargs Legacy shim layer: Adapters: InputData <-> TensorData, OutputData <-> TensorOutputData Old APIs (fit(InputData), predict(InputData) -> OutputData) call into new tensor-based im
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 aimclub/FEDOT, 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 aimclub/FEDOT acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.8% were successfully merged into the primary branch.
aimclub/FEDOT 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 61.7 places aimclub/FEDOT in the Welcoming tier.
The external pull request merge rate is 81.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, aimclub/FEDOT 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 aimclub/FEDOT 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.