SofaPython3 icon indicating copy to clipboard operation
SofaPython3 copied to clipboard

A python plugin for Sofa offering a pythonic interface and python3 support.

Results 85 SofaPython3 issues
Sort by recently updated
recently updated
newest added

_Originally posted by @ScheiklP in https://github.com/sofa-framework/SofaPython3/issues/290#issuecomment-1284069903_ ------- When trying to write into `MechanicalObject.position`, with `writeable()` or `__setitem__`, SofaPython3 checks if the data is dirty or not in `memcache`. For some...

issue: bug

Hi, there is another memory leak, this time related to rendering in combination with `simulation.unload`. As a testing scene, I took the [pygame example from SofaPython3](https://github.com/sofa-framework/SofaPython3/blob/master/examples/additional-examples/pygame_example.py) and added a reload...

SOFA PR https://github.com/sofa-framework/sofa/pull/2988/ introduces a new mechanism for the application of the gravity (broken inheritance from ForceField). This PR propagates the changes in the python bindings

pr: status wip

All examples udpated!

pr: status wip
pr: clean-fix
pr: fast-merge

The plugin scans the plugin reporitories to locate what are the Sofa plugins that match a given pattern. Once found it createe a hierarchy in the scene graph by splitting...

pr: new feature
topic for next dev-meeting

Further to #284 we noticed that missing tests on the execution of a SOFA simulation in a python interpreter For the future, refactoring the PythonEnvironment file to split PythonEnvironment in...

A new feature on all SOFA objects `object.linkpath` now returns a type LinkPath (not a string) to provide directly path of objects in the scene and connect components. This feature...

pr: experimental

Some issues were notice with visualization on SP3 master. Works fine with release v21.06.00. Texture visualization with SOFA master does not work due to issue reported here: https://github.com/sofa-framework/sofa/issues/2392 To be...

enhancement
pr: status wip
pr: highlighted in next release

The default behavior should be the most common use case while more rare scenario should be accessible but with explicit call api (opt-in vs opt-out strategy). Currently the default case...

pr: status wip
pr: new feature
pr: experimental

This PR brings: - Bindings for BaseState - Bindings for VecId and MultiVecId - Bindings for ExecParams and MechanicalParams - Bindings for VectorOperations and MechanicalOperations (aka vop and mop) -...

pr: status wip
pr: new feature