Inti Pelupessy
Inti Pelupessy
I don't think any work has been done on this one yet?
great! I would also put the changes in new (derived) classes in this case (and a more descriptive name than bridgev) in bridge.py. Can you also add an example of...
ok, I checked more carefully now: you should indeed make a new: ``` class BridgeWithVelocityDependendForces(Bridge): ..etc ``` (or some other descriptive name)..the option use_velocity still has to be present because...
one thing I don't fully like: the method to get the acceleration in the velocity kick case is still called get_gravity; maybe it should be renamed to get_acceleration?
ok, I see you had the same concern ;-)
keep open for now
@hamers so I started a bit #557
commit 8a24874e38189de3018f7aa635bd1e433461bb0f fixes some of the seg faults..its the functions w/o return that cause the segfaults..I still think update and linkage with the current git version is a good idea...
certainly not completed