blockfactory
blockfactory copied to clipboard
robotology
A tiny framework to wrap algorithms for dataflow programming
Compilation is failing with the following error message: ``` $ make [ 9%] Built target mxpp [ 28%] Built target shlibpp [ 71%] Built target Core [ 80%] Built target...
While setting up the Windows CI of the robotology-superbuild, I am experiencing this error: ~~~ 2019-11-13T15:10:26.6676384Z Checking Build System 2019-11-13T15:10:26.8114995Z Creating directories for 'BlockFactory' 2019-11-13T15:10:26.9428104Z Building Custom Rule D:/a/robotology-superbuild/robotology-superbuild/CMakeLists.txt 2019-11-13T15:10:26.9669757Z...
When compiling the `Mex` target, the compilation fails with the following error: ``` Invalid MEX-file '/.../BlockFactory.mexa64': Gateway function is missing. ``` This happens only on Matlab R2018b. The same commit...
This are some random notes related to get `blockfactory` to generate Modelica blocks. It is meant to be more a place where to store relevant information, rather than an issue...
The [`ExampleToolbox.slx`](https://github.com/robotology/blockfactory/blob/master/example/matlab/ExampleToolbox.slx) if I am not wrong is compiled/requires to be loaded at least Simulink 2018a. If this is the case, it would be nice to document this, and eventually...
Original comment by @traversaro in https://github.com/robotology/blockfactory/issues/5#issuecomment-454402604 : > Generate the XML files after the build by running a program that invokes the `configureSizeAndPorts` method of the block to wrap as...
The `blockfactory::core::Block ` interface of blockfactory support the following methods that seem to indicate that it supports discrete and continuous stateful systems: * `blockfactory::core::Block::numberOfDiscreteStates()` * `blockfactory::core::Block::numberOfContinuousStates()` * `blockfactory::core::Block::updateDiscreteState(const BlockInformation* blockInfo)`...
Despite the code generated with Simulink Coder supports tunable parameters, the ones coming from the block masks are not accessible. Refer to the `Operation` selected from the drop-down menu of...
For several reasons, typically involving performance (due to use of system calls and violation of cache locality) but also determinism on *some* hard real-time OS, a good practice is to...
@traversaro wrote: > Additionally, w.r.t. to debian packaging, it would be good if the default installation prefix was in the search path even without the need to define BLOCKFACTORY_PLUGIN_PATH, so...
Metadata
Owner
Metadata
A tiny framework to wrap algorithms for dataflow programming