You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy/monai-deploy-express/README.md
+53-21Lines changed: 53 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,13 +49,23 @@ The [Docker compose file](docker-compose.yml) spins up the following services. S
49
49
Execute one of the following commands in the directory where the `docker-compose.yml` resides to start, stop all the services or to view the logs.
50
50
51
51
```bash
52
-
docker compose up # start all services
52
+
docker compose up # start MONAI Deploy Express
53
53
docker compose up -d # or run detached
54
54
docker compose logs -t -f # view output from all containers
55
55
docker compose down # stop all services
56
56
```
57
57
58
-
The first time calling `docker compose up` may take longer as it needs to pull all the container images. However, once all container images are pulled and available on the local system, all the services should spin up within 20 to 60 seconds.
58
+
Use the following commands to launch MONAI Deploy Express with ELK (ElasticSearch-LogStash-Kibana):
59
+
60
+
```bash
61
+
./init.sh # required to setup Elastic volume mapping permissions on Linux
docker compose --profile elk up -d # or run detached
64
+
docker compose logs -t -f # view output from all containers
65
+
docker compose --profile elk down # stop all services
66
+
```
67
+
68
+
The first time calling `docker compose up` may take longer as it needs to pull all the container images. However, once all container images are pulled and available on the local system, all the services should spin up between 20 to 65 seconds.
59
69
60
70
### MONAI Deploy Services
61
71
@@ -75,6 +85,9 @@ The first time calling `docker compose up` may take longer as it needs to pull a
*Note: Orthanc is included for convenience and to demo end-to-end workflow execution. It may be disabled and have MONAI Deploy Express integrated with external Orthanc, PACS or other DICOM devices.*
80
93
@@ -166,12 +179,17 @@ This example uses the `alpine` container image instead of a MAP to print all fil
166
179
In this section, we will download a DICOM dataset, upload it to Orthanc and then run the [Liver Segmentation MAP](https://github.com/Project-MONAI/monai-deploy-app-sdk/tree/main/examples/apps/ai_livertumor_seg_app) from the
167
180
[MONAI Deploy App SDK](https://github.com/Project-MONAI/monai-deploy-app-sdk). Finally, we can expect the AI-generated segmentation result to appear in Orthanc.
168
181
182
+
169
183
#### Steps
170
184
171
185
1. Download the [Abdomen CT dataset](#running-a-monai-deploy-workflow) dataset
172
-
2. Upload the dataset as described in [Uploading Data](#upload-dicom-datasets)
173
-
3. Deploy the workflow definition to MONAI Deploy Workflow Manager:
5. Navigate to Orthanc, select any study and then click *Send to DICOM Modality* from the menu on the left.
203
+
6. Navigate to Orthanc, select any study and then click *Send to DICOM Modality* from the menu on the left.
186
204
In the popup dialog, select **MONAI-DEPLOY** to start a C-STORE request to the Informatics Gateway.
187
-
6. Wait for the workflow to complete; the entire workflow takes roughly one minute and thirty seconds to complete. To see the AI-generated segmentation object, reload the Orthanc study page.
188
-
7. To see the output of the container, run the following commands:
205
+
7. Wait for the workflow to complete; the entire workflow takes roughly one minute and thirty seconds to complete. To see the AI-generated segmentation object, reload the Orthanc study page.
206
+
8. To see the output of the container, run the following commands:
189
207
```bash
190
208
> docker container list -a | grep monai_ai_livertumor_seg_app
191
209
# locate the container ID and run the following
@@ -202,9 +220,13 @@ In this section, we will download a DICOM dataset, upload it to Orthanc and then
202
220
#### Steps
203
221
204
222
1. Download the [Chest CT dataset](#running-a-monai-deploy-workflow) dataset
205
-
2. Upload the dataset as described in [Uploading Data](#upload-dicom-datasets)
206
-
3. Deploy the workflow definition to MONAI Deploy Workflow Manager:
5. Navigate to Orthanc, select any study and then click *Send to DICOM Modality* from the menu on the left.
240
+
6. Navigate to Orthanc, select any study and then click *Send to DICOM Modality* from the menu on the left.
219
241
In the popup dialog, select **MONAI-DEPLOY** to start a C-STORE request to the Informatics Gateway.
220
-
6. Wait for the workflow to complete; the entire workflow takes roughly one minute to complete. To see the AI-generated segmentation object, reload the Orthanc study page.
221
-
7. To see the output from the container, run the following commands:
242
+
7. Wait for the workflow to complete; the entire workflow takes roughly one minute to complete. To see the AI-generated segmentation object, reload the Orthanc study page.
243
+
8. To see the output from the container, run the following commands:
222
244
```bash
223
245
> docker container list -a | grep monai_ai_lung_seg_app
224
246
# locate the container ID and run the following
@@ -230,9 +252,14 @@ In this section, we will download a DICOM dataset, upload it to Orthanc and then
230
252
In the `liver-lung-seg.json` workflow definition, we combined the AI Lung MAP and the AI Liver MAP into one single workflow definition. With this workflow definition, the Workflow Manager would route the incoming data based on the routing rules defined.
231
253
232
254
1. Download one or both of the [datasets](#running-a-monai-deploy-workflow) provided above
233
-
2. Upload the dataset as described in [Uploading Data](#upload-dicom-datasets)
234
-
3. Deploy the workflow definition to MONAI Deploy Workflow Manager:
235
-
4.
255
+
2. Download the AI Liver Tumor & the AI Lung Segmentation MAPs
5. Navigate to Orthanc, select one of the studies and then click *Send to DICOM Modality* from the menu on the left.
273
+
6. Navigate to Orthanc, selectone of the studies and then click *Send to DICOM Modality* from the menu on the left.
247
274
In the popup dialog, choose **MONAI-DEPLOY** to start a C-STORE request to the Informatics Gateway.
248
-
6. Wait for the workflow to complete and reload the Orthanc study page and expect a new series to be added.
249
-
7. To see the output from the container, run the following commands:
275
+
7. Wait for the workflow to complete and reload the Orthanc study page and expect a new series to be added.
276
+
8. To see the output from the container, run the following commands:
250
277
```bash
251
278
> docker container list -a | grep monai_ai_
252
279
# locate the container ID and run the following
253
280
> docker logs {CONTAINER ID}
254
281
```
255
-
8. Repeat the steps with the other dataset.
282
+
9. Repeat the steps with the other dataset.
256
283
257
284
In this example, the [Chest CT dataset](https://drive.google.com/file/d/1IGXUgZ7NQCwsix57cdSgr-iYErevqETO/view?usp=sharing) should only launch the AI Lung MAP, while the [Abdomen CT dataset](https://drive.google.com/file/d/1d8Scm3q-kHTqr_-KfnXH0rPnCgKld2Iy/view?usp=sharing) would launch the AI Liver MAP.
258
285
286
+
## Using Kibana
287
+
288
+
A default dataview is imported to Kibana at startup. To load the saved search, navigate to http://localhost:5601/, click on Analytics > Discover from the 🍔 menu. From the top right click *Open* and select*MONAI-Default*.
289
+
290
+
259
291
## Tips
260
292
261
293
- If you are using your DICOM dataset, please remove the router task or modify the routing conditions to meet your needs.
0 commit comments