PyBind Segmentation Fault
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 289
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am hoping to use your repo in part of my research. I installed it according to the instructions on the README. The C++ tests are passing, but when I tried to run the Python example, I got a seg fault. I can reproduce the issue by calling to the Euclidean Distance invariant function as shown below:
import numpy as np
import clipperpy
if __name__ == "__main__":
iparams = clipperpy.invariants.EuclideanDistanceParams()
iparams.sigma = 0.01
iparams.epsilon = 0.02
invariant = clipperpy.invariants.EuclideanDistance(iparams)
d1 = np.array([[1.0,2.0,3.0]]).T.astype(np.float64)
d2 = np.array([[1.0,2.0,3.0]]).T.astype(np.float64)
d3 = np.array([[1.0,2.0,3.0]]).T.astype(np.float64)
d4 = np.array([[1.0,2.0,3.0]]).T.astype(np.float64)
scr = invariant(d1, d2, d3, d4)
The seg fault occurs when "invariant" is called.
I am running everything in a container, but I don't think that this should be causing the problem. Could you let me know the versions that you are using to get a working version of the python code (e.g., pybind11, python, cmake, etc.)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by following the README and running the reported Python snippet, then compare its EuclideanDistance call with the passing C++ tests. Inspect the Python binding entry point for EuclideanDistance and verify the supported pybind11, Python, and CMake versions. Done means the call no longer segfaults and the working environment is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100