Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
U
ur_simple_control
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Marko Guberina
ur_simple_control
Commits
2f26f254
Commit
2f26f254
authored
9 months ago
by
m-guberina
Browse files
Options
Downloads
Patches
Plain Diff
just added 2 todos
parent
67a162a6
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
4
Show whitespace changes
Inline
Side-by-side
Showing
4 changed files
README.md
+2
-0
2 additions, 0 deletions
README.md
TODOS_2024-03-23
+5
-7
5 additions, 7 deletions
TODOS_2024-03-23
python/README.md
+2
-0
2 additions, 0 deletions
python/README.md
python/examples/point_impedance_control.py
+0
-1
0 additions, 1 deletion
python/examples/point_impedance_control.py
with
9 additions
and
8 deletions
README.md
+
2
−
0
View file @
2f26f254
...
...
@@ -87,6 +87,8 @@ Here is a checklist of what to do together with the key remarks.
files to make clutter and cause confusion.
-
the pyproject.toml actually brakes local install so i'm just keeping it out for now. sweet jesus
what a mess
-
instead of using a debug argument and ifs for prints,
use built-in python logging
#TODO: write instruction for extending the library to new robots
-------------
...
...
This diff is collapsed.
Click to expand it.
TODOS_2024-03-23
+
5
−
7
View file @
2f26f254
in order of priority
--------------------
1. real-time plotting (need to see what's happening as it's happening,
this is here primarily to aid in debugging)
---> have a list of what's possible to plot and then select what's selected
2. debug dmp end-of-trajectory shennanigans
3. implement compliantMoveL
4. fix getMarkerOffset
this is here primarily to aid in debugging)
- DONE
---> have a list of what's possible to plot and then select what's selected
- TODO make logging smoother and uniform accross code
2. debug dmp end-of-trajectory shennanigans
- DONE (at least mostly)
3. implement compliantMoveL
- DONE
4. fix getMarkerOffset
- DONE
5. add waypoints to marker pick up
6. fix anything that looks problematic in drawing
7. switch to robot_manager.step() to ensure you're not double-computing things
8. implement cartesian dmp
9. faster visualizing (process in a different thread)
This diff is collapsed.
Click to expand it.
python/README.md
+
2
−
0
View file @
2f26f254
...
...
@@ -17,6 +17,8 @@ so not terribly convenient. it will get fixed in a future ur_rtde release tho
this to work than to re-do the same functionality from scratch.
and you won't really be using it too much anyway let's be real. AND ALSO,
if you ditch your shitty integration for pinocchio's it will be faster.
-
use logging instead of a debug flag (you're reinventing the wheel and it's also ugly)
-
add types to everything, check them with mypy
# installation
------------
...
...
This diff is collapsed.
Click to expand it.
python/examples/point_impedance_control.py
+
0
−
1
View file @
2f26f254
...
...
@@ -255,7 +255,6 @@ def controlLoopPointImpedance(q_init, controller, robot, i, past_data):
# TODO: implement
def
controlLoopCartesianPointImpedance
(
Mtool_init
,
clik_controller
,
robot
,
i
,
past_data
):
breakFlag
=
False
# TODO rename this into something less confusing
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment