Hi John
Yes, that is exactly what I have in mind.
Once we have a comprehensive database of JEOL wavescans, there is no need to mix them with CAMECA scans anymore and they can definitely be in separate files, where the user can than choose between JEOL and CAMECA. Especially if I end up capturing scans on the same standards that currently exist for CAMECA my database.
But the problem is that at the moment all scans that you want to display have to be in the same csv file using the 1st column for the x values and the other columns for the individual scans. Furthermore, all wavescans have to be collected with the same x values since I only have one column for them. If I find time, I will look into transferring the csv files over to sql.
The csv format that I am using is fairly similar to the Probe for EPMA output file. In my csv files the first row contains the labels (e.g., standard or mineral names). The first column has all the x values and the other columns carry the wavescans. When I export wavescans collected with your software I basically just have to delete the multiple x columns and adjust the label a little bit, because that is what comes up in the legend under the graph.
At the moment, to be able to easily add wavescans from other labs, the scans should be from 23000 to 80000 with # Points 2048 in the acquisition window (and I use a time of 0.5 sec.). Using these parameters, our instrument than produces scans that start at 23000 and run with a step size of 27 units (23000, 23027, 23054, etc.) to ~78242. Although the end is not too important. The important bit is the step size so that I can use the same x values for everything.