issue to open SPM8 standalone and SPM12 standalone with the latest singularity image #268
Comments
|
I just tried to open my SPM12 standalone from casa-distro with the But I also tried with another version of an SPM12 standalone which contains CAT12, and it opens well. Both versions do not use the same Matlab Runtime (MCR). |
|
Have you checked that the problem does not happen using the |
|
I am only using SPM standalone for the normalization processes of Morphologist in brainvisa, and I still could run it without error on my laptop (using a rather old release of SPM12 standalone). |
|
I made more tests with SPM12 and SPM8 standalone with different images version. I tried to use a brainvisa coregister process with both versions. I also tried to open the interface of SPM inside a
Both SPM8 and SPM12 standalone use an mcr dedicated, but with the exact same version (v713). I tried to use the mcr located in SPM12 folder to launch SPM8 (and the SPM8 mcr for SPM12). And I get the exact same results as in the table. |
|
So,
Now after testing a bit, I will add even more confusion: I have 2 machines (a desktop and a laptop), both running Ubuntu 18.04 (with updates done), with SPM12-standalone-7771 installed (same release on both machines). Casa-distro updated to image
So would it be linked to a user config somewhere (path...) ? |
|
MCR v713 is the version shipping with Matlab R2010a. |
|
Perhaps ReproNim/neurodocker#358 will help. |
|
But then, do I need to update the MCR used by the standalone SPM outside of Singularity? Why hasn't this ever been reported outside Singularity here at NS? |
|
Hello 😀 I couldn't follow all your tests and I don't know what casa-distro is but there is a good chance all of the issues will disappear when using a more recent version of the MCR. R2010a was used consistently to prevent having to install a new MCR from time to time (or having to keep several versions in parallel) but it is just very dated now. I use R2019b in this Singularity definition file with no known issue. |
|
Hi Guillaume! So to be clear, you recommend we deploy the SPM8 and SPM12 standalone versions with the MCR v97 from Matlab R2019b? Although this ticket is about a Singularity deployment, I am personally interested in the deployment of SPM directly on Ubuntu 18.04 and 20.04 workstations, without Singularity. If you envision a new SPM12 standalone release, why not switch directly to R2021a? |
|
Yes, the idea would be to release a new SPM12 standalone version (r7771) relying on the most recently available version of the MATLAB Runtime (probably waiting a few weeks for R2021b, even if ideally I was waiting for R2022a). From then on, would you prefer if new releases of SPM standalone were using the same version of the MATLAB Runtime or if they were using the most recently available one at each given time (or both)? |
|
If a new MCR is required to fix bugs or crashes, then by all means please do upgrade the MCR - that's more important than saving a few GB of disk space. On the other hand, I suggest using the same MCR as long as it works and has no security issues - every sub-system upgrade comes with its own (minimal) risks of problems. Good to learn about this I tried to erase SPM5, but a couple users still need it in some scripts! As you can imagine, we have even more users still in need of SPM8 here and there. One last update of SPM8 based on the latest version of Matlab would be useful. It should buy us enough time (years) to phase out SPM8 completely... |
|
Has this issue been fixed in the Singularity image? How? |
|
Not that I know, but I haven't really understood if we could do anything, and what. The MCR is not in our (casa-distro) singularity image. We're running programs (brainvisa, anatomist, aims...) from a container, and SPM may get called from the container, but it's not actually installed in the container: it's up to the user to install it and set its path in brainvisa; or use the version installed on the network in noeuropspin. So unless a precise library in the casa-distro brainvisa container is incompatible with the MCR in use in neurospin, and could be changed with another one, it's not really related to casa-distro and containers ? |
|
In my case, I am in the process of changing the MCR which can typically be found under |
|
So we'll see if it fixes the problems for users... |
|
@gllmflndn Should I / can I use Standalone SPM8 with the R2019b MCR (v97) instead of the default R2010a MCR (v713)? I am asking because when installing Standalone SPM8 (r5236) using the R2019b MCR (v97) on an Ubuntu 18.04 workstation: #
# Install MCR 2019b (v97)
#
cd /tmp
unzip /source/matlab/MATLAB_Runtime_R2019b_Update_9_glnxa64.zip
/tmp/install -destinationFolder /destination/matlab/MATLAB_Runtime -agreeToLicense yes -mode silent
#
# Install Standalone SPM8 (r5236)
#
mkdir /destination/spm8-standalone-5236
cd /destination/spm8-standalone-5236
unzip /source/spm/standalone/spm8/spm8_r5236.zip
mv spm8/* .
rmdir spm8
#
# Initialize Standalone SPM8
#
./run_spm8.sh /destination/matlab/MATLAB_Runtime/v97 quitThe last command |
|
I get the same crash when attempting to initialize SPM12 (r7771) using the R2019b MCR (v97) on the same Ubuntu 18.04 workstation: Again Any clue? |
|
Sorry, I don't know. Any chance you can try with 20.04? |
|
I'm trying to install from scratch, trying to compare the R2010a MCR ( Installing Standalone SPM12 – MCR v713 on Ubuntu 18.04On an up-to-date Ubuntu 18.04 workstation, following the SPM/Standalone instructions, I am unable to execute Sample MCR v713 installation attempt on Ubuntu 18.04$ chmod 755 MCRInstaller.bin
$ ./MCRInstaller.bin -P bean421.installLocation="MCR" -silent
No Java Runtime Environment(JRE) was found on this system.
$ Additional messagesInstalling Standalone SPM12 – MCR v97 on Ubuntu 18.04Installation of the MATLAB RuntimeOn an up-to-date Ubuntu 18.04 LTS workstation, I am able to install the R2019b MCR using Sample MCR v97 installation on Ubuntu 18.04$ mkdir /tmp/M
$ cd /tmp/M
$ unzip /path/to/MATLAB_Runtime_R2019b_Update_9_glnxa64.zip
$
$ ./install
Installing ...
Finished
$
Installation of the SPM StandaloneI am unable to run a fresh installation of Standalone SPM12, it crashes on the first run: Sample SPM12 run with MCR v97 on Ubuntu 18.04$ cd /tmp/
$
$ unzip /i2bm/src/spm/standalone/spm12_r7771.zip
Archive: /i2bm/src/spm/standalone/spm12_r7771.zip
creating: spm12/
extracting: spm12/spm12_maci64.zip
inflating: spm12/spm12_glnxa64
inflating: spm12/run_spm12.sh
inflating: spm12/spm12_maci64
inflating: spm12/spm12.ctf
inflating: spm12/spm12_win64.exe
inflating: spm12/spm12_win32.exe
$
$ cd spm12
$
$ ./run_spm12.sh /tmp/MATLAB_Runtime/v97/ quit
--------------------------------------------------------------------------------
Segmentation violation detected at mar. oct. 26 17:13:20 2021 +0200
--------------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Desktop Environment : ubuntu:GNOME
GNU C Library : 2.27 stable
MATLAB Architecture : glnxa64
MATLAB Root : /tmp/MATLAB_Runtime/v97
MATLAB Version : 9.7.0.1737446 (R2019b) Update 9
Operating System : Ubuntu 18.04.6 LTS
Process ID : 12654
Processor ID : x86 Family 6 Model 45 Stepping 7, GenuineIntel
Static TLS mitigation : Enabled: Full
Fault Count: 1
Abnormal termination:
Segmentation violation
Register State (from fault):
RAX = 0000000000000000 RBX = 00007ffce1f5fb90
RCX = 0000000000000000 RDX = 00000000006030a0
RSP = 00007ffce1f5f8e0 RBP = 00007ffce1f5faf0
RSI = 0000000000000001 RDI = 00007ffce1f5fb90
R8 = 0000000000000000 R9 = 0000000000400a95
R10 = 00000000000000cd R11 = 00007f3ee3e505a0
R12 = 00007ffce1f5fb90 R13 = 0000000000000001
R14 = 0000000000000000 R15 = 0000000001ec49d0
RIP = 00007f3ecf83fc83 EFL = 0000000000010202
CS = 0033 FS = 0000 GS = 0000
Stack Trace (from fault):
[ 0] 0x00007f3ecf83fc83 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclmcr.so+02686083
[ 1] 0x00007f3ecf8369fd /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclmcr.so+02648573 mclInitializeComponentInstanceNonEmbeddedStandalone+00000061
[ 2] 0x00007f3ee3e505e2 /tmp/MATLAB_Runtime/v97//runtime/glnxa64/libmwmclmcrrt.so+00103906 mclInitializeComponentInstanceNonEmbeddedStandalone_proxy+00000066
[ 3] 0x0000000000400b46 /tmp/spm12/spm12_glnxa64+00002886
[ 4] 0x0000000000400b64 /tmp/spm12/spm12_glnxa64+00002916
[ 5] 0x0000000000400bb2 /tmp/spm12/spm12_glnxa64+00002994
[ 6] 0x00007f3edce0b220 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclbase.so+00352800
[ 7] 0x00007f3ecef83587 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwMVMLocal.so+00570759 _ZN7mwboost6detail8function21function_obj_invoker0INS_3_bi6bind_tINS3_11unspecifiedENS_9function1IiRKSt6vectorINSt7__cxx1112basic_stringIDsSt11char_traitsIDsESaIDsEEESaISD_EEEENS3_5list1INS3_5valueISF_EEEEEEiE6invokeERNS1_15function_bufferE+00000039
[ 8] 0x00007f3edccf7487 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00865415
[ 9] 0x00007f3edccf79c8 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00866760
[ 10] 0x00007f3edccf7c74 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00867444 _Z12mcr_run_mainRKN7mwboost9function0IiEEbb+00000196
[ 11] 0x00007f3ecef782e4 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwMVMLocal.so+00525028
[ 12] 0x00007f3edcb471d7 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmvm.so+02986455 _ZN3mvm6detail11SessionImpl7runMainERKN7mwboost9function1IiRKSt6vectorINSt7__cxx1112basic_stringIDsSt11char_traitsIDsESaIDsEEESaISA_EEEESE_+00000087
[ 13] 0x00007f3edce0b71a /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclbase.so+00354074 mclRunMain+00001194
[ 14] 0x0000000000400c59 /tmp/spm12/spm12_glnxa64+00003161
[ 15] 0x00007f3ee32d3bf7 /lib/x86_64-linux-gnu/libc.so.6+00138231 __libc_start_main+00000231
[ 16] 0x00000000004009ba /tmp/spm12/spm12_glnxa64+00002490
[ 17] 0x0000000000000000 <unknown-module>+00000000
** This crash report has been saved to disk as /home/xxxxxxxx/matlab_crash_dump.12654-1 **
MATLAB is exiting because of fatal error
Killed
$ Note that MATLAB R2019b is compatible with Ubuntu 16.04, 18.04 and 19.04 according to System Requirements - Release 2019b - Linux. |
Running existing versions of Standalone SPM12 – Ubuntu 16.04 → Ubuntu 18.04Trying different versions of SPM12 installed using Ubuntu 16.04, sometimes years ago, but now running on Ubuntu 18.04. I don't see crashes, at least on very simple tasks. I'll double check with my colleagues. Sample SPM12 runs with MCR v713 on Ubuntu 18.04 |
|
I'm trying to install from scratch again, now on Ubuntu 20.04: Installing Standalone SPM12 – MCR v713 on Ubuntu 20.04On an up-to-date Ubuntu 20.04 workstation, following the SPM/Standalone instructions, I am unable to execute Sample MCR v713 installation attempt on Ubuntu 20.04$ chmod 755 MCRInstaller.bin
$ ./MCRInstaller.bin -P bean421.installLocation="MCR" -silent
No Java Runtime Environment(JRE) was found on this system.
$ Installing Standalone SPM12 – MCR v97 on Ubuntu 20.04Installation of the MATLAB RuntimeOn an up-to-date Ubuntu 20.04 LTS workstation, I am able to install the R2019b MCR using Sample MCR v97 installation on Ubuntu 20.04$ mkdir /tmp/M
$ cd /tmp/M
$ unzip /path/to/MATLAB_Runtime_R2019b_Update_9_glnxa64.zip
$
$ ./install
Installing ...
Finished
$ Installation of the SPM StandaloneI am unable to run a fresh installation of Standalone SPM12, it crashes on the first run, on Ubuntu 20.04 as well as on Ubuntu 18.04: Sample SPM12 run with MCR v97 on Ubuntu 20.04$ cd /tmp/
$
$ unzip /i2bm/src/spm/standalone/spm12_r7771.zip
Archive: /i2bm/src/spm/standalone/spm12_r7771.zip
creating: spm12/
extracting: spm12/spm12_maci64.zip
inflating: spm12/spm12_glnxa64
inflating: spm12/run_spm12.sh
inflating: spm12/spm12_maci64
inflating: spm12/spm12.ctf
inflating: spm12/spm12_win64.exe
inflating: spm12/spm12_win32.exe
$
$ cd spm12
$
$ ./run_spm12.sh /tmp/MATLAB_Runtime/v97/ quit
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: nouveau
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib/dri/nouveau_dri.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: nouveau
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
--------------------------------------------------------------------------------
Segmentation violation detected at mar. oct. 26 22:00:00 2021 +0200
--------------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Desktop Environment : ubuntu:GNOME
GNU C Library : 2.31 stable
MATLAB Architecture : glnxa64
MATLAB Root : /tmp/MATLAB_Runtime/v97
MATLAB Version : 9.7.0.1737446 (R2019b) Update 9
Operating System : Ubuntu 20.04.3 LTS
Process ID : 9713
Processor ID : x86 Family 6 Model 94 Stepping 3, GenuineIntel
Static TLS mitigation : Enabled: Full
Fault Count: 1
Abnormal termination:
Segmentation violation
Register State (from fault):
RAX = 0000000000000000 RBX = 00007ffd807880d0
RCX = 0000000000000000 RDX = 00000000006030a0
RSP = 00007ffd80787e20 RBP = 00007ffd80788030
RSI = 0000000000000001 RDI = 00007ffd807880d0
R8 = 0000000000000000 R9 = 0000000000400a95
R10 = 000000000040063a R11 = 00007f11b92fd5a0
R12 = 00007ffd807880d0 R13 = 0000000000000001
R14 = 0000000000000000 R15 = 0000000000e9c240
RIP = 00007f11a614fc83 EFL = 0000000000010202
CS = 0033 FS = 0000 GS = 0000
Stack Trace (from fault):
[ 0] 0x00007f11a614fc83 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclmcr.so+02686083
[ 1] 0x00007f11a61469fd /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclmcr.so+02648573 mclInitializeComponentInstanceNonEmbeddedStandalone+00000061
[ 2] 0x00007f11b92fd5e2 /tmp/MATLAB_Runtime/v97//runtime/glnxa64/libmwmclmcrrt.so+00103906 mclInitializeComponentInstanceNonEmbeddedStandalone_proxy+00000066
[ 3] 0x0000000000400b46 /tmp/spm12/spm12_glnxa64+00002886
[ 4] 0x0000000000400b64 /tmp/spm12/spm12_glnxa64+00002916
[ 5] 0x0000000000400bb2 /tmp/spm12/spm12_glnxa64+00002994
[ 6] 0x00007f11b3749220 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclbase.so+00352800
[ 7] 0x00007f11a5469587 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwMVMLocal.so+00570759 _ZN7mwboost6detail8function21function_obj_invoker0INS_3_bi6bind_tINS3_11unspecifiedENS_9function1IiRKSt6vectorINSt7__cxx1112basic_stringIDsSt11char_traitsIDsESaIDsEEESaISD_EEEENS3_5list1INS3_5valueISF_EEEEEEiE6invokeERNS1_15function_bufferE+00000039
[ 8] 0x00007f11b3635487 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00865415
[ 9] 0x00007f11b36359c8 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00866760
[ 10] 0x00007f11b3635c74 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmcr.so+00867444 _Z12mcr_run_mainRKN7mwboost9function0IiEEbb+00000196
[ 11] 0x00007f11a545e2e4 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwMVMLocal.so+00525028
[ 12] 0x00007f11b34851d7 /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmvm.so+02986455 _ZN3mvm6detail11SessionImpl7runMainERKN7mwboost9function1IiRKSt6vectorINSt7__cxx1112basic_stringIDsSt11char_traitsIDsESaIDsEEESaISA_EEEESE_+00000087
[ 13] 0x00007f11b374971a /tmp/MATLAB_Runtime/v97/bin/glnxa64/libmwmclbase.so+00354074 mclRunMain+00001194
[ 14] 0x0000000000400c59 /tmp/spm12/spm12_glnxa64+00003161
[ 15] 0x00007f11b8f8b0b3 /lib/x86_64-linux-gnu/libc.so.6+00159923 __libc_start_main+00000243
[ 16] 0x00000000004009ba /tmp/spm12/spm12_glnxa64+00002490
[ 17] 0x0000000000000000 <unknown-module>+00000000
** This crash report has been saved to disk as /home/xxxxxxxx/matlab_crash_dump.9713-1 **
MATLAB is exiting because of fatal error
Killed
$ |
|
So we have two issues:
|
|
Actually we have more issues:
Typical error message
|
|
Just for reference... Installing Standalone SPM12 – MCR v713 on Ubuntu 16.04On an Ubuntu 16.04 workstation, following the SPM/Standalone instructions, I am able to execute Sample MCR v713 installation on Ubuntu 16.04$ ./MCRInstaller.bin -console -P installLocation=/tmp
Initializing InstallShield Wizard........
Launching InstallShield Wizard........
-------------------------------------------------------------------------------
MATLAB(R) Compiler Runtime 7.13 - InstallShield Wizard
Welcome to the InstallShield Wizard for MATLAB(R) Compiler Runtime 7.13
The InstallShield Wizard will install MATLAB(R) Compiler Runtime 7.13 on your
computer.
To continue, choose Next.
MATLAB(R) Compiler Runtime 7.13
The MathWorks
http://www.mathworks.com
[...] |
|
Can you test what happens with this version of SPM12 that uses the R2021b Runtime: WCHN/CTseg#9 (comment) |
|
Good news! The new version:
I'll investigate issue 2 and come back to you. |
|
Also you must have added a In my case: |
|
All the images of casa-distro that I used for tests were based on Ubuntu-18.04 as mentionned here. I could try to dig to find differences between image versions when I have some time. |
|
I'm coming back on this issue as I'm trying to test shipping SPM in casa-distro images (see brainvisa/brainvisa.github.io#106). However I see that the MCR 911 installed at neurospin is 8.5 Gb in size, whereas the v713 shipped with spm12-standalone-7771 was "only" 500 Mb large. That's a notable difference... Has v713 been pruned in any way because parts were not needed for SPM, or did the "raw" MCR grow this big ? |
That said, I do see a growth in MCR sizes ! Here is the output of [edited for proper ordering of MCR versions] |
|
Yes, that was part of the question: is the mcr 713 bundled with SPM12 standalone a lightened version, and is it possible to lighten 911 the same way, or do we need to carry the whole 8.5 Go ? From your stats, it seems that MCRs have consistently grown in a somewhat uncontrolled exponential way (this size seems crazy to me: just the matlab runtime is 3 times the size of a complete full featured operating system with several programming languages in it - gosh !) |
|
(actually I don't even know how the numbers are ordered: is 911 > 97 ?) |
|
My wrong, I had misinterpreted the MATLAB Runtime version numbers: I have reordered the above list. |
|
I'm not certain the MCR bundled with SPM12 Standalone is a light version. The size of the bundled
|
|
So we're doomed. No escape. :| |
|
Unless an official version of SPM is released soon with only the needed MCR parts in it, since it is said to be possible (https://fr.mathworks.com/matlabcentral/answers/101332-why-is-matlab-runtime-so-large)..........? ;) |
|
I have a look at this soon but would it help already if you can specify which toolboxes to install from the MCR as we do here: |
|
I don't think we can without your MATLAB Compiler. See https://fr.mathworks.com/matlabcentral/answers/101332-why-is-matlab-runtime-so-large:
|
|
Well I'm not sure to be able to fully answer that ;) We are using the core SPM (normalization, segmentation...), and Dartel, but I'm not completely aware of what are using the different toolboxes of brainvisa... I don't think we want to install a "custom SPM" just for us if the main distribution ships the whole MCR in order to allow all possible toolboxes to run, if this is needed. I was just hoping the whole SPM + toolboxes could require a limited set of libraries and ship only those, but I was maybe naive. |
|
The MCR |
|
So you've already done that, using MCR 97 lightened to the needed toolboxes, in a Ubuntu 22.04 system. I just check it and see that the MCR there is "only" 2.3 GB (compared to 5.8 as listed by @DimitriPapadopoulos above). I did not know such a container already existed, and that's a very good news, and maybe we should rely on it. The problem is that we cannot merge singularity containers, nor call one from another one (at least I have not succeeded in such an attempt), thus any modularity seems impossible. But we could perhaps unpack the image and copy its content (all is in /opt I guess), or merge/include your singularity recipe (or part of it) into ours. |
|
I hadn't checked the actual size of the MCR there and I presume that the size mentioned in the manifest (~1.2GB) is for everything compressed. It's still quite large though. It seems that some extra files can be safely removed but I didn't look into this recently: |
|
Yes, singularity .sif images are a bit compressed, and are larger inside than outside (the magic "bag of holding" concept). Yes it seems that for SPM you install just the MCR core and "numeric" package. It is still big, yes, but less than the full thing. And, yes, it's probably the good way to go, thanks again :) |
|
By the way, @DimitriPapadopoulos, we should probably install this version of SPM12 (7771 + v97) in neurospin, shouldn't we ? |
|
Mix 7771 with v97? But that cannot work, can it? We have:
[edit: v97 → v911] |
|
Would this help? |
|
It seems to: that's what is shipped in the SPM containers (it's obviously another build of 7771 based on v97, not the one we are using in neurospin). I have done it on my laptop and it works, just as in https://github.com/spm/spm-docker/blob/main/matlab/singularity.def |
|
(otherwise I could not run the SPM 8168 installed in neurospin with a MCR 911 installed "minimally": it complains that the MCR version is not the expected one, whereas it does work with the "full" MCR 911 installed in neurospin (same version, in principle?), and I don't understand that - but maybe I did a mistake somewhere) |
I just realize I did not read that correctly - 8186 is built with v97, not 911 ? I ran it using 911 and it did not complain (the full 911, as I said just earlier) |
|
My wrong. We currently have:
|
8186 is built with v911. From <manifest ... mcr-major-version="9" mcr-minor-version="11" mcr-release-version="0" need_exclusive_mcr_process="0" need_java="1 ...>You might find a list of required MCR components in there. |
|
I think the installation of spm12-standalone-7771 + mcr v97 fixes this issue. I guess we can close the ticket now. |
Hi,
I use the last singularity image (casa-dev-5.0-4.sif ) and I cannot open SPM8Standalone or SPM12Standalone.
For SPM12 standalone I had the following error:
For SPM8 standalone it is also a " Segmentation violation" error but it is quite long .
I do not have theses issue when opening the same SPM standalone in my computer without casa.
It seems that I can open SPM12 via matlab without issue.
Is there any change in the latest image that can explain this issue ?
Am I the only one to have trouble ?
Emmanuelle
The text was updated successfully, but these errors were encountered: