Forum Replies Created
Please do a quick search of the forum before asking any questions: it may have already been answered, and it will save you some time.
Please always include what version of iolite and Igor Pro you are using and what platform you are running it on (Mac or PC, Windows 7 or 8, etc?)
Please include any/all error messages you may have seen. Usually an error message is also printed to the Command Window in Igor. You can view the History Window by pressing Cmd + J (Cntl+J on PC).
Please include anything remedies you have already tried. It will save you time if you don’t have to wait until we suggestion something you’ve already tried.
Please be patient! 🙂
Hi all and welcome to the new iolite forum. We hope that this forum is as constructive as the old forums. Please read the Sticky about posting to the forum before creating a new post, but apart from that, all questions, queries, comments or suggestions related to iolite, LA-ICP-MS, mass spectrometry or analytical chemistry are welcome. Also, feel free to plug any of your publications that you think might be useful to the iolite community.
- This topic was modified 4 years, 11 months ago by Dr Bence Paul.
To post to the new iolite forum, you need to have a user account. Users that have purchased iolite should automatically get a user account (if you haven’t received your log in details yet, please send us an email).
If you would like to post but don’t want to purchase a copy of iolite, or are part of a team that purchased iolite under a single user’s name, please contact us, or download the free trial version of iolite. The latter will automatically create a user profile that you can use to sign in with.
If you have any problems, please let us know.
Also, please include that OS you’re working on (PC or Mac), what version of Igor and what version of iolite you are using for all new posts. Thanks!
the iolite teamDecember 7, 2014 at 4:40 am in reply to: Iolite default preferences – single file/entire folder issue #3117
Matthijs van SoestParticipant
Per Bence’s request, I am posting this issue on the forum:
When you select entire folder for the import file settings in the default preferences panel, it will still be set to single file.
I know there is a fix in the works.December 7, 2014 at 6:07 am in reply to: Iolite default preferences – single file/entire folder issue #3118
This issue is related to the saving of default options, and we’ve fixed it in iolite v3.01 (which is due for release early in 2015)!
Thanks for posting Thijs!
BenceJanuary 12, 2015 at 10:29 am in reply to: Problem creating format file for Nu Plasma .run files. #3177
I have a problem trying to import Nu Plasma .run files from U-Pb LA-ICP-MS analyses
I am unable to save the format file: I create and assign the appropriate channel names e.g. U238, U235, Pb207 etc. and ‘_skip_’ for columns with no useful information. When I press done i get a “Function Execution Error” which says “While executing Save, the following error occurred. no symbolic path of that name”.
DavidJanuary 12, 2015 at 11:27 am in reply to: Problem creating format file for Nu Plasma .run files. #3178
I have copied the global procedure file across, and that seems to allow me to create a format file. After creating, when I try to import a .run file i get the error: “Failed to extract either an element or mass from “N=’_skip_'”. Import aborted”
The procedure “StoreNu_TR_ChannelMetadata_2()” aborted with the following message… (Full RT stack is: Butt_ImportButtonHandler;LoadNu_TR_File;StoreNu_TR_ChannelMetadata_2;) “Failed to extract either an element or mass from “N=’_skip_'”. Import aborted”
Any help would be greatly appreciated,
P.S I have emailed you a .run file
January 25, 2015 at 10:21 am in reply to: Problem creating format file for Nu Plasma .run files. #3229
- This reply was modified 4 years, 8 months ago by DHolder.
Sorry for the delay in getting back to you with this issue. I have found the issue in the Nu Plasma importer and fixed it so that now it should be able to handle the skipped columns gracefully.
An updated version of the importer is available here. Make a backup of your iolite v3 folder before you download the file, and quit Igor Pro. Then unzip the downloaded file and put it into the Global Procedures folder within your iolite 3 folder. It should overwrite the existing file of the same name. Then restart Igor Pro and you should be using the latest version of the code.
This fix will be available in versions of iolite greater than v3.0.
Please let me know if it doesn’t work.
BenceJanuary 27, 2015 at 3:23 pm in reply to: Problem creating format file for Nu Plasma .run files. #3243
Thanks for your help. I am now able to import my .run files. I am now stuck on the DRS. I am trying to run U/Pb geochronology, but when i try to crunch the data after setting up my baselines and samples, i get an error:
“while executing a wave read, the following error occurred: couldn’t find the given dimension item label %FinalAge206_238 in wave ‘m_Baseline_1′”
Two things: I did an automated baseline identification based on the beam intensity. Secondly, when i look at the individual channels there seems to be almost no discernible data, only the first (‘U238’) channel appears to show anything really. I dont see why this is. Any ideas what im doing wrong?
I have emailed you a copy of the experiement as this may be easiest to work on.
Thanks again for your help,
I’m trying to import data from an X-Series, and I managed to get one of my three .csv files to import into Iolite 3. The other two (and now if I try to import the one that worked originally) give the error message: “The function AddTo3DMetadataWave found a blank row in the start times column of the 3D metadata wave. This is a bad thing – the function says it wants a payrise before it’s willing to deal with these kinds of shenanigans.”
I have tried importing .csv files that have worked in the past, and they no longer work either even though they have not been modified or opened since the last import into Iolite 2.5.
I know that someone was having this problem in Iolite 2.5 based on a forum post from last november, but it does not appear that a solution was ever posted, and now I am having this problem in Iolite 3.
CiciApril 27, 2015 at 9:34 am in reply to: Problem creating format file for Nu Plasma .run files. #3572
Just to follow up on this issue, there was a problem with the raw data that we sorted out. It ended up not being an import issue… this time!
I am setting up our Nu Plasma 1 (machine #2!) for Pb by laser, but when I try to import the data into Iolite I keep getting errors related to the timing of each analysis. This morning I got ‘could not import <sample> due to time overlap on one or more channels (“Hg202”)’ (this might not be the exact wording; Iolite froze for other reasons before I copied the warning). Out of the 11 files I was trying to import, this happened to the two samples immediately before standards, when the delay between analyses is the longest. Now I’m getting ‘The sample <sample> was shunted by x seconds to avoid a time conflict’, where x is between 12 and -12, and has been applied to about 3/4 of the samples (but not the standards). The time stamps in the individual files in both cases clearly do not overlap each other, but I’m not sure why/where/how else Iolite thinks they might be colliding.
I’m running Iolite v.3.0 in Igor Pro 6.36 on a Win7 machine.
If it helps, this morning’s run was:
and this afternoon’s run was:
Many thanks in advance for any help you can provide,
P.S. Thanks for the instructions and patch for creating Nu format files, by the way – although I still get ‘<time>: The shortcut file “<shortcut>” did not contain enough channel names to load this file. Import aborted.’ on the first attempt every time I create one (and I promise I put the correct number of column headings into the table)…
Quick update – found a screen grab with most of this morning’s error message visible (missing bits indicated with ….):
‘The sample <sample> was not loaded due to a time conflict with existing d…. channel(“Hg202”), somewhere between 27/04/2015 (2…. 27/04/2015 (2) 14:08:00’
Hopefully that makes more sense to you than me!
One of the issues with the Nu Plasma .run files is that the time stamp doesn’t include seconds. So if you start your sample at 9:15:54, it will be recorded as 9:15. When iolite tries to import your data, the actual start time could be off by up to 59 seconds. iolite always checks to make sure you won’t have overlapping values for your data, which is what might happen if one samples ends at e.g. 9:20:10 and your next sample starts are 9:20:50. This is why you see that “shunting…” message. If it finds an overlap*, iolite tries shifting the data backwards and forwards looking for a fit where there’s no overlap. In your case, it appears this is not working.
Would you mind zipping up some example files and sending them to us at firstname.lastname@example.org? That way, we can see in the code where things are going wrong.
*Only for Nu Plasma data
Thanks for the quick reply. Our files do appear to have seconds printed: “27/04/2015″,”04:22:08 PM” from one of yesterday’s files, for instance. The selected date format in Iolite is dd/mm/yyyy hh:xx:ss. Many thanks for offering to look at the files; they will be on your way shortly.