Array3022 commited on
Commit
80310dd
1 Parent(s): ffa1bce

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +4 -4
README.md CHANGED
@@ -12,11 +12,11 @@ pinned: false
12
 
13
  Configuration reference: https://huggingface.co/docs/hub/spaces-config-reference
14
 
15
- ### Supplementary Scripts
16
 
17
  The `PubMedTM-Scripts.zip` file is a directory of additional scripts and functions written during the development of the GUI tool. The file includes the scripts used to clean and process the data as well as experimental work on network analysis and lexical bundle extraction. Many of these scripts are experimental or incomplete, but they might be a good starting point if you want to analyze the data further.
18
 
19
- ### Local Install
20
 
21
  For optimal performance, run this application on a computer with a performant CPU and at least 16GB of RAM. Using Dev Containers within Visual Studio Code (VS Code) is the easiest way to run the application locally. To get started, follow [this](https://code.visualstudio.com/docs/devcontainers/tutorial) tutorial until the "Check Installation" step.
22
 
@@ -26,7 +26,7 @@ Once you've downloaded the files, open the folder containing the files in VS Cod
26
 
27
  Wait for the container to build and install the requirements. This could take five to ten minutes depending on the internet connection and hardware. Once the container is ready, run the application by typing `streamlit run 01_Introduction.py` in the terminal at the bottom of VS Code. The application should open in your default browser automatically.
28
 
29
- # Troubleshooting
30
 
31
- - If the container fails to build, look for a part of the error message that says `"bind": bind source path does not exist:` then delete the `wayland-0` and `wayland-0.lock` files in the path specified by that portion of the error. On a default Ubuntu installation, the path is `/run/user/1000/wayland-0`. This advice is taken from [here](https://dev.to/crumdev/vscode-dev-container-failing-to-build-ap4).
32
  - If the app starts to run in the Dev Container but spontaneously kills itself, increase the maximum RAM and SWAP allocations in the Docker Desktop application settings.
 
12
 
13
  Configuration reference: https://huggingface.co/docs/hub/spaces-config-reference
14
 
15
+ # Supplementary Scripts
16
 
17
  The `PubMedTM-Scripts.zip` file is a directory of additional scripts and functions written during the development of the GUI tool. The file includes the scripts used to clean and process the data as well as experimental work on network analysis and lexical bundle extraction. Many of these scripts are experimental or incomplete, but they might be a good starting point if you want to analyze the data further.
18
 
19
+ # Local Install
20
 
21
  For optimal performance, run this application on a computer with a performant CPU and at least 16GB of RAM. Using Dev Containers within Visual Studio Code (VS Code) is the easiest way to run the application locally. To get started, follow [this](https://code.visualstudio.com/docs/devcontainers/tutorial) tutorial until the "Check Installation" step.
22
 
 
26
 
27
  Wait for the container to build and install the requirements. This could take five to ten minutes depending on the internet connection and hardware. Once the container is ready, run the application by typing `streamlit run 01_Introduction.py` in the terminal at the bottom of VS Code. The application should open in your default browser automatically.
28
 
29
+ ### Troubleshooting
30
 
31
+ - If the container fails to build, look for a part of the error message that says `"bind": bind source path does not exist:` then delete the `wayland-0` and `wayland-0.lock` files in the path specified by that portion of the error. On a default Ubuntu installation, the path is `/run/user/1000/wayland-0`. This advice is taken from [here](https://dev.to/crumdev/vscode-dev-container-failing-to-build-ap4).
32
  - If the app starts to run in the Dev Container but spontaneously kills itself, increase the maximum RAM and SWAP allocations in the Docker Desktop application settings.