Comments (10)
fyi @robotology/iit-ami-scrum-masters when implemented this may affect configuration files on our side.
from robots-configuration.
As discussed in a private chat with @Nicogene, we decided to add the sensorName
tag in all the FT IMUs XML files and the chosen names must be coherent with the simulated ones.
-
For the ergoCub side, since:
the sensorName tag should be
<part>_ft_imu
(for example,l_arm_ft_imu
) to make it different from the FT ones without the suffix_imu
: -
For the iCub side, instead, with:
there were added the
alljoints-inertials
also for iCub models, but the name used is the same as the FT ones, i.e.<part>_ft
. According to the nice-to-have, it could be useful/nice/coherent using the same convention used for ergoCub and fix the simulated models with a PR on icub-models-generator.
cc @Nicogene @pattacini @traversaro
from robots-configuration.
Great! Do you think it could make sense to document this convention of the sensor names somewhere in the docs? We can just write down that its implementation is still work in progress, but at least to have a reference for the future.
from robots-configuration.
For each sensor belonging to a robot part there's a table with a column named
Sensor Name
. What about using this? Or we can add an extra column in these tables
I think that "sensor name" in the table is a bit misleading, as what is indicating is the prefix of the port that publish information about the reference sensors, not the sensor name, so I totally agree in using that column.
from robots-configuration.
cc @mfussi66 since he added this information to the documentation.
from robots-configuration.
For the time being, I opened this PR:
to set a starting point for the real robots. The simulated ones will be modified taking this PR as a reference
from robots-configuration.
Since
* [ IMU sensors: add sensorName tag in FT IMU xml #637](https://github.com/robotology/robots-configuration/pull/637)
has been merged, could we close this issue? I'll proceed to update iCub and ergoCub models according to that PR.
Let's close it when also the models PR will be merged
I'll revive this PR:
https://github.com/icub-tech-iit/ergocub-software/pull/232
and open a new one on icub-models-generator
Put it ready for review and rebase it, it may be that you will face some conficts, once resolved please let me know when generating the V1_1 models
from robots-configuration.
There are those pages in the doc for the sensors:
- https://icub-tech-iit.github.io/documentation/robot_sensors/ergocub_sensors/
- https://icub-tech-iit.github.io/documentation/robot_sensors/icub2.7_sensors/
For each sensor belonging to a robot part there's a table with a column named Sensor Name
. What about using this? Or we can add an extra column in these tables
cc @traversaro @Nicogene @pattacini
from robots-configuration.
Since
has been merged, could we close this issue? I'll proceed to update iCub and ergoCub models according to that PR.
from robots-configuration.
I'll revive this PR:
and open a new one on icub-models-generator
from robots-configuration.
Related Issues (20)
- Replace `analogServer` with `multipleanalogsensorsserver` for publishing FT data – Stint 2 HOT 8
- ergoCubSN000: expose BMS on YARP network via `battery_nws_yarp` HOT 1
- CI failing on `ergoCubSN000` and `iCubGenova09` with the latest `yarp-3.8` HOT 11
- Missing example for `embObjMultipleFTsensors` device in `iCubTemplates/iCubTemplateV6_0/hardware/FT`
- Split robots between `maintained` and `unmaintained` and refactor CI dry-run accordingly HOT 3
- [ergoCubSN000] Gear ratio values of right and left shoulder roll joints do not match HOT 3
- Update maintained robots to the use of `multipleanalogsensorsserver` for `embObjMAIS` device HOT 3
- Check and validate ergoCub wrist-mk2.x gear ratios HOT 13
- Wrong eyes joint names for iCubGenova11 HOT 4
- Replace `embObjInertial` w/ `embObjIMU` – Stint 2 HOT 11
- Port all the robots' configuration to the TemperatureSensorType parameter HOT 2
- Register iCub `iCubManchester01` and update robotology-superbuild HOT 16
- CI for tests `dry-run_R!SN00?_dev` HOT 1
- Add alljoints-inertials_wrapper/remapper
- Cleanup ergocub configuration files using `enable_by` and `disable_by` yarprobotinterface tags HOT 6
- [ergoCubSN00*] Missing elbow and wrist joints from axesNames used in WBD HOT 5
- Remove ergocub xml leftovers
- Enable tags not working for ros2 HOT 11
- wholeBodyDynamics configuration files for ergoCubSN00* not setting the estimateJointVelocityAcceleration option? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from robots-configuration.