Fast and minimalist 3D viewer.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 74%
Response Time: 2d
First Timer Success: 53%
f3d-app/f3d has a recorded first-timer success rate of 53.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in f3d-app/f3d respond to incoming external pull requests in approximately 40.1 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 66.7 places f3d-app/f3d in the A tier.
The external contributor pull request merge rate for f3d-app/f3d is 74.0%, based on public PR activity from non-core contributors.
f3d-app/f3d currently has 42 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in f3d-app/f3d. 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/f3d-app/f3d?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~26 hours (93% approval). Large PRs (>500 lines) take ~192 hours (33% approval). Keep your diff compact for rapid review.
Describe the bug Using triggerEventLoop before a render crashes in ImGUI layer. To Reproduce The following python code segfault/asserts engine = f3d.Engine.create(True) inter_ref = engine.interactor.trigger_event_loop(0.1) while this works perfectly: engine = f3d.Engine.create(True) engine.window.render() inter_ref = engine.interactor.trigger_event_loop(0.1) backtrace: #0 0x00007ffff749a11c in ?? () from /usr/lib/libc.so.6 #1 0x00007ffff743e5d0 in raise () from /usr/lib/libc.so.6 #2 0x00007ffff7425685 in abort () from /usr/lib/libc.so.6 #3 0x00007ffff7426704 in ?? () from /usr/lib/libc.so.6 #4 0x00007ffff74361f2 in __assert_fail () from /usr/lib/libc.so.6 #5 0x00007ffff4690a1b in ImGui::GetIO () at /home/glow/dev/f3d/f3d/src/external/imgui/imgui.cpp:5177 #6 0x00007ffff46710e6 in vtkF3DImguiActor::SetDeltaTime (this=0x555555d62fc0, time=0.10000000000000001) at /home/glow/dev/f3d/f3d/src/vtkext/private/module/vtkF3DImguiActor.cxx:1462 #7 0x00007ffff46
Describe the bug When taking a minimal screenshot, the notifications and console badge are not hidden like the other UI elements. To Reproduce Steps to reproduce the behavior: open a file and somehow generate an error/warning, for example f3d ../testing/data/cow.vtp /dev/null --multi-file-mode=all take a minimal screenshot with ctrl+F12, the screenshot will include the warning/error badge in the top right corner take a minimal screenshot quickly after, the screenshot will include the previous screenshot notification the bottom left corner Expected behavior The screenshot should not contain these two items.
I don't think this is currently possible, but I could be wrong. It would be very handy for my use case (WASM viewer in Manyfold) to be able to disable pan/zoom and just rotate. There is an interaction mode for the opposite, the "2d" style, so presumably this would be like adding another option to that list?
Is your feature request related to a problem? Please describe. InsertNext causes repeated reallocations, which we can avoid in this case (F3DOCCTShapeConverter::ToPolyData) Describe the solution you'd like Count points and cells in a first pass, allocate once.
Is your feature request related to a problem? Please describe. At the moment here's the status of coloring with F3D: --scalar-coloring (boolean): turn on/off scalar coloring --coloring-array (string): select the array name --coloring-by-cells (boolean): specify if the array is located on points or cells --coloring-component (int): specify the component to color with (-1: magnitude, -2: direct scalar) This is hard to use and ``--coloring-component=-2` is a bad design. Describe the solution you'd like --scalar-coloring should allow selection of material, raw vertex/cell colors or color mapping. --coloring-array should cycle on both point and cell arrays --coloring-by-cells should be used only if there's a name conflict on points and cells. --coloring-component should have an effect only if --scalar-coloring is set to "color mapping" Related libf3d options should be changed too. --scalar-coloring should probably be renamed to something more consistent with other options and new behavior
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 f3d-app/f3d, 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 f3d-app/f3d acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.0% were successfully merged into the primary branch.
f3d-app/f3d has a recorded first-timer success rate of 53.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 66.7 places f3d-app/f3d in the Welcoming tier.
The external pull request merge rate is 74.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, f3d-app/f3d currently has 42 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for f3d-app/f3d 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.