-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark this repo as deprecated and not mantained and move it in robotology-legacy? #29
Comments
@traversaro I am sorry but I do not know the content of this repo, did you mention me by mistake or because I should check? |
I did not want to bother Lorenzo with this and so I picked the senior person in HSP that could know something about this (being related to machine learning), it was a bet but given your reply I think I was not lucky. : ) |
:) Then I am sorry but I cannot provide more information regarding future plans for this repo, as far as I read from the issue you mentioned. |
hi @traversaro nobody in the group is currently working on this code so we cannot reply to issues in a timely manner as you noticed. However, it is likely we will start using it again in a near future as we are planning to work with RL algorithms for grasping. One thing we should do now is to fix the models in https://github.com/robotology/icub-models ( robotology/icub-models#12) and change the code so that this repo uses those models (if I understand the problem described in the issue). |
added warning issue in readme, hopefully we will remove it soon enough :) |
Thanks @lornat75 ! |
Hi @lornat75 @GiuliaP,
there are a few issue and PR left unanswered in this repo. To avoid confusions in the users (last occurrence in robotology/icub-models-generator#29 (comment)) could it make sense to modify the README of the repo to specify that is not maintained anymore? If we want to make this even more clear, we can even move the repo to https://github.com/robotology-legacy and archive it.
The text was updated successfully, but these errors were encountered: