NTRT Simulator
v1.1
|
add to config
if bogus, stop trial (reset simulation)
if bogus, stop trial (reset simulation)
if bogus, stop trial (reset simulation)
if bogus, stop trial (reset simulation)
- consolidate with other controller classes.
- return length scale as a parameter
- return length scale as a parameter
- return length scale as a parameter
- return length scale as a parameter
should this throw an exception instead??
get top, left, right offset, add bodywaves back in.
better name?
ask about refactoring to use for_each
ask about refactoring to use for_each
better name?
ask about refactoring to use for_each
: reference the things that do this for us
: there seems to be an issue with Muscle2P connections if the front of a tetra is inside the next one.
: the snake is a temporary variable – will its destructor be called? If not, where do we delete its children?
: there seems to be an issue with Muscle2P connections if the front of a tetra is inside the next one.
: the snake is a temporary variable – will its destructor be called? If not, where do we delete its children?
- consolidate with other controller classes.
- return length scale as a parameter
Does the model assume ownership of the controller?
Does the model assume ownership of the controller?
Does the model assume ownership of the controller?
Does the model assume ownership of the controller?
Does the model assume ownership of the controller?
Does the model assume ownership of the controller?
add to config
if bogus, stop trial (reset simulation)
- consolidate with other controller classes.
- return length scale as a parameter
Inlining this does no good; stream operations are slow.
Do we need to re-add the collision shape for debugging?
should this throw an exception instead??
verify data!
add to config
if bogus, stop trial (reset simulation)
- consolidate with other controller classes.
- return length scale as a parameter
acceleration constraint was removed on 12/10/14 Replace with tgKinematicActuator as appropreate
acceleration constraint was removed on 12/10/14 Replace with tgKinematicActuator as appropreate
acceleration constraint was removed on 12/10/14 Replace with tgKinematicActuator as appropreate
consider implications of casting to include Corde objects
Use typeinfo to verify that this is correct.
Make this const here and in all base classes and derived classes.
Make rigid const when tgCompoundRigidInfo::getCenterOfMass() is const.
If all m_rigids are supplied in the constructor, this can be calculated in the constructor and cashed as a const member variable.
What is the purpose? The caller must already have the object, a reference or a pointer to be able to call this.
Add this to the base classes and derived classes.
Do this in the constructor and cache the result as a member variable.
Use std::accumulate()
Change this to std::set to prevent duplication.
Make this const and initialize it in the constructor.
Make this const in all base classes and all derived classes.
Make other const in all base classes and all derived classes.
Use std::find_if()
move functions to constructor when possible
move functions to constructor when possible
examine whether this should be public, and perhaps create a read only version
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Unnecessary copying can be avoided by pasing the result collection in the recursive step.
Is it OK for from == to, either the same object or the same value?
Is it OK for from == to, either the same object or the same value?
upgrade once the messaging protocol is in place
- are there any sanity checks we can enforce here?
: For the generic tgRigidInfo implementation, allow people to provide a delegate object to find the connection point.
: Should this return a reference instead of a value? Possibility of change indicates a reference, but do we want to allow this to be changeable?
write a function that returns the normal of a vector without overwriting the original vector line btVector3's .normalize() functions
Normalize the return value so that it is in [0.0, 360.0).
can we make the ground const?
Use the factory method design pattern to create the m_pImpl object.