How can I get MacOS to run the VTK window over ssh - macos

I am trying to open a VTK render on a local machine through ssh. I am using pyvista to make the render, which is being run from a python script on a remote machine.
Local machine (where I want to see the render): MacOS Catalina 10.15
Remote machine: Ubuntu 18.04
To run the script I first ssh into the remote machine and then run, i.e.
ssh -Y <username>#remotehost.com
python script.py
However when I run this I get the following error:
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
ERROR:root:GL version 2.1 with the gpu_shader4 extension is not supported by your
graphics driver but is required for the new OpenGL rendering backend. Please update
your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5
or later and make sure your driver in Mesa supports OpenGL 3.2.
[1] 21692 segmentation fault (core dumped) python script.py
Based on several posts online I have tried the following setting:
defaults write org.macosforge.xquartz.X11 enable_iglx -bool true
On MacOS I have installed mesa==20.0.2 and mesalib-glw==8.0.0
The issue appears to be that MacOS is using OpenGL==2.1, but should instead be using version 3.2+. This is confirmed with I run:
$ glxinfo|grep OpenGL
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: AMD Radeon Pro 560X OpenGL Engine
OpenGL version string: 2.1 ATI-3.8.24
OpenGL shading language version string: 1.20
OpenGL extensions:
How can I get MacOS to run the VTK window over ssh? I The script runs fine if I run it locally. Also, it runs fine if I run it on the remote only. It's only when I try to run it remotely and view in locally I have this issue. Is it a matter of either changing the default OpenGL version or upgrading somehow?

I solved this using VirtualGL.
VirtualGL server works for Ubuntu 18.04 and VirtualGL client for MacOS Catalina (10.15.4).

Related

Installing OMNeT++ on M1 MacBook

