WB-Toolbox 3.0 Released #279
diegoferigo
started this conversation in
Releases
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The
WB-Toolbox
3.0 was released today and is now available for download at https://github.com/robotology/wb-toolbox/releases.This is a major release, you can find here below a detailed changelog.
This version comes with a new website and a first version of a doxygen-based documentation. An heavy update of the latter is coming soon.
Please visit the migration guide from the 2.0 version.
Changelog
For
WB-Toolbox
UsersyarpWholeBodyInterface.ini
.Subsystem
) overrides the ones present in the higher level. All blocks which need data from a Configuration block have in their mask a button to highlight the Configuration block to which they refer to.PWM
andCurrent
control modes.PID
andWBTPIDConfig
classes have been developed to store PID data. The block's mask reads the name of the object which must be present in the workspace before the simulation starts. Furthermore, support of multiple configurations has been dropped.For
WB-Toolbox
DevelopersMatlab
WBToolboxLibrary
which contains the blocks displayed in the Simulink Library Browser is now exported only inslx
format (Matlab >=2014b
).+WBToolbox
package.WBToolboxConfig
class is used to store the robot configuration.WBBlock
must callBlockInitialization.m
in their mask'sInitialization
.Mask2WBToolboxConfig.m
reads the Configuration block's mask and creates aWBToolboxConfig
object.WBToolboxConfig2Mask.m
fills a Configuration block's mask with data parsed from aWBToolboxConfig
object.WBBlock
parameters are now passed to C++ using astruct
extracted from aWBToolboxConfig
object in the mask'sInitialization
.Block
need only 1 parameter: the::ClassName
.WBBlock
needs only 3 parameter: the::ClassName
, theWBTConfigParameters
(struct
extracted from aWBToolboxConfig
), and theconfigBlockAbsName
(name of the Configuration block from the root or the Simulink model).WBBlock
does not require anymore changing all the block's masks. It is enough adding a new option in theWBToolboxConfig
Matlab class and then handling its parsing in the C++ side.C++
AnyType
interface has been developed.MxAnyType
is one of its implementationand is used to parse genericmxArray
pointers (includingstruct
s,cell
s, and vectors).iDynTree
is now required by the entireWB-Toolbox
.iDynTree::KinDynComputations
.yarp::dev::RemoteControlBoardRemapper
.WBInterface
singleton has been renamed toToolboxSingleton
.Configuration
has been developed. It contains data parsed from theWBToolboxConfig
Matlab's class.RobotInterface
has been developed. It contains aConfiguration
instance, and it handles in a lazy way all the resources used to communicate to the robot.retainRemoteControlBoardRemapper
in theirinitialization
method, and must callreleaseRemoteControlBoardRemapper
in therterminate
method.WBIBlock
class has been renamed toWBBlock
.WBIModelBlock
class has been deprecated.Signal
class has been rewritten. It supports both contiguous and non-contiguous input signals (output are always contiguous). By default, input signals are now contiguous.Log
substitutesError
.WBBlock
, the robot state passed directly toiDynTree
is now stored in the parent'sWBBlock::iDynTreeRobotState
struct.ModelPartitioner
class instead ofYARPWBIConverter
.GetMeasurement
substitutesGetEstimate
.Other
C++11
is now required.CMake > 3.3
is now required.You can find more details about this major release in robotology/wb-toolbox#46 and robotology/wb-toolbox#56.
Beta Was this translation helpful? Give feedback.
All reactions