diff --git a/docs/Scanner/docker/docker_compose.md b/docs/Scanner/docker/docker_compose.md index 3ffc1772..ff446d6d 100644 --- a/docs/Scanner/docker/docker_compose.md +++ b/docs/Scanner/docker/docker_compose.md @@ -16,7 +16,7 @@ To use your own local database, we provide a docker compose recipe that: ### Use pre-built docker image -You can use the pre-built images `romidb` & `plantviewer`, accessible from the ROMI dockerhub, to eaasily test & use the plantviewer with your own database [^3]. +You can use the pre-built images `romidb` & `plantviewer`, accessible from the ROMI dockerhub, to easily test & use the `plant 3d explorer` with your own database [^3]. [^3]: https://docs.docker.com/compose/compose-file/#image diff --git a/docs/Scanner/docker/index.md b/docs/Scanner/docker/index.md index f2a4c56f..9ed8bea6 100644 --- a/docs/Scanner/docker/index.md +++ b/docs/Scanner/docker/index.md @@ -11,17 +11,16 @@ We hereafter list the docker containers, their availability and provides link to - [ ] **plantimager** is not available yet and explanations [there](plantimager_docker.md) - [ ] **plantinterpreter** is not available yet and explanations [there](plantinterpreter_docker.md) - [ ] **virtualplantscanner** is not available yet and explanations [there](virtualplantimager_docker.md) - - [x] **plantviewer** is available [here](https://hub.docker.com/repository/docker/roboticsmicrofarms/plantviewer) and explanations [there](plantviewer_docker.md) + - [x] **plantviewer** is available [here](https://hub.docker.com/repository/docker/roboticsmicrofarms/plantviewer) and explanations [there](plant3dexplorer_docker.md) ## Use cases with docker-compose In this section we reference the "real-life" use cases of our software. -### Use the plantviewer on a local database directory +### Use the plant 3d explorer on a local database directory To easiest way to use the plantviewer on a local database directory without installing the ROMI libraries (and their dependencies) is to use the pre-built docker image and add a docker-compose YAML recipe. See [here](docker_compose.md#database--plantviewer) for more details. - ## DockerHub ### roboticsmicrofarms diff --git a/docs/Scanner/docker/plantviewer_docker.md b/docs/Scanner/docker/plant3dexplorer_docker.md similarity index 86% rename from docs/Scanner/docker/plantviewer_docker.md rename to docs/Scanner/docker/plant3dexplorer_docker.md index 6d98cfac..ffcd4449 100644 --- a/docs/Scanner/docker/plantviewer_docker.md +++ b/docs/Scanner/docker/plant3dexplorer_docker.md @@ -1,4 +1,4 @@ -Docker container for ROMI plantviewer +Docker container for ROMI `plant 3d explorer` ===================================== The plant visualizer is a webapp that dialog with the database to display images & some quantitative traits. @@ -24,11 +24,11 @@ To create a local ROMI database: * python package install, look [here](../install/romidb_setup.md). * `romidb` docker image, look [here](romidb_docker.md). -* docker-compose YAML recipe (start both a `romidb` & a `plantviewer` docker image connected to the db), look [here](docker_compose.md). +* docker-compose YAML recipe (start both a `romidb` & a `plant 3d explorer` docker image connected to the db), look [here](docker_compose.md). ## Use pre-built docker image -You can easily download and start the pre-built `plantviewer` docker image with: +You can easily download and start the pre-built `plant 3d explorer` docker image with: ```bash docker run -p 3000:3000 roboticsmicrofarms/plantviewer:$VTAG ``` @@ -43,7 +43,7 @@ docker run --env REACT_APP_API_URL='0.0.0.0' -p 3000:3000 roboticsmicrofarms/pla [^1]: https://docs.docker.com/engine/reference/commandline/run/#set-environment-variables--e---env---env-file ## Build docker image -To build the image, from the `3d-plantviewer` root directory, run: +To build the image, from the `plant 3d explorer` root directory, run: ```bash export VTAG="latest" docker build -t roboticsmicrofarms/plantviewer:$VTAG . diff --git a/docs/Scanner/install/index.md b/docs/Scanner/install/index.md index 56836179..0e522296 100644 --- a/docs/Scanner/install/index.md +++ b/docs/Scanner/install/index.md @@ -10,7 +10,7 @@ In the following subsections we will details how to install ROMI software for a 0. Plant scans acquisition using the ROMI plant scanner to a database [here](plant_imager_setup.md). 0. Plant reconstruction pipelines from existing plant scans in a database [here](plant_reconstruction_setup.md). 0. Virtual plant creation (3D modelling of plant architecture with LPY), virtual scan (mimic plant scanner with blender) & reconstruction (same as 2.) [here](virtual_plant_setup.md). -0. Create a web server hosting the plantviewer GUI [here](visualizer_setup.md). +1. Create a web server hosting the plant 3d explorer GUI [here](./plant3dexplorer_setup.md). !!!note You can find **docker images** for use cases #1, #3 & #5 in the dockerhub repository of the ROMI project [here](https://hub.docker.com/orgs/roboticsmicrofarms/repositories). diff --git a/docs/Scanner/install/visualizer_setup.md b/docs/Scanner/install/plant3dexplorer_setup.md similarity index 76% rename from docs/Scanner/install/visualizer_setup.md rename to docs/Scanner/install/plant3dexplorer_setup.md index 0a2867d8..f1bc60ad 100644 --- a/docs/Scanner/install/visualizer_setup.md +++ b/docs/Scanner/install/plant3dexplorer_setup.md @@ -1,16 +1,16 @@ -Install ROMI software for virtual plants acquisition & reconstruction +Install the ROMI `Plant 3d explorer` ===================================================================== To follow this guide you should have a `conda` environment, see [here](create_env.md). -For the sake of clarity it will be called `plant_visualizer`. +For the sake of clarity it will be called `Plant 3d explorer`. !!! note - If you do not want the hassle of having to create environment & install python libraries, there is a pre-built docker image, with usage instructions [here](../docker/plantviewer_docker.md). + If you do not want the hassle of having to create environment & install python libraries, there is a pre-built docker image, with usage instructions [here](../docker/plant3dexplorer_docker.md). ## Pre-requisite -The plantviewer relies on: +The `Plant 3d explorer` relies on: - `node` - `npm` @@ -40,17 +40,17 @@ npm install ``` -## Use the plantviewer +## Use the `Plant 3d explorer` ### With the official ROMI database -You can use the ROMI database to test the installation of the plantviewer: +You can use the ROMI database to test the installation of the `Plant 3d explorer`: ```bash export REACT_APP_API_URL='https://db.romi-project.eu' npm start ``` ### With a runnning local database -If you have followed the install instructions of the ROMI database ([here](romidb_setup.md)), you can use it with the viewer: +If you have followed the install instructions of the ROMI database ([here](romidb_setup.md)), you can use it with the `Plant 3d explorer`: ```bash export REACT_APP_API_URL='0.0.0.0' npm start diff --git a/docs/Scanner/install/romidb_setup.md b/docs/Scanner/install/romidb_setup.md index 1dee2e82..58bb01a3 100644 --- a/docs/Scanner/install/romidb_setup.md +++ b/docs/Scanner/install/romidb_setup.md @@ -29,7 +29,6 @@ python3.7 -m pip install flask flask-restful flask-cors && \ python3.7 -m pip install . ``` - ## Initialize a ROMI database The `FSDB` class from the `romidata` module is used to manage a local file system for data storage. diff --git a/docs/Scanner/tutorials/plant-3d-explorer.md b/docs/Scanner/tutorials/plant-3d-explorer.md new file mode 100644 index 00000000..781a81fa --- /dev/null +++ b/docs/Scanner/tutorials/plant-3d-explorer.md @@ -0,0 +1,186 @@ +How to see directly the results of your plant phenotyping with the `plant-3d-explorer` ? +================================ + +## Objective +Throughout the whole process of plant phenotyping, viewing data is often needed. +This tutorial explains how to use the romi `plant-3d-explorer`, a web-server tool, to explore, display and interact with most of the diverse data generated during a typical plant phenotyping experiment from 2D images (2D images, 3D objects like meshes or point cloud, quality evaluations, trait measurements). +After this tutorial, you should be able to: +* connect the plant-3d-explorer to a database containing the phenotyping data of one to several plants ; +* explore the database content with the `plant-3d-explorer` menu page ; +* For each plant, display, overlay and inspect in 3d every data generated during analysis + +## Prerequisite +* install romi `plant-3d-explorer` (from [source](https://github.com/romi/plant-3d-explorer) or using a [docker image](../docker/plant3dexplorer_docker.md) ) & read [install procedure](../install/plant3dexplorer_setup.md) +* install romi `plantdb` (from [source](https://github.com/romi/plantdb) or using a [docker image](../docker/romidb_docker.md)) & read [install procedure](../install/romidb_setup.md) +* install romi `plant-3d-vision` (from [source](https://github.com/romi/plant-3d-vision) or using a [docker image](../docker/plantinterpreter_docker.md)) & read [install procedure](../install/plant_reconstruction_setup.md) +* Create and activate isolated python environment (see the procedure [here](/docs/Scanner/install/create_env.md) ) + +!!! note + using **docker** + docker_logo + + You can avoid installs by using **docker** only. Read first the docker procedures ( ['docker for plant-3d-vision'](../docker/plantinterpreter_docker.md) and + ['docker-compose to run both database and 3d explorer with docker containers'](../docker/docker_compose.md) ). In the following tutorial (steps 1, 2 and 3), follow the docker logo to adapt the procedure. + +## Linked documentation +* [Manual of the romi plant-3d-explorer](/docs/plant_3d_explorer/index.md) + +## Step-by-step tutorial +Principle: the `plant-3d-explorer` is a web client that displays in your favorite web browser data exposed by a server (here, romi `plantdb`) on a particular url. The process consists in pointing the server to your folder of interest, starting the server and starting the client that points to the served url. + +!!!note + the `plant-3d-explorer` has only been developed and tested on Chrome. + + +### 1. Preparing your database for display by the `plant-3d-explorer` +**Starting point:** your *database* is made of one or several *datasets*, which all correspond to a single plant phenotyping experiment: each dataset contains at least 2D images (raw acquisitions) and metadata, and possibly several other data generated by subsequent 3D reconstruction, segmentation and analysis. + +!!! Note + + Your database must follow the rules of romi databases: please make sure that you comply to [requirements](../install/romidb_setup/#initialize-a-romi-database). + + You can also download an example database [here](https://db.romi-project.eu/models/test_db.tar.gz). + +*example*: let's consider a database called `my_experiment` containing 3 datasets (named plant1, plant2, plant3) generated by phenotyping three plants. + +* open a terminal and go to your local database directory +* if romi commands (like `romi_run_task`) are not accessible from your terminal, activate the appropriate python environment (e.g. using venv or conda) required for romi commands (or [read this procedure](../install/create_env.md)) +* Process all datasets for display by the `plant-3d-explorer` by running the following code + +```bash +dataset_list=('plant1','plant2','plant3') + +for ds in "${dataset_list[@]}" +do + romi_run_task Visualization path_to/my_experiment/"$ds"/ --config ~/config/ml_pipe_real.toml +done +``` +!!! Note + For more information about using romi_run_task command, the Visualization task and the config file, please read XXXXX. + +!!! Note + docker_logo *for docker users* + + - Start a docker container by mounting your database as a volume ([details](../docker/plantinterpreter_docker.md/#manually)) + + - In the container, run the same Visualization Task has above + +**check result**: a new folder called `Visualization` should have been created in each dataset of your database + +!!! Note + docker_logo *for docker users* + + Skip step 2 & 3 and follow instead instructions given by['docker-compose to run both database and 3d explorer with docker containers'](../docker/docker_compose.md) + +### 2. Connect your database to a local server +- Continue in the same shell terminal (if you open a new terminal, do not forget to activate appropriate python environment) +- set the DB location using the `DB_LOCATION` environment variable +- Type the following commands to launch the server: +```bash +export DB_LOCATION=/path/to/your/db +romi_scanner_rest_api #command that starts the server +``` +**check result**: the terminal prints various information given by the server (e.g. number of datasets in the database). Do not stop this terminal as this will shut down the server + +### 3. Connect the `plant-3d-explorer` to the server +- Open a new terminal +- go to your local cloned directory of `plant-3d-explorer/` +- start the frontend visualization server by entering: +```bash +npm start +``` +You should now be able to access the `plant-3d-explorer` on [http://localhost:3000](http://localhost:3000). Depending on you system preferences, your default web browser may automatically open a window displaying the server content. if not, open your web browser and enter [http://localhost:3000](http://localhost:3000) in the url bar. + +!!! note + You need to add a file `.env.local` at project's root to set the API URL: ```REACT_APP_API_URL='{`API URL}'```. + Without this, the app will use: http://localhost:5000 which is the default for `romi_scanner_rest_api`. + +### 4. Explore your database content via the menu page + +!!! note + More description about the function of the menu page: read [here](/docs/plant-3d-explorer/index.md) + +The starting page of the `plant-3d-explorer` lists the datasets of the connected database as a table and looks like this: + + + plant3dexplorer_menupage + + + * The top search bar allows you to find particular datasets based on keywords. + * Data filters: in the header row, click on an icon to activate the filter (datasets that do *not* contain the data will be filtered out) + + * availdata 3d objects generated from the plant 2D images (icons respectively stand for: mesh, point cloud, segmented point cloud, skeleton and organs) + + * phyllofilter or phyllotaxis data (manual or computed phyllotaxis measurements) + + * Open a dataset with the green 'Open' button at the far right of a row openbutton + + +### 5. View a single dataset and all related data + +!!! note + This is only a brief description to allow a quick start. More description [here](/docs/plant-3d-explorer/index.md) + +By default, the `plant-3d-explorer` displays in the main panel the skeleton and the organs (if available) and phyllotaxis data (as graphs) in the right panel. + + + plant3dexplorer_dataset_initpage + + +Mouse-over most elements provides a brief description. + +#### Select the 3D layers to display +In the top left corner of the main panel, icons allows you to quickly (un)select 3D layers (if available): + +plant3dexplorer_dataset_initpage + +* White icons are active, dark grey are available but not active, light grey are not available for this dataset +* From left to right, icons represents respectively the mesh, the pointcloud, the segmented point cloud, the skeleton and the organs. + + +In the center of the middle panel are icons for general viewing options: +plant3dexplorer_view-icons.png + +* Activate the camera icon displays the camera poses (only works if overlay with 2 images is deactivated) +* Click the round arrow to reset the view + +#### Moving the view in the "free" 3D (without 2D overlay) +Easy movements are accessible with a mouse: + +* scroll to zoom in/out +* left click rotate +* right click translate + +#### Activate overlay with 2D images +click on any image of the bottom carousel to activate the display of 2 images in the main panel. On Mouse-over, a single picture is enlarged and proposes to open it in the main panel. + +plant3dexplorer_view-icons.png + +Overlay with active 3D layers is automatic. In the carousel, the box around the active displayed 2D image is now permanent. + +To close the 2D overlay, just click the close button of the boxed picture in the carousel. + +plant3dexplorer_view-icons.png + +#### Moving the view with 2D overlay +Note that movement control with the mouse slightly changes compared to the "free" view without 2D overlay. Notably, the free rotation mode is not possible anymore, since it is constrained by the real movements made by the camera when it took the pictures. + +* Slide right/left the active box picture in the carousel to reproduce the camera movement +* scroll to zoom in/out +* left-click to translate + +#### The phyllotaxis measure plots +Plots represent the successive measures of divergence angles (left, in degrees) and internode length (right, in mm) between consecutive pairs of organs (here fruits) along the stem, from the base to the inflorescence tip. Both plots can be closed by clicking the cross at the far right the plot's title. Closed plot panels can be re-opened by clicking a green "+" sign appearing at the to right-hand corner when at least one plot is closed. + +Mouse-over any of the two plots highlights an interval that correspond to a measure between two consecutive organs segmented by the analysis. The interval appears synchronously on both plots if opened. This interval and the organs are numbered by their order from the base of the stem, these numbers appear on the X-axis of the plots. + +When the 'organ' 3d-layer is activated in the main panel, +automatically select the organ pair in the main panel that correspond to the current interval pointed by the mouse in the graph (the 3d layer of other organs disappear). The two graphs (divergence angles and internodes) are synchronized. + +clicking an interval + +#### Go back to main page +In the top left corner of the page, click "all scans" + +backtomenu + diff --git a/docs/Scanner/tutorials/visualizer.md b/docs/Scanner/tutorials/visualizer.md deleted file mode 100644 index 93a077e1..00000000 --- a/docs/Scanner/tutorials/visualizer.md +++ /dev/null @@ -1,51 +0,0 @@ -How to use the ROMI plantviewer? -================================ - -## Ready to run docker image -To use a ready to run docker image pointing toward the `db.romi-project.eu`, look [here](../docker/plantviewer_docker.md). - -!!! note - This requires `docker-ce` to be installed on your machine. - - -## Running a development server for the visualizer - -Set the DB location using the `DB_LOCATION` environment variable and launch the flask server: -```bash -export DB_LOCATION=/path/to/the/db -romi_scanner_rest_api -``` -Finally, start the frontend visualization server (from `3d-plantviewer/` folder): -```bash -npm start -``` -You should now be able to access the visualizer on [http://localhost:3000](http://localhost:3000). - -!!! note - You need to add a file `.env.local` at project's root to set the API URL: - ```REACT_APP_API_URL='{`API URL}'``` - - Without this, the app will use: http://localhost:5000 which is the default for `romi_scanner_rest_api`. - -## Preparing your database -To access the data from your running DB (`` from ``) -```bash -dataset_list=('2018-12-17_17-05-35' '2018-12-18_13-14-57' '2018-12-20_13-21-24' '2019-01-29_16-56-01' '2019-02-01_10-56-34') - -for ds in "${dataset_list[@]}" -do - romi_run_task Visualization ~/db_test/"$ds"/ --config ~/config/ml_pipe_real_2.toml --local-scheduler -done -``` - - -## Running a production server for the visualizer - -!!! warning - This is not tested yet! - - -## Visualizer API reference - -!!! warning - Not too many details here, I like it! \ No newline at end of file diff --git a/docs/assets/images/ext/docker_logo2.png b/docs/assets/images/ext/docker_logo2.png new file mode 100644 index 00000000..de9a275f Binary files /dev/null and b/docs/assets/images/ext/docker_logo2.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_3dlayers_icons.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_3dlayers_icons.png new file mode 100644 index 00000000..8054b6f8 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_3dlayers_icons.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_allscans_backmenu.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_allscans_backmenu.png new file mode 100644 index 00000000..869e6de2 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_allscans_backmenu.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_availabledata.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_availabledata.png new file mode 100644 index 00000000..f581ab7a Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_availabledata.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-close.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-close.png new file mode 100644 index 00000000..84c6e736 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-close.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-open.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-open.png new file mode 100644 index 00000000..fb4c13f6 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_carousel-open.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_dataset_initpage.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_dataset_initpage.png new file mode 100644 index 00000000..8ea8e105 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_dataset_initpage.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_menupage.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_menupage.png new file mode 100644 index 00000000..a3dd4156 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_menupage.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_openbutton.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_openbutton.png new file mode 100644 index 00000000..57fd6925 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_openbutton.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_phyllotaxisfilter.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_phyllotaxisfilter.png new file mode 100644 index 00000000..0b362fb8 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_phyllotaxisfilter.png differ diff --git a/docs/assets/images/plant-3d-explorer/plant3dexplorer_view-icons.png b/docs/assets/images/plant-3d-explorer/plant3dexplorer_view-icons.png new file mode 100644 index 00000000..92b06a23 Binary files /dev/null and b/docs/assets/images/plant-3d-explorer/plant3dexplorer_view-icons.png differ diff --git a/docs/Visualizer/guide.md b/docs/plant-3d-explorer/guide.md similarity index 99% rename from docs/Visualizer/guide.md rename to docs/plant-3d-explorer/guide.md index 54b9fa16..0f8b87ef 100644 --- a/docs/Visualizer/guide.md +++ b/docs/plant-3d-explorer/guide.md @@ -1,5 +1,4 @@ ## The scan list page - When first opening the app, you will be greeted with a home page displaying every available scans. A scan is defined as a folder containing acquisition of plant data (e.g. 2D RGB images, manual measures) and a set of 3D reconstructions and analysis (e.g. point cloud, mesh, automated measures,...) diff --git a/docs/Visualizer/index.md b/docs/plant-3d-explorer/index.md similarity index 100% rename from docs/Visualizer/index.md rename to docs/plant-3d-explorer/index.md diff --git a/mkdocs.yml b/mkdocs.yml index 149e2f7f..2768c721 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -49,16 +49,14 @@ nav: - 'Plant imager software setup': 'Scanner/install/plant_imager_setup.md' - 'Virtual plants scanner software setup': 'Scanner/install/virtual_plant_setup.md' - 'Plant reconstruction software setup': 'Scanner/install/plant_reconstruction_setup.md' - - 'Visualizer software setup': 'Scanner/install/visualizer_setup.md' + - 'plant-3d-explorer software setup': 'Scanner/install/plant3dexplorer_setup.md' - 'Tutorials': - 'Home': 'Scanner/tutorials/index.md' - 'Basics': 'Scanner/tutorials/basics.md' - 'Plant imaging': 'Scanner/tutorials/hardware_scan.md' - 'Virtual scanner': 'Scanner/tutorials/virtual_scan.md' - 'Scan reconstruction': 'Scanner/tutorials/reconstruct_scan.md' - - 'Visualizer': 'Scanner/tutorials/visualizer.md' - - 'Explanations': - - 'Segmentation of images': 'Scanner/explanations/segmentation.md' + - 'plant-3d-explorer: view your data': 'Scanner/tutorials/plant-3d-explorer.md' - 'How-to': - 'Home': 'Scanner/how_to/index.md' - 'Import external ressources': 'Scanner/how_to/import_files.md' @@ -94,12 +92,12 @@ nav: - 'Plant Imager': 'Scanner/docker/plantimager_docker.md' - 'Virtual Plant Scanner': 'Scanner/docker/virtualplantscanner_docker.md' - 'Plant Interpreter': 'Scanner/docker/plantinterpreter_docker.md' - - 'Plant Viewer': 'Scanner/docker/plantviewer_docker.md' + - 'plant-3d-explorer': 'Scanner/docker/plant3dexplorer_docker.md' - 'Docker compose': 'Scanner/docker/docker_compose.md' - 'Build romicscan docker for developers': 'Scanner/docker/docker_dev_build.md' - - 'Visualizer': - - 'Home': 'Visualizer/index.md' - - 'Guide': 'Visualizer/guide.md' + - 'plant-3d-explorer': + - 'Home': 'plant-3d-explorer/index.md' + - 'Guide': 'plant-3d-explorer/guide.md' - 'Research': 'research.md' - 'Data': 'data.md'