News:

:) To see the latest forum posts scroll to the bottom of the main page and click on the View the most recent posts on the forum link

Main Menu

CalcImage EDS map input format

Started by JonF, July 11, 2023, 07:59:47 AM

Previous topic - Next topic

JonF

Hi all,

  I have some questions about the format used by the Thermo and Bruker systems for inputting EDS maps in to CalcImage for quantification, and how they relate to the intensities imported by PfE for the Thermo, Bruker and JEOL EDS systems.

Does PfE request background subtracted net intensities for EDS quant on the standards?
Does anyone know whether (and which) software makes alterations to these intensities e.g. background subtraction, interference correction and so on? Is it all done in e.g. Esprit and imported in to PfE?
I don't suppose anyone knows what the JEOL software is exporting? Linearly interpolated background subtracted, integrated intensities?

What is the format of the maps imported in to CalcImage from the EDS software? Are they converted to .Prbimg, .GRD...?

John Donovan

#1
Yes, Probe for EPMA can quantify both WDS and EDS point analyses, but Probe Software is now working with both JEOL and Bruker to implement the acquisition and net intensity extraction of EDS maps for subsequent quantification in CalcImage, but at the moment we can only import JEOL and Cameca WDS intensity maps. These issues were previously discussed here:

https://smf.probesoftware.com/index.php?topic=400.0

In 2019, we almost had an implementation of integrated WDS and EDS map acquisition with Thermo Pathfinder (see attached poster) working with Gareth Seward on Cameca EPMA instruments (at UCSB). But then Thermo shut down their development lab in Madison and of course now Cameca is only selling shielded EPMA instruments for ~$4M, so that project was never completed unfortunately. We only were waiting for Thermo to finish two small items, first a call to retrieve the net intensities normalized to cps/livetime (at the time Thermo only returned the raw net counts, and we separately had to export the live time per pixel from Pathfinder and them normalize the intensities manually), and second, to add an option to not acquire an analog signal base map prior to the start of the spectrum image acquisition (because if the pixel dwell times were too long, or the image size too large, the base map wouldn't finish before the WDS stage/beam map would start, and the line scans would get offset diagonally).

Currently we are working to implement integration of JEOL EDS spectrum images maps with JEOL WDS stage/beam mapping and of Bruker EDS spectrum images maps with JEOL WDS stage/beam mapping also.

In any event we can say that the CalcImage file import format for EDS intensity data will be the same GRD format used for the CalcImage WDS maps. But unlike WDS intensity maps, which are uncorrected for background, the EDS maps will be net intensity maps normalized to cps/livetime. These EDS net intensity GRD files will get saved and assigned in the CalcImage project file (.CIP) just as the WDS maps do, as shown here for the Thermo Pathfinder synchronized WDS/EDS mapping that we almost got working:



We will be meeting with both JEOL and Bruker later this month at M&M to discuss moving forward on this project. However, for those who are contemplating a new EPMA instrument purchase, I would merely mention that, as we all know, the best way to ensure that we get this feature actually implemented, is to make sure to specify in your instrument purchase agreement some language requiring this capability, for example:

Quote"The vendor will provide communication and/or API documentation and necessary hardware/cables for WDS synchronized EDS spectrum image acquisition and extraction of EDS map net intensities stage and beam mapping by third party software, e.g., Probe Software, Inc. A sample test program demonstrating the necessary EDS API calls for these synchronized WDS/EDS stage and beam mapping calls and the source code for this sample/test application will also be required. Specific examples of the necessary API calls required for synchronized EDS spectrum acquisition and extraction of EDS net intensities can be provided at the appropriate time by Probe Software, Inc."

I've also attached a generic specification of the necessary calls that would need to be implemented in the attachments below just FYI.  But I should say that both JEOL and Bruker already have this document, so they know exactly what is needed, we just need to make sure that they follow through...

By the way, here is an example of a CalcImage project file with both WDS and EDS elements:

9            "CalcImage Quantitative Image Project 2/22/2019 2:34:29 PM"
"Orthoclase_374_01-30-2019_Orthoclase_00294_"
"Orthoclase_374_01-30-2019.MDB"
42            8            -1             0             0             0             0             0            -1             0             0             0             0             0             0             0             0             0             0
0             1            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP1_Na_TAP_.grd"
0             2            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP2_Ba_LPET_.grd"
0             4            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP3_Sr_LPET_.grd"
0             3            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP4_Rb_TAP_.grd"
0             5            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP5_Fe_LIF_.grd"
0             6            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP0_Si_EDS_.grd"
0             7            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP0_Al_EDS_.grd"
0             8            .100           26.1665       26.1864       43496.7962037037            43496.8026157407           "Orthoclase_00294_SP0_K_EDS_.grd"
8
0  0  0  0  0  0  0  0
0
-1             0             0             0             0             0             0
0            "C:\UserEDS\Donovan\Integrated WDS EDS Mapping\Orthoclase\01-2019\Orthoclase(1).MAP.EDS"
1             0
0            "SE"           0            "BSE"          0            "CL"
"Orthoclase_00294_VS1.grd"  ""            ""
0             0
0             0             0             0             0             0
John J. Donovan, Pres. 
(541) 343-3400

"Not Absolutely Certain, Yet Reliable"

JonF

Quote from: John Donovan on July 11, 2023, 09:40:26 AM
... the EDS maps will be net intensity maps normalized to cps/livetime. These EDS net intensity GRD files will get saved and assigned in the CalcImage project file (.CIP) just as the WDS maps do, as shown here for the Thermo Pathfinder synchronized WDS/EDS mapping that we almost got working:




Ah super, cps/livetime GRD maps is relatively easy. I was halfway through creating a .prbimg Base64 encoder!

Thanks  :)


John Donovan

Quote from: JonF on July 11, 2023, 12:25:53 PM
Quote from: John Donovan on July 11, 2023, 09:40:26 AM
... the EDS maps will be net intensity maps normalized to cps/livetime. These EDS net intensity GRD files will get saved and assigned in the CalcImage project file (.CIP) just as the WDS maps do, as shown here for the Thermo Pathfinder synchronized WDS/EDS mapping that we almost got working:




Ah super, cps/livetime GRD maps is relatively easy. I was halfway through creating a .prbimg Base64 encoder!

Thanks  :)

Attached is some code for reading and writing GRD files.

Which EDS vendor spectrum image file is this for?  I have the Thermo SI access DLLs and documentation...
John J. Donovan, Pres. 
(541) 343-3400

"Not Absolutely Certain, Yet Reliable"