Contours not shown

We have a very odd case where a fresh installation of AnalysisAssign 3 on a MacBook (MacOS Tahoe, Apple M1 2020) works apparently fine but does not display the contours of an example HSQC from the tutorials. It imported fine and all parameters are shown and make sense but regardless of the contour threshold no contours are drawn. Changing contour levels leads to the following error message in a little window:

SpectrumViewNd’ object has no attribute ‘_getVisibleSpectrumViewParams’

Plus the following in the terminal:

AttributeError: ‘NoneType’ object has no attribute ‘dot’
Traceback (most recent call last):
File “/Users/claudia/ccpnmr/src/python/ccpn/ui/gui/lib/OpenGL/CcpnOpenGL.py”, line 2680, in mouseMoveEvent
point = self.mapFromGlobal(QtGui.QCursor.pos())
File “/Users/claudia/ccpnmr/src/python/ccpn/ui/gui/lib/OpenGL/CcpnOpenGL.py”, line 2836, in _updateMouseEvent
# # NOTE:ED check moving of baseline
File “/Users/claudia/ccpnmr/src/python/ccpn/ui/gui/lib/OpenGL/CcpnOpenGL.py”, line 4130, in getCurrentCursorCoordinate

AttributeError: ‘NoneType’ object has no attribute ‘dot’

Has this been seen before? Is there anything that one can do?

thanks,

mark

Hi Mark,

no, we haven’t seen this before, but we’ve not used Analysis on Tahoe yet. (Has anyone else??) We’ll have a look and see if we can make sense of this error or not.

Vicky

Hi Vicky,
Thank you very much for having a look.
I realised that Tahoe has just come out, so indeed few people might have used it. On my own iMac I have Sequoia and it works fine without any problems.
Based on a quick glance they seem to have made significant changes to the user interface in Tahoe and that might involve the graphics in general.
Let’s keep fingers crossed that something can be done.

Mark

Hi Mark,

it looks like you weren’t running the most up-to-date version of Analysis, so it could be worth making sure all the latest updates are installed. But essentially it looks as though we have to create a new build specifically for Tahoe which will probably take a few days to get sorted.

Sorry about that (but thanks for highlighting the issue!),
Vicky

Hi Vicky,
Just checking if anyone else has tried to use CCPNMR on a Mac with Tahoe? Mine urges me to upgrade from Sequoia but I am concerned that I won’t be able to use CCPNMR.

thanks,

mark

Hi Mark,

@ejb says that he should get the Tahoe build done this week. We’ll let you know once it’s done!

Vicky

Hi Mark,

@varioustoxins on our team has moved to a new Mac running Tahoe with an M5 processor and using our Mac download for the M processors he doesn’t seem to have had any problems at all. Contours are there etc.

So make sure you use the right Mac download for the right type of processor your have (Intel vs. ARM) and that you are fully up to date with updates etc. It looks like it should then work.

Vicky

Hi Mark,

we have a couple of new academic releases for Mac. The M-based on should work without problems on Tahoe. You can find it at
https://ccpn.le.ac.uk/download/ccpnmr/ccpnmr3.3.4/release3.3.4SequoiaM-Academic.zip

We’re still not sure why things didn’t work for your previously. All we can think is that the intel version was used accidentally.

Vicky

Hello Vicky,

I have recently installed the CCPNMR suite version 3.3.4 on my brand new MacBook Pro M5 running macOS Tahoe 26.2 (release3.3.4SequoiaM-Academic).

I have no problem opening project directories that were previously created with Assign version 3.2.2.1. However, I am unable to open projects that were created using Analysis version 2.5, Release 2.

When I attempt to open these projects, I receive the following message: “ Warning Error loading project. The ‘name’ trait of a XmlLoader instance expected a unicode string, not the NoneType None.”

I would like to avoid having to convert these projects to version 3 on my old computer (Mac running macOS Catalina) before opening them on the new machine.

Could you please advise on whether projects created with Analysis 2.5 are compatible with CCPNMR 3.3.4/Tahoe, or if a specific conversion procedure is required?

Thank you very much for your help.

Best regards,

Sylvie

Hi Sylvie,

I wonder if you could send us such a project to support@ccpn.ac.uk. I suspect the issue could be project-specific and not so easy for us to recreate.

Thanks,
Vicky

Hi Sylvie,

@varioustoxins has been able to read in a V2.5.2 project with CcpNmr Analysis 3.3.4 on Tahoe, so I suspect this is indeed something project specific. The warning about unicode strings suggests to me that there could be issues over unusual characters somewhere in the filenames or paths or something like that.

Vicky

Hello Vicky,

Thank you for your quick reply.

I have just re-tested the workflow using a new minimal project created with Analysis 2.5 on my old Mac, and then opened it with CCPNMR 3.3.4 on macOS Tahoe. This time it worked correctly. You were right — there must have been something corrupted in the original project file.

I would also like to take this opportunity to ask another question: have you been able to interface this new version of CCPNMR with XPLOR-NIH and ARIA on Apple M5 machines running macOS Tahoe?

Thank you again for your help.

Best regards,

Hi Sylvie,

I have not yet tested Xplor NIH on Tahoe, I have M1. I usually have not issues with Xplor NIH after Mac OS upgrade. As for Aria I tend to use AriaWeb.
Have you encountered any problems?

BW,
Eliza

Hi Eliza,

I have not installed XPLOR-NIH on my new machine yet. Which versiondid you use, and did you encounter any difficulties when compiling it?

BW

Sylvie

I can have a check in the next couple of days I have m5 Tahoe

regards
Gary

Dr Gary S Thompson NMR Facility Manager
CCPN CoI & Working Group Member
Wellcome Trust Biomolecular NMR Facility
School of Natural Sciences
University of Kent, Canterbury, Kent, England, CT2 7NZ

:telephone::01227 82 7117
:envelope:: g.s.thompson@kent.ac.uk
orchid: ORCID

Hi Gary, thanks !
I’ve just installed version arm64-3.11.1 from the website and using the sh script. It seems to be working. I haven’t tried calculating any structures with it yet. I also hope to find a version of Aria that is compatible.
Regards,
Sylvie