Skip to content
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

Replace embObjStrain w/ embObjFTSensor #523

Merged
merged 1 commit into from
May 25, 2023

Conversation

Nicogene
Copy link
Member

@Nicogene Nicogene commented May 19, 2023

Now embObjFTSensor can handle also strain board, see robotology/icub-main#874

I will test it on a robot that has both strain and strain2 (e.g iCubGenova02/4).

@pattacini
Copy link
Member

Hi @Nicogene

I suppose that the CI will fail until robotology/icub-main#874 is merged.
Correct?

@Nicogene
Copy link
Member Author

Hi @Nicogene

I suppose that the CI will fail until robotology/icub-main#874 is merged. Correct?

Yes it should 🤞🏻

@valegagge
Copy link
Member

Hi @Nicogene,
I have only a doubt: I saw you updated all the templates file replacing embObjStrain w/ embObjFTSensor. So here is my question: do we want to replace also the old templates?

In my mind, the old templates are related to old versions, so we don't need to update them, just the current template.

What do you think?

@traversaro
Copy link
Member

traversaro commented May 22, 2023

In my mind, the old templates are related to old versions, so we don't need to update them, just the current template.

I think the question is: they are related to old versions in the sense of "old robots", or "old releases of the software"?

If they are "old robots", perhaps it make sense to update them, if they are "old releases of the software", perhaps it could make sense to delete them from the repo, and if people they need to access them, can look in the git history at the corresponding tag?

@Nicogene
Copy link
Member Author

Hi @Nicogene, I have only a doubt: I saw you updated all the templates file replacing embObjStrain w/ embObjFTSensor. So here is my question: do we want to replace also the old templates?

In my mind, the old templates are related to old versions, so we don't need to update them, just the current template.

What do you think?

Hi @valegagge, the idea is to remove embObjStrain (see robotology/icub-main#875) since it works only w/ analogServer that will be removed soon, so those templates will not work anymore if we keep embObjStrain, but if it is for keeping an history I can undo the changes for the templates!

@valegagge
Copy link
Member

Hi @valegagge, the idea is to remove embObjStrain (see robotology/icub-main#875) since it works only w/ analogServer that will be removed soon, so those templates will not work anymore if we keep embObjStrain, but if it is for keeping an history I can undo the changes for the templates!

Hi @Nicogene ,
I think that the configuration files compliant with a template before the number 6, (that is current) don't work anymore because the parser and the module that interacts with such files are changed.
They can work with a particular set of revisions, but I think we lost track of this relation.

Anyway, I don't have a strong opinion on the matter of these changes, but I suggest reverting the template files before version 6.

What do you think?

@pattacini
Copy link
Member

pattacini commented May 23, 2023

Anyway, I don't have a strong opinion on the matter of these changes, but I suggest reverting the template files before version 6.

Ok for reverting for this PR 👍🏻

I think that the configuration files compliant with a template before the number 6, (that is current) don't work anymore because the parser and the module that interacts with such files are changed.
They can work with a particular set of revisions, but I think we lost track of this relation.

Unless there are particular reasons, I would be in favor of removing the old templates outright1, keeping only the last one.

Footnotes

  1. They'll remain within Git history anyway.

@valegagge
Copy link
Member

Unless there are particular reasons, I would be in favor of removing the old templates

I do not completely agree: if a robot is running an old sw-ditro related to an old template, how does he/she verify the meaning of the parameter configuration if the templates are not available?

What do you think if we move the old templates to a folder like old-templates in order to get the current template folder tidier?

@pattacini
Copy link
Member

pattacini commented May 24, 2023

What do you think if we move the old templates to a folder like old-templates in order to get the current template folder tidier?

Fair enough 👍🏻
Better off doing this with another PR though.

Now embObjFTSensor can handle also strain board, see robotology/icub-main#874
@Nicogene
Copy link
Member Author

Anyway, I don't have a strong opinion on the matter of these changes, but I suggest reverting the template files before version 6.

I reverted the changes in the old templates, as soon as robotology/icub-main#874 is merged, we can merge this PR.

@Nicogene Nicogene marked this pull request as ready for review May 25, 2023 09:06
@pattacini
Copy link
Member

robotology/icub-main#874 merged ✅
Rerunning the CI.

@pattacini
Copy link
Member

I need first to churn out a fresh docker image.

@pattacini
Copy link
Member

CI passed ✅

@pattacini pattacini merged commit 7a9209d into robotology:devel May 25, 2023
@Nicogene Nicogene deleted the removeEmbObjStrain branch May 25, 2023 10:08
mfussi66 pushed a commit to mfussi66/robots-configuration that referenced this pull request Jun 19, 2023
MSECode pushed a commit to valegagge/robots-configuration that referenced this pull request Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants