Problems starting v4.5.2 after update?

Bence

Hi everyone,

If you're having issues starting iolite after updating to v4.5.2 (released today), it is probably because we changed a couple of things with python.

To fix it, just hold down the Shift key when you start iolite. You'll be asked if you want to reset your preferences. Click Yes, and iolite should start normally.

Please let us know if you have any troubles.
-Bence

GEOJOE

Bence This helped me, many thanks!

tracypunshon

This fixed my problem, thanks!

Xin

Hi Bence,
I cannot start the latest Iolite either. I redownloaded and installed it. It showed that"“iolite4” can’t be opened because Apple cannot check it for malicious software." I also tried to hold down the Shift key but still cannot start it. Do you know what I should do?

Xin

Then I tried to allow the app to be opened in Security & Privacy, but failed again with information:
"A crash log from your last session was found."
"The following error was logged:
There was a problem with your python site-packages."

Xin

I solved it. Don't double click to start the app. Try shift+ right click & "open". Still thanks.

Bence

Hi @Xin ,

I didn't know that, so thanks for sharing it with the community. Hopefully you don't have to do it again.

Best regards,
Bence

furuixin

Hi @Bence, I’m encountering a situation where I enter the software serial number, and it always shows as already installed. However, no one is currently using this number. There seems to be a problem. How should I resolve this?

Bence

Hi @furuixin

Can you please email us at the iolite support email address? Please include your licence key in your email. We'll fix this for you via email.

Kind regards,
Bence

furuixin

Bence
Hi Bence, while processing trace-element data for Bastnaesite in 3DTraceElement, I selected NIST 610 and NIST 612 as reference standards and Ca as the internal standard, but I keep getting the error message shown below. What’s causing this, and how can I resolve it?

Bence

furuixin

It would seem that you have downhole fractionation applied. I would check the downhole fractionation plots and see if any are behaving strangely. If you don't need a downhole fractionation correction, I would turn it off.

If that doesn't work, please feel free to send me a copy of your experiment to the iolite support email.

Kind regards,
Bence

furuixin

Bence
Hello Bence,
Following your suggestion, I checked the downhole fractionation plots; only NIST612 shows a fitted curve. When I disable the fractionation correction, the error no longer appears. Could you please let me know whether the fractionation correction affects data accuracy? I’ve sent you the Iolite file—could you have a look at it for me? Many thanks.
Yous，
Fu

Bence

Hi Fu,

The short answer is that BeamSeconds is not set up correctly. In your experiment, you have Beam Seconds set to reset everytime Na passes through 1000 CPS, but it never gets that low due to background counts.

I would recommend setting the BeamSeconds channel to something with a very low background. I was able to get good results using U238, and a threshold of 200 CPS.

I will improve 3D Trace Elements to prompt you if there is an issue with BeamSeconds. It will now ask you to check your BeamSeconds settings. It will be available on the GitHub repo in the next few days.

Also, remember to re-crunch the data after changing the BeamSeconds settings.

Please let me know if that doesn't fix it for you.

Kind regards,
Bence