---
# System prepended metadata

title: Untitled

---

## Possible git repo structure

Discussion mono-repo vs multiple repos. My suggestion is to use 2 repos. 1 repo contains all our code we need for our users. The other repo we use to train and experiment with our SLAM/ArCore/ML code. For example the code to train e.g. DELF goes into research, the trained model is then used in the "user" repo. 

### Suggestion for the frontend facing repo
```bash
.
|
├── README.md
├── rendering
├── tracking #arcore code, optimized relocalization
├── ui_components
|    ├── example_ar_view
|    ├── example_user_profile
|    ├── example_login
├── flutter_common
|    ├── example_network_requests
|    ├── example_compute_id
├── app #standard flutter structure
├── web_app #AR Editor, user interal space (profile etc.)
├── server

```

### Suggestion for "research" repo
```bash 
.
|
├── README.md
├── research #Everything we try, if we don't use something any more push it to branch deprecated and delete here
├── production
|    ├── example_delg
|    ├── example_user_recommendations
|    ├── example_anomaly_detection
├── datasets
|    ├── example_gldv2
|    ├── example_data_augmentation
├── utilities
|    ├── example_tflite_converter
|    ├── example_create_benchmarks
├── trained_models
```