Skip to content
Snippets Groups Projects
Commit 104966fb authored by David Seus's avatar David Seus
Browse files

correct some minor typos

parent 96c0a7e5
Branches
No related tags found
No related merge requests found
...@@ -122,12 +122,12 @@ Have a look around running `ls`. You should see the folder `shared` from where ...@@ -122,12 +122,12 @@ Have a look around running `ls`. You should see the folder `shared` from where
you are, which should be the fenics home directoy. you are, which should be the fenics home directoy.
## Install missing python3 modules ## Install missing python3 modules
Once you are in the container navigate into the `Setup` of the cloned repository. Once you are in the container navigate into the `Setup` folder of the cloned repository.
This should be achieved by running If you followed the steps above, this should be achieved by running
cd shared/Setup cd shared/Setup
within the container. Upgrade pip by running within the container. Upgrade the python package manager `pip` by running
sudo pip3 install --upgrade pip sudo pip3 install --upgrade pip
...@@ -149,7 +149,7 @@ you might have to run ...@@ -149,7 +149,7 @@ you might have to run
sudo pip3 --use-feature=2020-resolver install pandas sudo pip3 --use-feature=2020-resolver install pandas
on offending packages. in this case and similary on offending packages listed in the warning.
In case you get a warning like this In case you get a warning like this
~~~ ~~~
WARNING: The scripts f2py, f2py3 and f2py3.6 are installed in '/home/fenics/.local/bin' which is not on PATH. WARNING: The scripts f2py, f2py3 and f2py3.6 are installed in '/home/fenics/.local/bin' which is not on PATH.
...@@ -165,7 +165,8 @@ Finally, add the `LDDsimulation` folder to your python path by adding ...@@ -165,7 +165,8 @@ Finally, add the `LDDsimulation` folder to your python path by adding
~~~bash ~~~bash
export PYTHONPATH=${PYTHONPATH}:${HOME}/shared/LDDsimulation/: export PYTHONPATH=${PYTHONPATH}:${HOME}/shared/LDDsimulation/:
~~~ ~~~
to ~/fenics.env.conf. to `~/fenics.env.conf`. Failing to do so will result in complaints of missing
modules if you run an LDDsimulation based example.
After steeing this you need to exit the container (by typing `exit`) and After steeing this you need to exit the container (by typing `exit`) and
step in again, to make changes effective. step in again, to make changes effective.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment