nformella / Cluster-based-network-modeling-using-auto-encoders

GNU General Public License v3.0
1 stars 2 forks source link

Create OpenFOAM singularity image #3

Closed AndreWeiner closed 3 years ago

AndreWeiner commented 3 years ago

To perform simulations on TU Braunschweig's Phoenix cluster and locally on your laptop/workstation, we use Singularity containers. The advantage of containers is that you can run your software wherever you want without having to install the software or its dependencies. The only dependency is Singularity. You can follow the instructions provided in this repository to build a suitable container with OpenFOAM-v2006. If you like, you can modify the definition (.def) file in two ways:

Also, add the final definition file to your repository and add instructions on how to build it to the README file.

Best, Andre

AndreWeiner commented 3 years ago

Hi @nformella, have a look at the updated repository with OpenFOAM-v2012 and PyTorch 1.7.1. Best, Andre

nformella commented 3 years ago

Hi Andre,

I figured out the memory allocation problems I had using singularity. Containers do not work with WSL1 so I had to update my Windows 10 system to a newer build in order to install WSL2. Now it is running fine. Trying to get GUIs to work right now via VcXsrv Windows X Server. I still have to figure out some network setting problems.

Best, Niels

AndreWeiner commented 3 years ago

Good to hear that you made Singularity work. If you need the X server for ParaView, it is easier to install ParaView on Windows. Regarding Visual Studio Code, you can try to access WSL via the VScode remote plugin. These two apps should be the only ones requiring a GUI. Best, Andre

nformella commented 3 years ago

Hi Andre,

I got everything up and running. However, I am not sure if by the final definition file you are referring to the Singularity.def file. I did not change anything in that file but deleted the libtorch lines in the Dockerfile.

I had some trouble building a new singularity image with the updated repository. Therefore I used WSL1 just for the image creation. In order to actually start the shell, however, I have to use WSL2. The problem seems to be related to my WSL2. I am assuming some network problem. Fortunately, there is no problem running the cylinder test case.