Skip to content

Commit

Permalink
Fix env setup
Browse files Browse the repository at this point in the history
  • Loading branch information
nachovizzo committed Mar 29, 2021
1 parent 830324e commit 4d258f4
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 5 deletions.
2 changes: 0 additions & 2 deletions .env

This file was deleted.

10 changes: 9 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ install [docker][docker] and [docker-compose][compose].
If you **don't want to use docker** and install `puma` locally you might want
to visit the [Installation Instructions](./INSTALL.md)

### 1) Datasets
### 1) Setting up the environment

First, you need to indicate where are all your datasets, for doing so just:

Expand All @@ -61,6 +61,14 @@ So far we've only tested our approach on the [KITTI Odometry
benchmark][kitti] dataset and the [Mai city dataset][mai-city]. Both
datasets are using a 64-beam Velodyne like LiDAR.

Then you need to expose your `user id` and `group id` to have access to the
artifacts of the pipelines:

```sh
export UID
export GID
```

### 2) Converting from `.bin` to `.ply`

All our apps use the [PLY][ply] which is also binary but has much
Expand Down
4 changes: 2 additions & 2 deletions docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ services:
context: .
dockerfile: docker/apps/Dockerfile
args:
USER_ID: ${USER_ID:-0}
GROUP_ID: ${GROUP_ID:-0}
USER_ID: ${UID:-1000}
GROUP_ID: ${GID:-1000}
working_dir: /apps
volumes:
- ./apps/:/apps:rw
Expand Down

0 comments on commit 4d258f4

Please sign in to comment.