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.

Sign up for GitHub

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

Jump to bottom

Review and Unify TEO dynamic model #16

Open
3 tasks
PeterBowman opened this issue Aug 16, 2017 · 35 comments
Open
3 tasks

Review and Unify TEO dynamic model #16

PeterBowman opened this issue Aug 16, 2017 · 35 comments
Assignees
@imontesino @AlvaroMartinezR
Labels
complexity: tedious Tarea tediosa que nadie quiere hacer documentation epic horizontal
Projects
[TEO]

Comments

@PeterBowman
Copy link
Member

From @jgvictores on April 20, 2016 10:59

Issue inherited from wiki, where work has been done (resulting in current TEO Diagrams). The following is a list of models to potentially be merged or linked somehow.

For future reference, links to Mass/Inertia (official based on mechanical schematics): .XLS and .PDF.

Updated on 16/08/17 by PeterBowman.

Copied from original issue: roboticslab-uc3m/kinematics-dynamics#29
@PeterBowman PeterBowman mentioned this issue Aug 16, 2017
Closed
3 tasks
This was referenced Nov 8, 2017
Closed
Closed
@jgvictores jgvictores changed the title Unify robot model dynamics Review and Unify TEO dynamic model Nov 8, 2017
@jgvictores
Copy link
Member

From @AlvaroMartinezR on November 8, 2017 12:15 at #21 :
I have been working with SolidWorks and other CAE programs in order to develop an accurate dynamic model for TEO, including masses, inertias, CoM. It is not yet finished, but I wonder in which repository this kind of information (probably a .doc or a .pdf file) could be placed into.

There are a number of options on where to centralize this information (namely: teo-configuration-files, teo-hardware-manual, teo-software-manual).

This is argueable, but I currently recommend to create a markdown page (generated via ods2md) similar to this one that got lost in translation as Appendix B of https://github.com/roboticslab-uc3m/teo-software-manual (then upload the .ods to a src folder or similar).

The workflow then would be to update through other repositories (including teo-configuration-files, as well teo-openrave-models etc) that use their own program/library specific formats.

@jgvictores
Copy link
Member

PS: Assigned to @AlvaroMartinezR but there will be a number of future collaborators to propagate the updates through the corresponding repositories. Thanks!

@AlvaroMartinezR
Copy link

Thanks! I will first finish extracting the information and then create a proper document.

@jgvictores
Copy link
Member

Great, thanks!

@jgvictores
Copy link
Member

I've been cleaning https://github.com/roboticslab-uc3m/teo-software-manual so now the workflow and placements are documented at: https://github.com/roboticslab-uc3m/teo-software-manual/blob/master/CONTRIBUTING.md#workflow-for-assets

Hope that helps!

@jgvictores
Copy link
Member

Please note that Workflow and Placements (same rules) are now correctly at https://github.com/roboticslab-uc3m/teo-software-manual/blob/master/README.md#workflow-for-assets

@AlvaroMartinezR
Copy link