Followed instructions given in https://doc.omnetpp.org/omnetpp/InstallGuide.pdf
OMNeT++ Version - omnetpp-5.6.2
Device - MacBook Air M1 (MacOS Big Sur Version 11.4)
Encountered the following problems.
$. setenv -> didn't work (worked after replacing "." with "source")
$./configure -> gives the following error.
configure: error: Qtenv cannot find qmake -- maybe it is not in the PATH or has some exotic name (tested names were: qmake qmake-qt5 qmake5) - disabling Qtenv. You can try setting the QT_PATH variable in configure.user to a valid location
$ make -> gives the following error.
Makefile:54: Makefile.inc: No such file or directory
make: *** No rule to make target `Makefile.inc'. Stop.
Is it possible to get OMNeT++ working on M1 Macs? Any help would be greatly appreciated.
Thanks in advance.
There is no native support for M1 processors, especially because omnet++ 5.6 was released way before the M1 release, but you can run omnet with Rosetta2 in x86_64 mode. You would still get pretty decent performance. With x86_64 emulation I measured similar performance like on my last year high end AMD laptop. Native mode would give you a 25% boost compared to that.
To turn on the emulation for a shell window, start a new shell with
$ arch -x86_64 /bin/zsh --login
and then continue in that shell with
$ source setenv
$ ./configure
$ make
run everything from that shell window (as usual).
NOTE: OMNeT++ 5.6 relies on the system-wide installed JRE to run the IDE. That may NOT be present on your system if you are running on ARM. OMNeT++ 6 and 5.7 comes with a built-in private JRE, so the IDE should work with those versions also in intel emulation mode.
ps: OMNeT++ 6 may get native M1 support (this depends on the availability of some dependencies (JavaVM, Qt etc.). I'm also considering an ARM based docker image, that would allow running at native performance (as long as you have an XServer installed).

tensorflow Mac OS gpu support

According to
https://www.tensorflow.org/install/install_mac Note: As of version 1.2, TensorFlow no longer provides GPU support on Mac OS X.
GPU support for OS X is no longer provided.
However, I would want to run an e-gpu setup like akitio node with a 1080 ti via thunderbolt 3.
What steps are required to get this setup to work?
So far I know that
disable SIP
run automate e-gpu script https://github.com/goalque/automate-eGPU
are required. What else is needed to get CUDA / tensorflow to work?
I wrote a little tutorial on compiling TensorFlow 1.2 with GPU support on macOS. I think it's customary to copy relevant parts to SO, so here it goes:
If you haven’t used a TensorFlow-GPU set-up before, I suggest first setting everything up with TensorFlow 1.0 or 1.1, where you can still do pip install tensorflow-gpu. Once you get that working, the CUDA set-up would also work if you’re compiling TensorFlow. If you have an external GPU, YellowPillow's answer (or mine) might help you get things set up.
Follow the official tutorial “Installing TensorFlow from Sources”, but obviously substitute git checkout r1.0 with git checkout r1.2.
When doing ./configure, pay attention to the Python library path: it sometimes suggests an incorrect one. I chose the default options in most cases, except for: Python library path, CUDA support and compute capacity. Don’t use Clang as the CUDA compiler: this will lead you to an error “Inconsistent crosstool configuration; no toolchain corresponding to 'local_darwin' found for cpu 'darwin'.”. Using /usr/bin/gcc as your compiler will actually use Clang that comes with macOS / XCode. Below is my full configuration.
TensorFlow 1.2 expects a C library called OpenMP, which is not available in the current Apple Clang. It should speed up multithreaded TensorFlow on multi-CPU machines, but it will also compile without it. We could try to build TensorFlow with gcc 4 (which I didn’t manage), or simply remove the line that includes OpenMP from the build file. In my case I commented out line 98 of tensorflow/third_party/gpus/cuda/BUILD.tpl, which contained linkopts = [“-lgomp”] (but the location of the line might obviously change). Some people had issues with zmuldefs, but I assume that was with earlier versions; thanks to udnaan for pointing out that it’s OK to comment out these lines.
I had some problems building with the latest bazel 0.5.3, so I reverted to using 0.4.5 that I already had installed. But some discussion in a github issue mentioned bazel 0.5.2 also didn’t have the problem.
Now build with bazel and finish the installation as instructed by the official install guide. On my 3.2 GHz iMac this took about 37 minutes.
Using python library path: /Users/m/code/3rd/conda/envs/p3gpu/lib/python3.6/site-packages
Do you wish to build TensorFlow with MKL support? [y/N] N
No MKL support will be enabled for TensorFlow
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]:
Do you wish to build TensorFlow with Google Cloud Platform support? [y/N]
No Google Cloud Platform support will be enabled for TensorFlow
Do you wish to build TensorFlow with Hadoop File System support? [y/N]
No Hadoop File System support will be enabled for TensorFlow
Do you wish to build TensorFlow with the XLA just-in-time compiler (experimental)? [y/N]
No XLA support will be enabled for TensorFlow
Do you wish to build TensorFlow with VERBS support? [y/N]
No VERBS support will be enabled for TensorFlow
Do you wish to build TensorFlow with OpenCL support? [y/N]
No OpenCL support will be enabled for TensorFlow
Do you wish to build TensorFlow with CUDA support? [y/N] y
CUDA support will be enabled for TensorFlow
Do you want to use clang as CUDA compiler? [y/N]
nvcc will be used as CUDA compiler
Please specify the CUDA SDK version you want to use, e.g. 7.0. [Leave empty to use system default]:
Please specify the location where CUDA toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify which gcc should be used by nvcc as the host compiler. [Default is /usr/bin/gcc]:
Please specify the cuDNN version you want to use. [Leave empty to use system default]:
Please specify the location where cuDNN library is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify a list of comma-separated Cuda compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size.
[Default is: "3.5,5.2"]: 6.1
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
Configuration finished
Assuming that you have already setup your eGPU box and attached the TB3 cable from the eGPU to your TB3 port:
1. Download the automate-eGPU script and run it
curl -o ~/Desktop/automate-eGPU.sh
https://raw.githubusercontent.com/goalque/automate-eGPU/master/automate-eGPU.sh
&& chmod +x ~/Desktop/automate-eGPU.sh && cd ~/Desktop && sudo
./automate-eGPU.sh
You might get an error saying:
"Boot into recovery partition and type: csrutil disable"
All you need to do now is to restart your computer and when it's restarting hold down cmd + R to enable the recovery mode. Then locate the Terminal while in recovery mode and type in:
csrutil disable
Then restart your computer and re-run the automate-eGPU.sh script
2: Download and installing CUDA
CUDA: https://developer.nvidia.com/cuda-downloads
Run the cuda_8.0.61_mac.dmg file and follow through the installation phase. Then afterwards you will need to set the paths.
Go to your Terminal and type:
vim ~/.bash_profile
Or whether you have stored your environmental variables and then add these three lines:
export CUDA_HOME=/usr/local/cuda
export DYLD_LIBRARY_PATH="$CUDA_HOME/lib:$CUDA_HOME:$CUDA_HOME/extras/CUPTI/lib"
export LD_LIBRARY_PATH=$DYLD_LIBRARY_PATH
3. Downloading and installing cuDNN
cuDNN: https://developer.nvidia.com/cudnn
To download cuDNN is a bit more troublesome you have to sign up to be a developer for Nvidia and then afterwards you can download it. Make sure to download cuDNN v5.1 Library for OSX as it's the one that Tensorflow v1.1 expects Note that we can't use Tensorflow v1.2 as there is no GPU support for Macs :((
[![enter image description here][1]][1]
Now you will download a zip file called cudnn-8.0-osx-x64-v5.1.tgz, unzip and, which will create a file called cuda and cd to it using terminal. Assuming that the folder is in Downloads
Open terminal and type:
cd ~/Downloads/cuda
Now we need to copy cuDNN files to where CUDA is stored so:
sudo cp include/* /usr/local/cuda/include/
sudo cp lib/* /usr/local/cuda/lib/
4. Now install Tensorflow-GPU v1.1 in your conda/virtualenv
For me since I use conda I created a new environment using Terminal:
conda create -n egpu python=3
source activate egpu
pip install tensorflow-gpu # should install version 1.1
5. Verify that it works
First you have to restart your computer then:
In terminal type python and enter:
import tensorflow as tf
with tf.device('/gpu:0'):
a = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[2, 3], name='a')
b = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[3, 2], name='b')
c = tf.matmul(a, b)
with tf.Session() as sess:
print (sess.run(c))
If you have a GPU this should run with no problem, if it does then you should get a stack trace (just a bunch of error messages) and it should include
Cannot assign a device to node 'MatMul': Could not satisfy explicit device specification '/device:GPU:0' because no devices matching that specification are registered in this process
If not then you're done congratz! I just got mine set up today and it's working perfectly :)
I could finally make it work with the following setup
Hardware
Nvidia Video Card: Titan Xp
EGPU: Akitio Node
MacBook Pro (Retina, 13-inch, Early 2015)
Apple Thunderbolt3 to Thunderbolt2 Adapter
Apple Thunderbolt2 Cable
Software versions
macOS Sierra Version 10.12.6
GPU Driver Version: 10.18.5 (378.05.05.25f01)
CUDA Driver Version: 8.0.61
cuDNN v5.1 (Jan 20, 2017), for CUDA 8.0: Need to register and download
tensorflow-gpu 1.0.0
Keras 2.0.8
I wrote a gist with the procedure:
https://gist.github.com/jganzabal/8e59e3b0f59642dd0b5f2e4de03c7687
Here is my solution to install an e-gpu on a mac. Tensorflow doesn't support tensorflow-gpu anymore, so there are definitely better approaches to get it working:
My configuration:
IMac 27' late 2012
Aktio Node
GTX 1080 ti
3 Screens: One of them connected to the GTX 1080 and the others directly plugged on the mac.
Advantages of windows bootcamp installation:
You can use pip to install tensorflow-gpu.
Good GPU 1080 ti support (Downloadable display driver)
Howto:
Install windows 10 with bootcamp. Do not connect the Akito node for the moment.
Download and install the display driver for your gpu from NVIDIA download page
Install Visual Studio
If you want to use CUDA 9.x you can install Visual Studio 2017
Otherwise install Visual Studio 2015
Install CUDA and CuDNN
Note that the tensorflow-gpu version must match with your Cuda and your CudNN version. See available tensorflow releases here.
After the CUDA installation you can move the unpacked CuDNN files to the CUDA folder at: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0. Move the lib files to the lib folder, the bin files to the bin folder and the include files to the include folder.
Install Python 3.5+
You need a 64-bit version to install tensorflow-gpu with pip
Python 2.7 won't work.
Install tensorflow with pip:
Command:
pip install tensorflow-gpu==1.5.0rc0
Check your installation
The display driver has been installed correctly when you can plug a screen to the GTX 1080 ti card.
Call C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe to check if your video card is available for CUDA.
Execute the following tensorflow command to see available devices:
from tensorflow.python.client import device_lib
device_lib.list_local_devices()
Troubleshooting and hints:
Windows wants to update your GTX 1080 driver. Never allow that because you
won't be able to startup your computer again! A black screen with moving dots will appear before you can login to windows. Game over! Only use the display driver from NVIDIA download page.
If you cannot start windows on OSX anymore, press the alt key at startup to reinstall windows.
Ubuntu solution:
I couldn't find a working solution but here are some approaches:
It seems that my GTX 680 (iMac) and my GTX 1080 ti won't work together. Ubuntu could not be started anymore after installing the display driver via apt-get: Ubuntu not starting anmore. Try to download the official display driver from NVIDIA download page.
OSX Solution:
Tensorflow GPU is only supported up to tensorflow 1.1. I tried to install a newer version but couldn't build tensorflow-gpu with cuda support. Here are some approaches:
Install OSX Sierra to use the e-gpu script. High Sierra won't work (Jan, 13 2018). Downgrade to sierra by deleting all your partitions. Then press Command + R at startup to load the internet recovery. Don't forget to backup your data first.
Install e-gpu script.
If tensorflow-gpu 1.1 is enough for you, you can just install via pip, otherwise you need to build your pip with bazel.
Conclusion:
The windows installation is easier than OSX or Ubuntu installation because display drivers work properly and tensorflow and must not be build on your own. Always check the software version you use. The must match exactly.
I hope this will help you!

Interp1 not defined in Octave GUI for Windows

Is anyone else getting the error: interp1 undefined near line... when using the Octave GUI (Octave version 4.0.0) on Windows 10? I was just at another computer using Debian and it worked fine.
Update: just checked it again by SSH'ing into that Debian server and it recognized interp1. Not sure why the difference on Windows version of Octave GUI.

Unable to compile a python script using buildozer

I am using win 32 python 2.7 and kivy 1.8.0 but on compiling using buildozer for creating an Android app it is showing the following error:
C:\Python27\Scripts>buildozer android debug deploy
I check configuration tokens
Unknown command/target android
Although buildozer works on Windows, python-for-android does not. You need to use OSX or Linux to make an APK with Kivy. Kivy provides a Linux virtual machine for your convenience.

Install headless Ubuntu server to VirtualBox on windows

I have recently started using VirtualBox to get my Linux environment rather than fully using Ubuntu. For me this works well. But recently i have realized that in the Ubuntu vm the only thing I use a lot is the terminal, mostly just because I need the Linux environment and not the full desktop.
So I tried installing Ubuntu server into a VM, which worked. But as soon as I reboot the machine, it fails after the system boot logo. After BIOS and where I would log on from the command line I simply get a black screen with a non blinking cursor. So I am never fully able to boot into the vbox.
I read up on the command line version, trying to run it headless and then connecting to it from demote desktop. after starting the vbox I am able to connect to the desktop and see the grub screen but after selecting Ubuntu I get that same non-blinking cursor.
So is this really possible? I tried cygwin but it never really felt adequate to me. I like and am very comfortable with the Ubuntu/Debian command line. How could I (if possible) accomplish this? I want to be bale to start up the VBox and get the full command line for that vbox session. Any ideas?
Ubuntu version: 10.10, VirtualBox v. 4.0.4 r70112 and I am on Windows 7 Ultimate.
You didn't mention the versions of Ubuntu and Virtualbox.
I failed twice to install full Ubuntu 10.10 over the latest VirtualBox 4.0.4 over Ubuntu (problems like those you describe), so I switched to Debian 6.0.
All you require to install Ubuntu headless is to install the server version, which you already did. If you get blank screens, tweak the ioapic settings in both VB and Ubuntu. Another tweak is to switch between IDE and SATA drivers for the main disk (the Grub in my non-virtualized Ubuntu hangs if there's USB media attached at boot time).
If you can run full Ubuntu on a VM, you can try downgrading it by removing the xserver-xorg package, or changing the default runlevel.
If all you want is a Linux consule, you can install Debian 6 without any GUI components.

Resources