perfanalytics/pose2sim - Open Source PR Review Scorecard

Markerless kinematics with any cameras — From 2D Pose estimation to 3D OpenSim motion

C-Rank Grade: D (Risky) - 12/100

External PR Merge Rate: -

Response Time: 17d

First Timer Success: -

Frequently Asked Questions

Is perfanalytics/pose2sim welcoming to first-time open-source contributors?

perfanalytics/pose2sim 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.

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

Maintainers in perfanalytics/pose2sim respond to incoming external pull requests in approximately 397.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 12.4 C-Rank™ score (D 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 12.4 places perfanalytics/pose2sim in the D tier.

What is the external contributor pull request merge rate for perfanalytics/pose2sim?

The external contributor pull request merge rate for perfanalytics/pose2sim is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in perfanalytics/pose2sim?

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

perfanalytics
perfanalytics/pose2simD•Risky798
GitHub
Back to Explorer
perfanalytics

perfanalytics/pose2sim

798
InactiveD•Risky(12/100)Low Sample (<20 PRs)Python

Markerless kinematics with any cameras — From 2D Pose estimation to 3D OpenSim motion

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in perfanalytics/pose2sim welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
16 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Your OS Windows Your Python version 3.13 What is your library version? 0.10.49 Your problem Hi, When using a Qualisys system that includes a Miqus Hybrid camera, the calibration step (Pose2Sim.Calibration()) fails. The if condition only checks for "video" and "none", so Hybrid cameras aren't recognized, leading to an empty Calib_qualisys.toml file. Location Code line 144 in Pose2Sim.Calibration() : if any(model in tag.attrib.get('model', '').lower() for model in ["video", "none"]): Fix Solved with : if any(model in tag.attrib.get('model', '').lower() for model in ["video", "hybrid", "none"]):.

📅 Opened Jul 24, 2026💬 1 comment
Quality: 80/100Contribute

Your OS Mac Your Python version Python3.13.13 ( python3.11.15 also have this problem) What is your library version? pose2sim 0.10.47 Your problem Hello! I am a first-year graduate student at a sports university in China. First of all, I would like to sincerely thank you for Pose2Sim—it has provided great conceptual inspiration and technical support for my thesis project.I am using a MacBook with the M5 Pro chip. However, I ran into an issue at the very first step: Pose2Sim.calibration(), problem like this: " ** In [1]: from Pose2Sim import Pose2Sim In [2]: Pose2Sim.calibration() Matplotlib is building the font cache; this may take a moment. Failed to extract font properties from /System/Library/PrivateFrameworks/FontServices.framework/Resources/Reserved/PingFangUI.ttc: FT_Open_Face (ft2font.cpp line 200) failed with error 0x02: unknown file format Failed to extract font properties from /System/Library/Fonts/Apple Color Emoji.ttc: Non-scalable fonts are not supported Failed to extract

📅 Opened Jun 26, 2026💬 13 comments
Quality: 55/100Contribute

Your OS Windows Your Python version No response What is your library version? No response Your problem Hi David we are trying to do an extrinsic calibration of our cameras with scene These are the values we defined in config.toml [calibration.calculate.extrinsics.scene] # list of 3D coordinates to be manually labelled on images. Can also be a 2 dimensional plane. # in m -> unlike for intrinsics, NOT in mm! # [X,Y,Z], which becomes [Z,X,Y] in the TRC reference frame, and [-Y,X,Z] in the Blender one object_coords_3d = [[0.0, -0.54, 0.0], [0.02 , -0.51, 0.10], [0.00 , -0.54, 2.11], [0.0, 0.0, 3.0], [3.02, -0.02 , 0.0], [3.0, 0.0 , 0.1]] the 6 poins are: 1: lower end of the right side of the door 2: left end of the base board next to the door 3: upper end of the right side of the door 4; top right corner of the room 5: end of the right wall, meeting the floor 6: corner of the base board 10 cm above point 5 at the wall Please see also the green crosses in the image. Do you have any

📅 Opened Jun 7, 2026💬 14 comments
Quality: 80/100Contribute

Currently, we have 3D pose data that we gathered using DeepLabCut and are trying to go to an OpenSim model using Pose2Sim. I am having some trouble figuring out the folder structure to use for multiple trials and what needs to be changed in the config.toml files. Here is what I currently have: --Main Project Folder       --Config.toml       --Trial N             --Config.toml             --Videos                   -- Raw, unlabeled videos             --Calibration                   -- camera intrinsics/extrinsics/config             --Pose                   -- camN                         --camN.h5                         --camN.csv What needs to be changed in each Con

📅 Opened Jan 30, 2026💬 3 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 perfanalytics/pose2sim

When evaluating whether to contribute to perfanalytics/pose2sim, 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 perfanalytics/pose2sim acknowledge new external contributions in approximately 16 days+. 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.

Frequently Asked Questions - Contributing to perfanalytics/pose2sim

01

Is perfanalytics/pose2sim welcoming to first-time open-source contributors?

perfanalytics/pose2sim 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.

02

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

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

03

What does the 12.4 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 12.4 places perfanalytics/pose2sim in the Risky tier.

04

What is the external contributor pull request merge rate for perfanalytics/pose2sim?

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.

05

Are there beginner Good First Issues open in perfanalytics/pose2sim?

Yes, perfanalytics/pose2sim 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 perfanalytics/pose2sim 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.