jamovi

De nada. You did all the work anyhow.

Sorry, I meant 2.6.26. There was a mixup own my end. I have way too many dmgs in my downloads folder. But 2.6.26 works.

It worked!!

Apparently. Again, all I got was for the app to boot as version 2.6.25. I haven't tried it with any data yet, but I'm betting that isn't the problem now that the thing goes ahead and comes up.

Thanks, Jonathon

Just tried 2.6.19 and got the mario error again. Sorry.

Sure. It's OSX 12.7.4. and my Python is 3.13.

Ok, here you go: Traceback (most recent call last): File "/Applications/jamovi2.app/Contents/Resources/lib/python3.11/numpy/_core/__init__.py", line 23, in <module> from . import multiarray File "/Applications/jamovi2.app/Contents/Resources/lib/python3.11/numpy/_core/multiarray.py&quo...

Ok, I: 1. Called up the dmg for 2.25.6 arm64 and reloaded the application. 2. Tried to get the app to boot and got the mario result. 3. Called up the Terminal and entered Application/jamovi.app/Contents/MacOS/jamovi 2. That's the name the os gave the arm64 version. I also tried using jamovi alone, a...

And this would be issued in Terminal, I suppose? Sorry to be so dense, but I never work with the system if I can help it.

You assume correctly; I'm trying to open the arm64 version of 2.6.25. I haven't tried the intel version yet. Now things get curious. Sure thing, the app is crashing the same way it did for mario. Problem = this isn't showing up in my crash logs in Console. Everything there is grayed out. Result = I ...

Ok, I just downloaded 2.6.25 on my M1 Airbook with Monterey and had the same problem as mario (Osx 12.7.4, Python 3.13, R 4.2). I reverted to 2.3.28 and the app runs just fine. I'm guessing R is too old, but the problem seems to be with numpy, not R. What gives? I can try again and try to get the er...