this is an update to version 1.0.9.
Installation, start and data processing.
After installing Warpem 1.0.9, the "nightly build " is unzipped in place.
What does not
There are a number of installation isses. These Workarounds for Warpem 1.0.9 have to be applied.
What was not tested
several users have already been using it, so far there are no known issue.
An advantage over a pure windows installation is, that multiple users can use Warpem on a remote machine.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Debian 11||Dec 22 2022||7.22-staging||Yes||No||No||Garbage||Alois Schlögl|
|Show||Debian 11||Dec 22 2022||7.21-staging||Yes||Yes||Yes||Silver||Alois Schlögl|
|Current||Debian GNU/Linux 11.x "Bullseye" x86_64||Oct 07 2022||7.18-staging||Yes||Yes||No||Silver||Alois Schlögl|
|Bug #||Description||Status||Resolution||Other apps affected|
|54102||GPU Caps Viewer does not report any CUDA devices starting with version 7.21||UNCONFIRMED||View|
|54197||cuda-z and warpem fail in wine-staging 7.22 and later||UNCONFIRMED||View|
|55011||Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs||UNCONFIRMED||View|
Using Boxnet  in Warp crashes on machine with RTX2080 cards but works fine on GTX1080 cards (other GPU's were not tested)
Instead of using all of wine-staging, it is sufficient to use only the patches of "nvcuda-CUDA_Support".
The Boxnet module in Warpem seem only usable with older GPU versions like the GTX1080ti
For the RTX2080 an additional patch to wine is needed (see Bug 53809)
When using newer cards like RTX3080, A10, A40, Warpem hangs when trying to load the Boxnet model. I do not know whether this is also the case on Window, so I do not know whether this is a bug in Wine or Warpem.
However, when Boxnet is not needed, Warpem seems to run fine.