Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
LRS Development Environment - Common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
lrs
LRS Development Environment - Common
Commits
20ab9b70
Commit
20ab9b70
authored
4 years ago
by
Tommy Persson
Browse files
Options
Downloads
Patches
Plain Diff
Work on doc.
parent
a35dcdb1
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/futurereleases.mf
+82
-0
82 additions, 0 deletions
doc/futurereleases.mf
with
82 additions
and
0 deletions
doc/futurereleases.mf
0 → 100644
+
82
−
0
View file @
20ab9b70
BIG ISSUE: wexec STARTED IN SCREEN DO NOT DIE WHEN SCREEN KILLED WITH C-o \ y
Later you will use screen. Notice that the command key for screen is
here C-o. The screen file are in: waraps/screen
NOTICE: C-o \ do not kill the docker containers. If somebody find out
how to solve this problem pleae let us know.
## Screen Based Approach
NOT ROBUST HANGING PROCESSES. Be aware of the possibility of hanging docker processes.
### Loading configurtion launch files
For each agent you have to load a configuration file and that have to
be done before the screen for the agent is loaded. The arguments to
the config.launch file is location and ns.
Suppose we want to start unit /op0 and /dji0 in Gränsö then we do:
```bash
wexec roslaunch lrs_launch config.launch location:=granso ns:=/op0
wexec roslaunch lrs_launch config.launch location:=granso ns:=/dji0
```
We are not setting kdb to trues since the repo lrs_kdb_base_knowledge is not available.
### Start /op0 using a screen:
```bash
env NS=/op0 screen -c waraps/screen/screen_op
```
This will start the following scripts which starts docker containers:
```bash
wexec roslaunch lrs_launch wdb.launch vehicle:=op ns:=${NS}
wexec roslaunch lrs_launch tst_part.launch ns:=${NS}
wexec_system roslaunch lrs_launch exec_part.launch ns:=${NS}
wexec roslaunch lrs_launch exec_exec.launch ns:=${NS}
```
### Start /dji0 simulation using a screen:
```bash
env NS=/dji0 screen -c waraps/screen/screen_djisim
```
This will start the following scripts which starts docker containers:
```bash
wexec roslaunch lrs_dji_sim sim.launch dynamics:=true mpc:=true inair:=false ns:=/dji0 basic:=false gazebo:=true
wexec roslaunch lrs_launch lrsdji.launch publish_pose:=true ns:=${NS}
wexec roslaunch lrs_launch wdb.launch vehicle:=op ns:=${NS}
wexec roslaunch lrs_launch tst_part.launch ns:=${NS}
wexec roslaunch lrs_launch exec_part.launch ns:=${NS}
wexec roslaunch lrs_launch exec_exec.launch ns:=${NS}
wexec roslaunch lrs_launch exec_vehicle.launch vehicle:=dji ns:=${NS}
```
### Test the two running screens
On the local machine do:
Watch the pose:
```bash
rostopic echo /dji0/pose
```
Takeoff
```bash
wexec rosrun lrs_tst tstcommand.py --takeoff --exec __ns:=/dji0
```
Flyto
```bash
wexec rosrun lrs_tst tstcommand.py --fly -x 100 -y 100 -z 12 --speed 3 --exec __ns:=/dji0
```
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