Skip to content

Camera movement following#30

Open
Ahelsamahy wants to merge 173 commits intomasterfrom
CameraMovementFollowing
Open

Camera movement following#30
Ahelsamahy wants to merge 173 commits intomasterfrom
CameraMovementFollowing

Conversation

@Ahelsamahy
Copy link
Collaborator

No description provided.

mkbielaw and others added 30 commits January 4, 2024 14:50
Switched to master release without coms and without delay and added following functionality to it
So the movement of controller won't overlap it
It works on both mobile and mouse click. Might change it to work only on phone.

It will send text either stop or start following to Tornado backend
it will send a one time message through TEL chatter with start or stop command along with timestamp
…tion

it will append timestamp to the received command from the front-end and broadcast it through TEL chatter
The docker image is working on python 3.6, CUDA 10.2, pytorch 1.10 and numpy 1.16
Added the throttle control function inside the following branch.
Now the throttle control will not run if following is running, to avoid sending commands at the same time
Ahelsamahy and others added 20 commits May 17, 2024 13:27
New branch without master and .engine
in order to avoid the request sometimes not being registered
teleop working at 80% CPU, following at 10% when standby, 80% when used
there is no need to have two nested loops inside each others
it is used to run profile to measure speed usage by each function. I will send the result to MB
camera movement implemented but not utilized during following
Allowing spinning of the robot if spin = 1 / -1
The robot spins when it's too close to the operator to move forward and if the operator is too close to the edge of the screen, the robot will move the camera and spin
@Ahelsamahy
Copy link
Collaborator Author

Ahelsamahy commented Jun 5, 2024

@mkbielaw please make sure to merge the changes from master branch before you leave this feature

mkbielaw and others added 8 commits June 7, 2024 14:27
Camera will move to keep the user in FOV if the user reaches the edge of the screen. When the position of the user is in the center again, the camera goes to home position and the robot turns to keep the camera look in the same direction.
To split the logic in it
MB didn't remove them when merging from main
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.

3 participants