I finally obtained all dynamic information about all TEO's parts. SolidWorks provides the information in the following form: (see image below), as a plain text.
image (This comes straight out from SolidWorks, some lines are not usable in TEO's context, so will be edited or deleted)

My main inconvenient is that this kind of information I think it wouldn't fit well on a table similar to point 3 of the workflow. Therefore I think it will be better in a PDF.

@AlvaroMartinezR
Copy link

After talking with Santiago, he told me to upload the info as a PDf in the doc folder of teo-simox-models and link it from the wiki.

@jgvictores
Copy link
Member

The screenshot is not plain text, it's .odt. What is the real output format? Is that copied and pasted?

@AlvaroMartinezR
Copy link

Yes, it copies to your clipboard as plain text, I pasted it on a .ods file because you go piece by piece, so I needed to store the previous ones somewhere.

@jgvictores
Copy link
Member

jgvictores commented Nov 21, 2017 •
edited
Loading

Please add your .odt to the assets/src folder of https://github.com/roboticslab-uc3m/teo-software-manual. It would be great if you could add some lines at the top describing that it came from SolidWorks and link to the model.

After you do that, notify me here and I will proceed to see if pandoc does a good job in exporting .odt to .md. .md has very good properties (better parsed for search, better copied and pasted). Please note that an integrated .pdf is ultimately generated via the enabled GitBook mechanism (see here, the Download PDF button).

@jgvictores
Copy link
Member

PS just because you mentioned .ods even though I got .odt from your screenshot:

  • .odt: Equivalent to Word Document. We'd try pandoc.
  • .ods: Equivalent to Excel Spreadsheet. This tabled format would be even better, and we could use ods2md.

@jgvictores
Copy link
Member

PPS: @AlvaroMartinezR Think you could give it a shot at pasting the parts into an .ods? Perhaps it could work out.

@AlvaroMartinezR
Copy link

Well, dyslexia coming in place: I was all the time referring to .odt. In the meantime I was thinking in using md directly, actually I already started. So if I do it directly I save you this work. I will go for .md then.

@jgvictores
Copy link
Member

So if I do it directly I save you this work. I will go for .md then.

.md is the new black. Three cheers for .md. What else can I say... Thanks! 👍

@jgvictores
Copy link
Member

PD: Would go directly in assets for now. Still looking for a good way to #include one .md in another.

@AlvaroMartinezR
Copy link

Done, created in assets.

@jgvictores
Copy link
Member

Great! Did some renaming at roboticslab-uc3m/teo-developer-manual@b95b219

Still plenty to do to close this issue, just to recap from the top:

@jgvictores
Copy link
Member

jgvictores commented Nov 22, 2017 •
edited
Loading

Also pending to resolve duplicates between https://github.com/roboticslab-uc3m/teo-simox-models and https://github.com/roboticslab-uc3m/teo-software-manual (see roboticslab-uc3m/teo-developer-manual#15)

@jgvictores jgvictores added this to ToDo in [ROBOTICSLAB] Dec 9, 2017
@AlvaroMartinezR
Copy link

@jgvictores Duplicates solved

@jgvictores
Copy link
Member

Still seeing some duplicates:

@AlvaroMartinezR
Copy link

Ups, my mistake, I forgot them 😅.
Which one do you prefer that I delete? @jgvictores

@jgvictores
Copy link
Member

Also did: roboticslab-uc3m/teo-developer-manual@5d2ddb4

@jgvictores
Copy link
Member

Add visibility to dynamic info at roboticslab-uc3m/teo-developer-manual@5ca1cae.

@jgvictores jgvictores mentioned this issue Feb 15, 2018
Open
5 tasks
@jgvictores
Copy link
Member

Started #37 to track unifying link names.

@jgvictores jgvictores added this to In progress in [TEO] Feb 15, 2018
@jgvictores
Copy link
Member

jgvictores commented Feb 15, 2018 •
edited
Loading

Been moving things around. We have https://github.com/roboticslab-uc3m/teo-developer-manual/blob/7d7f7216ecc2e558c65314d4862a3c90cc10a625/appendix/b-teo-dynamic-information.md but I'd also port https://github.com/roboticslab-uc3m/teo-simox-models/blob/551e1dc678eceea9a3ba416d7f584827a244df62/doc/teo-center-of-masses.csv to https://github.com/roboticslab-uc3m/teo-developer-manual/tree/master/assets

@jgvictores jgvictores removed this from ToDo in [ROBOTICSLAB] Apr 4, 2018
@jgvictores jgvictores mentioned this issue Dec 12, 2018
Closed
@jgvictores jgvictores added complexity: tedious Tarea tediosa que nadie quiere hacer and removed complexity: hard labels Dec 12, 2018
@jgvictores jgvictores moved this from In progress to To do in [TEO] Dec 12, 2018
@jgvictores
Copy link
Member

Blocked by #38

@jgvictores jgvictores added the blocked Do not focus on this issue until blocking issue is closed label Dec 12, 2018
@jgvictores jgvictores moved this from To do to Blocked in [TEO] Jan 8, 2019
@jgvictores jgvictores mentioned this issue May 6, 2019
Open
@jgvictores
Copy link
Member

Just for tracking:

@jgvictores
Copy link
Member

Also see: roboticslab-uc3m/teo-configuration-files#17

@jgvictores jgvictores mentioned this issue May 8, 2019
Closed
@jgvictores jgvictores added epic and removed blocked Do not focus on this issue until blocking issue is closed labels May 8, 2019
@jgvictores jgvictores moved this from Blocked to To do in [TEO] May 8, 2019
@jgvictores
Copy link
Member

No longer blocked by #38

@imontesino imontesino pinned this issue Sep 26, 2019
@jgvictores
Copy link
Member

Cool commit: roboticslab-uc3m/teo-developer-manual@7def769

@imontesino
Copy link

Added the absolute values of the centers of masses in roboticslab-uc3m/teo-developer-manual@ce9af81
with respect to the right foot contact with the gound
TEO_joint_twists_numbers

@jgvictores
Copy link
Member

Cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@imontesino imontesino

@AlvaroMartinezR AlvaroMartinezR

Labels
complexity: tedious Tarea tediosa que nadie quiere hacer documentation epic horizontal
Projects
[TEO]
  
To do
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jgvictores @PeterBowman @imontesino @AlvaroMartinezR