Unable to load the yarp devices built by wearables in Windows #91
Comments
|
Which version of YARP are you using? |
|
The error:
Was added to solve the issue robotology/yarp#975 . Can you double check the content of the automatically generated .ini files installed by wearables for YARP devices? |
|
I see that this repo is still shipping manually written .ini files for YARP devices. While this in theory is still supported, is for sure much more error prone. Switching to the automatic generation of this file should avoid possible problems. |
|
Related issue: #79 . |
In theory this was fixed in #80 . I am not sure why .ini files are still around. |
Sorry, I probably was wrong and instead the files are no longer there. |
YARP version 3.4.1+29-20201020.2+git35f80d6d4 |
Yes, looks like the fix was done only to Update: the ini files for |
|
In any case, I think it would be useful to check all the files installed by wearables and check if there is anything strange there. I am particularly worried about the |
|
All the other devices installed by the superbuild instead listed by |
|
@Yeshasvitvs @lrapetti may you give your inputs here? |
|
I am here with @GiulioRomualdi , it seems like the installation of the plugins of wearable repo is not done correctly. |
yes, only the plugins of the wearable library could not be run |
|
Given that the demo was done successfully, I guess that this was solved, or at least a workaround was found? |
This should permit to debug problems such as robotology/wearables#91 .
|
@GiulioRomualdi please close this if do not have the problem anymore. |
|
To be honest I was able to reproduce the problem as part of the robotology-superbuild CI in https://github.com/robotology/robotology-superbuild/pull/521/checks?check_run_id=1425070305 (see " Check if YARP devices are correctly listed [Windows]" section, part of PR robotology/robotology-superbuild#521). So I think the problem is still there, see: |
|
@Yeshasvitvs @lrapetti @GiulioRomualdi, it would be nice that someone gives an update on this
to avoid future problems in hard times |
Sorry, we got carried away with the results of the experiments. No, this issue was not solved. We need to work on this and understand the problem. As a first step, maybe we can try to check the versions of the software on the other Windows machine on which we ran the experiment and try to replicate that environment in the newer machine (which was supposed to be used for the experiments.) |
I think we will forget about this issue if we close it, let's keep it open until we solve it. |
|
The problem is not solved. We ran the experiments on a different laptop. I would avoid to close this issue |
Just to understand, given that the problem was present was already in May #79, that laptop was not updated since before May? Which version of YARP, CMake and wearables is that laptop using? |
I am not sure about the setup we are talking about above, but in the new setup which was prepared from scratch in Sept/Oct by @Yeshasvitvs, the device are loaded correctly. We should investigate why there is working fine. |
That is quite interesting. A few info that it would be interesting to get there:
|
I double checked the dependencies, and I used https://github.com/microsoft/vcpkg/ at microsoft/vcpkg@5d33bd3 May be this needs to be aligned with the documentation on robotology https://github.com/robotology/robotology-superbuild#system-libraries and use https://github.com/robotology/robotology-superbuild-dependencies-vcpkg/releases
CMake 3.18.3
https://github.com/robotology/ycm/tree/ycm-0.11
https://github.com/robotology/yarp/tree/yarp-3.4 Another detail as pointed by @traversaro is the last release tag of wearables https://github.com/robotology/wearables/releases/tag/v1.0.0 that is used in https://github.com/robotology/robotology-superbuild/blob/master/releases/2020.11.yaml#L106-L109 We are working on a bit of cleanup now following which @lrapetti with make a new release and test the new release on the machine @GiulioRomualdi ran into problems. UPDATE: I was doing some development #82 #84 #81 on the machine and it was updated to master branch latest commit e7429bc |
yes, all the plugins (devices and wrappers) that are built and installed from wearables repo are discovered correctly. |
|
The idea can be to investigate if the error is reproducible on a new installation on Windows. |
Can you please refer to machines with their IIT code so that it is clear to which machine are we referring to?
Was that on a clean build or not? To clarify, the fact that on some machines it is working, and that on other machines and on GitHub Actions (that is a perfectly deterministic environment) it is not working, lead me to think that there is probably either something that depends on the environment (such as some local CMake or environment change) of the specific machine, or (even worse!) a non-deterministic issue. If it was the other way around (i.e. that on GitHub actions it did work, and just on some machines it was not working) I would be more relaxed, but the fact that the problem is constantly occuring on GitHub Actions lead me to think that it is highly probably that it could occur on new Windows machine, and I think that having software that "sometimes" does not work is a ticking bomb that could create problems in the future (think for example if we need to prepare a new laptop for Andy/iFeel demos). |
|
Hi, guys at this moment. I don't have time to check this. I'm sorry. If you don't want to keep the issue open please feel free to close it. Someone will reopen it again in case of problems |
|
No worries @GiulioRomualdi . It's better for us (An.Dy guys) to have a check on this. Thanks anyway. |
We are referring to
Here are the exact commit:
We could try to replicate the same configuration to investigate if the problem was introduced by some update in YCM or YARP, or try to update them to check if the error occur also on this machine. |
|
I restarted the build in https://github.com/robotology/robotology-superbuild/pull/521/checks?check_run_id=1485361566, and the problem is not occurring anymore in the |
Possibly replacing
I'll open a separate issue for adding this check robotology/human-dynamics-estimation#402 |
|
Perfect! |
Following these changes in the upstream, I compiled and installed wearables on the Alienware machine this issue was observed by @GiulioRomualdi . All the wearable devices are now discovered and loaded correctly.
NOTE: For the We can do one more final testing of launching xsens suit wearable device on this machine before closing this issue, to ensure everything is in order. CC @lrapetti @S-Dafarra @GiulioRomualdi @claudia-lat @traversaro @DanielePucci |
I did a quick test with the xsens sensors placed on the table, and the xsens suit wearable device loaded, calibrated and started data acquisition without any problems
|
|
Perfect, thanks @Yeshasvitvs ! At this point we can close the issue I guess? |
|
Closing after checking with @GiulioRomualdi |
We installed wearables with the superbuild however when we try to check the devices
yarp dev --listthe following errors occurI'm using windows 10. From dependency walker everything is ok
The text was updated successfully, but these errors were encountered: