fuse: 0.4.1-1 in 'noetic/distribution.yaml' [bloom] #30198
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Increasing version of package(s) in repository
fuse
to0.4.1-1
:noetic/distribution.yaml
0.10.7
null
fuse
fuse_constraints
fuse_core
fuse_doc
fuse_graphs
fuse_loss
fuse_models
fuse_msgs
fuse_optimizers
error:
[FATAL] [/Optimizer] [1604557006.977288017]: Could not find required parameter twist_target_frame in namespace /Optimizer/imu
Mostly for:
In order to match the getParam and getRequiredParam, so the value is
not returned, but set in an in/out argument.
parameter.h from util.h, and updated the ros/unit tests accordingly.
Instead of (-Pi, +Pi], and update unit test to reflect that.
This allows to compound multiple YAML files that provide additional
models or publishers. This cannot be done with a list/array, because the
previous values get overwritten/lost.
By using the transaction stamp instead of ros::Time::now() it's
possible to replay things with the same transaction and compare the
original and new generated graphs.
Mostly for:
If a constraint has a loss function, the cost is computed with and
without loss, and the quotient of the cost with loss by the cost without
loss is used to scale the error line. This is used to draw a "loss"
error line, so we can see the contribution of the loss function to the
constraint.
the properties are later created
Mostly for:
If a constraint has a loss function, the cost is computed with and
without loss, and the quotient of the cost with loss by the cost without
loss is used to scale the error line. This is used to draw a "loss"
error line, so we can see the contribution of the loss function to the
constraint.
the properties are later created