festim-dev/FESTIM - Open Source PR Review Scorecard

Coupled hydrogen/tritium transport and heat transfer modelling using FEniCS

C-Rank Grade: A (Welcoming) - 66/100

External PR Merge Rate: 70%

Response Time: 2h

First Timer Success: 33%

Frequently Asked Questions

Is festim-dev/FESTIM welcoming to first-time open-source contributors?

festim-dev/FESTIM 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.

How fast can I expect code review feedback on my pull request?

Maintainers in festim-dev/FESTIM respond to incoming external pull requests in approximately 1.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.8 C-Rank™ score (A Tier) represent?

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 65.8 places festim-dev/FESTIM in the A tier.

What is the external contributor pull request merge rate for festim-dev/FESTIM?

The external contributor pull request merge rate for festim-dev/FESTIM is 70.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in festim-dev/FESTIM?

festim-dev/FESTIM currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

festim-dev
festim-dev/FESTIMA•Welcoming131
GitHub
Back to Explorer
festim-dev

festim-dev/FESTIM

131
InactiveA•Welcoming(66/100)Python

Coupled hydrogen/tritium transport and heat transfer modelling using FEniCS

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.2/10
Patience Score
8.0/10
Nitpick Rate
25%

Strict review standards in festim-dev/FESTIM. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in festim-dev/FESTIM focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Link the issue and include reproduction context in the PR
  • •Call out API, migration, or compatibility impact clearly

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not open context-free PRs
  • •Do not hide breaking changes in implementation details
Response Velocity
1 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
70.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
6 core
Highly collaborative maintainer core
Diagnostic Health HUD
70.0%
Merge Gauge
33.3%
1st-Timer
Community Vibe67/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for festim-dev/FESTIM
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/festim-dev/FESTIM)](https://getmerged.abhishekco.de/festim-dev/FESTIM?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Describe the bug Running a transient sim with an OutflowBC raises an AttributeError 'OutflowBC' object has no attribute 'time_dependent'. To Reproduce import numpy as np from dolfinx import fem, mesh as dmesh from mpi4py import MPI import festim as F m = dmesh.create_unit_interval(MPI.COMM_WORLD, 20) left = F.SurfaceSubdomain1D(id=1, x=0.0) right = F.SurfaceSubdomain1D(id=2, x=1.0) vol = F.VolumeSubdomain1D( id=1, borders=[0.0, 1.0], material=F.Material(D_0=1.0, E_D=0.0) ) H = F.Species("H") W = fem.functionspace(m, ("DG", 0, (1,))) v = fem.Function(W) v.x.array[:] = 1.0 model = F.HydrogenTransportProblem( mesh=F.Mesh(m), subdomains=[vol, left, right], species=[H], temperature=500.0, boundary_conditions=[ F.FixedConcentrationBC(subdomain=left, value=1.0, species=H), F.OutflowBC(subdomain=right, species=H), ], drift_terms=[F.AdvectionTerm(velocity=v, subdomain=vol, species=H)], settings=F.Settings( atol=1e-10, rtol=1e-10, tra

📅 Opened Sep 15, 2026💬 0 comments
Quality: 90/100Contribute
📅 Opened Sep 9, 2026💬 0 comments
Quality: 70/100Contribute

(generated by Claude because I didn't have time, will go back to it later) Summary Flagging a convention issue rather than a bug: SurfaceReactionBC has no way to express the statistical degeneracy of a mixed isotopologue channel, and the natural way to write H + D <-> HD is silently inconsistent with detailed balance. Same root cause as the InterfaceReaction discussion in #1222: the rate is the plain product of reactant concentrations, and stoichiometry is expressed only by repeating a species in reactant. The physics For recombination, the forward step carries a degeneracy that the reverse step does not: there are two ways to pick an (H, D) pair to recombine, but an HD molecule dissociates only one way. Writing the homonuclear channel as k_r c_H^2 absorbs the one-half that avoids double counting identical pairs, so consistency requires k_r(HD) = 2 k_r(HH) with equal k_d. This is what reproduces the classical P_HD^2 / (P_H2 P_D2) = 4, i.e. H2 : HD : D2 = 1 : 2 : 1 at equal H and D. No

📅 Opened Aug 5, 2026💬 0 comments
Quality: 80/100Contribute

After this is released: FEniCS/dolfinx#4172 we will be able to move the import of transfer_meshtags_to_submesh from scifem to dolfinx

📅 Opened Apr 23, 2026💬 0 comments
Quality: 55/100Contribute

For very large simulations, even with a rtol=1e-5 the export will be exported very far from the desired export time. Consider the following: import numpy as np import festim as F model = F.HydrogenTransportProblem() model.mesh = F.Mesh1D(np.linspace(0, 1, 10)) mat = F.Material(D_0=1.0, E_D=0.0) vol = F.VolumeSubdomain1D(id=1, material=mat, borders=[0, 1]) model.subdomains = [vol] H = F.Species("H") model.species = [H] model.temperature = 300 model.settings = F.Settings(atol=1e-12, rtol=1e-12, final_time=0.9e8 + 20) model.settings.stepsize = F.Stepsize(1, milestones=[0.9e8]) model.exports = [ F.Profile1DExport(H, subdomain=vol, times=[0.9e8]), ] model.initialise() model.t.value = 0.9e8 - 10 model.run() assert abs(model.exports[0].t[0] - 0.9e8) < 1e-12, ( "time of export is far from the expected" ) proposed solution expose rtol and atol in is_it_time_to_export as an argument of F.Settings that will be used for all exports Tagging @AdriaLlealS

📅 Opened Feb 23, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for festim-dev/FESTIM

When evaluating whether to contribute to festim-dev/FESTIM, 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 festim-dev/FESTIM acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to festim-dev/FESTIM

01

Is festim-dev/FESTIM welcoming to first-time open-source contributors?

festim-dev/FESTIM 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.8 C-Rank™ score represent?

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 65.8 places festim-dev/FESTIM in the Welcoming tier.

04

What is the external contributor pull request merge rate for festim-dev/FESTIM?

The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in festim-dev/FESTIM?

Yes, festim-dev/FESTIM currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for festim-dev/FESTIM 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.