Quantifying X-Ray Fluorescence Data Using MAPS

Summary

Here, we demonstrate the use of the X-ray fluorescence fitting software, MAPS, created by Argonne National Laboratory for the quantification of fluorescence microscopy data. The quantified data that results is useful for understanding the elemental distribution and stoichiometric ratios within a sample of interest.

Abstract

The quantification of X-ray fluorescence (XRF) microscopy maps by fitting the raw spectra to a known standard is crucial for evaluating chemical composition and elemental distribution within a material. Synchrotron-based XRF has become an integral characterization technique for a variety of research topics, particularly due to its non-destructive nature and its high sensitivity. Today, synchrotrons can acquire fluorescence data at spatial resolutions well below a micron, allowing for the evaluation of compositional variations at the nanoscale. Through proper quantification, it is then possible to obtain an in-depth, high-resolution understanding of elemental segregation, stoichiometric relationships, and clustering behavior.

This article explains how to use the MAPS fitting software developed by Argonne National Laboratory for the quantification of full 2-D XRF maps. We use as an example results from a Cu(In,Ga)Se₂ solar cell, taken at the Advanced Photon Source beamline 2-ID-D at Argonne National Laboratory. We show the standard procedure for fitting raw data, demonstrate how to evaluate the quality of a fit and present the typical outputs generated by the program. In addition, we discuss in this manuscript certain software limitations and offer suggestions for how to further correct the data to be numerically accurate and representative of spatially resolved, elemental concentrations.

Introduction

Synchrotron-based XRF has been used across multiple disciplines for many decades. For example, it has been used in biology on studies such as that done by Geraki et al., in which they quantified trace amounts of metal concentrations within cancerous and non-cancerous breast tissue ¹. More generally, quantitative XRF has been applied to a wide array of biology studies concerned with metal concentrations in cells and tissues, as described by Paunesku et al.². Similarly, marine protists were studied for trace elements ^3,4 and even micro- and macronutrient distributions were observed within plant cells ⁵. Work by Kemner et al.⁶, which identified distinct differences in morphology and elemental composition in single bacteria cells, was also made possible through quantitative XRF analysis. Additionally, and specifically relevant to the example disclosed herein, materials scientists studying solar cell devices have made use of high-resolution XRF for studies on the existence of sub-micron metal impurities in silicon semiconductors ^7,8, correlative work on how elemental distributions affect electrical performance in solar devices ^9,10, and identifying depth-dependent gradients of CIGS thin film solar cells via grazing incidence X-ray fluorescence (GIXRF) ¹¹.

Many of these studies make use not only of the high-resolution capabilities of synchrotron X-ray fluorescence to study spatial distribution, but also the quantification of the information for drawing numerical conclusions. In many studies it is critical to know the elemental concentrations associated with the aforementioned spatial distributions. For instance, in the work by Geraki et al., the study required quantifying the difference in concentrations of iron, copper, zinc, and potassium in cancerous and non-cancerous breast tissues, to better understand what concentrations become harmful to human tissues ¹. Similarly, work by Luo et al. made use of quantified XRF to identify small amounts of chlorine incorporated in perovskite solar cells when synthesized both with and without chlorine-containing precursors ¹². Therefore, for certain studies in which the concentrations of elements are needed, proper quantification is a necessary and critical step.

The process of quantifying elemental concentrations from X-ray fluorescence (XRF) measurements translates fluorescence intensity counts into mass concentrations (e.g. µg/cm²). The raw spectra present the number of photons collected by the energy dispersive fluorescence detector as a function of energy. The spectra are first fit and then compared to a standard measurement to calculate the quantified data. In particular, the first step of fitting fluorescence spectra is critical even for the qualitative analysis of the elements. This is because prior to fitting, counts are binned based on their energy, which becomes a problem when two elements with similar fluorescence transitions are contained in the sample. In this situation, counts may be incorrectly binned and thus associated with the wrong element.

It is often also necessary to quantify XRF spectra in order to accurately draw conclusions on relative quantities of elements in a sample. Without proper quantification, counts of heavy elements and lighter elements will be compared directly, ignoring differences in capture cross section, absorption and fluorescence probability, attenuation of the fluorescence photons, and the distance of the element's absorption edge from the incident energy, which all affect the number of photons striking the detector. Therefore, the process of fitting the spectra for each map and comparing peak intensities to the standard, both of which are done in the following procedure, is critical for the accurate quantification of each of the elemental concentrations.

We demonstrate how to convert the raw counts of fluorescence photons to units of micrograms per square centimeter (µg/cm²) by first fitting an integral spectrum, or a summed spectrum of all the individual spectra produced at each measurement spot or pixel in a 2D map. This spectrum demonstrates the relative intensities of the different elements contained in the sample. The distance the absorption edge of a certain element is from the incident beam energy influences the intensities of their fluorescence peaks. In general, the closer the two energies are, the greater the intensity produced for those elements, although this is not always the case. Figure 4 in Ref ¹³ shows the dependence of the absorption length of X-ray photons, which directly relates to the resulting intensity, for the majority elements in a methylammonium lead iodide perovskite solar cell. This demonstrates the fluorescence response of elements with respect to energy, and shows that it is not a continual decrease in response with increasing distance from the incident energy, but rather that it is also dependent upon the element itself.

The result of this relationship is that raw elemental concentrations may appear higher for element channels with excitation energies closer to the incident energy, even if the true quantities of those elements are lower in relation to other elements with excitation energies farther from the incident. Therefore, the energy dependence of intensity, along with other factors such as fluorescence yield variations, different absorption edges, detector sensitivity, and measurement background, etc., is why fitting the data is very important prior to drawing conclusions on the observed elemental quantities. We then apply a fitting algorithm to the integral spectrum, where the user defines the elements and parameters to fit via a text document.

The algorithm, created by Vogt et al. ¹⁴, makes use of regions of interest (ROI) filtering, in which it integrates over certain elements' peak regions, and principle component analysis (PCA). First, PCA is done to identify only the elements and peaks that are very strongly apparent. This allows for the separation of noise from the true signal. Next, the principle components identified are numerically quantified, which is important for deconvoluting different element peaks with the same excitation energy, for example overlapping Au M_α and P K_α. Finally, ROI filtering may be applied to the numeric data by integrating over specified regions.

To relate counts to elemental concentrations, a well-quantified reference (often referred to as "standard") is measured under the same measurement conditions, geometry and energy, as the sample under study. This standard is often from Dresden AXO or from the National Institute of Standards and Technology (NIST). They cover a variety of different elements and come with tabulated elemental distributions. The normalization of the measured counts of the sample of interest to the counts of the standard under the same measurement conditions provides the basis for the elemental quantification for the sample of interest.

More specifically, MAPS identifies the elements and their concentrations of the standard either by the fact that the standard information is known by the program (as is the case for the AXO and NIST standards) or through data entered into a separate file (in the case of a different standard being used). From this information, the program relates the measured intensities of the standard elements under the measurement settings to the anticipated concentration embedded in MAPS. It then creates a scaling factor to adjust for any offset and extrapolates this scaling factor to all the remaining elements not included in the standard. The scaling factor then includes the offset from the measurement settings and the information provided within MAPS for the linear conversion of raw counts to areal density in µg/cm².

Here, we demonstrate how to make use of the program, MAPS, developed by Dr. S. Vogt, to quantify data acquired from fluorescence-capable beamlines at Argonne National Laboratory (ANL) ¹⁴. The data used for the demonstration was acquired at sector 2-ID-D of ANL using the measurement setup shown in Figure 1 of ¹⁰. The fitting procedure may also be applied to data taken from other beamlines, however, note that certain characteristics of the ANL beamlines are embedded in the program and will need to be updated.

Protocol

NOTE: Prior to beginning the fitting, it is important to know a few things about the measurements taken: the number of detector elements used - different beamlines use different detectors which are sometimes segmented into smaller sections from which the counts are read and compiled; the incident energy used; and the standard measured. This information will be applied throughout different aspects of the procedure.

1. Setting up the program

1. Download the IDL and the MAPS program
   NOTE: Links for downloading MAPS and IDL can be found at  http://www.stefan.vogt.net/downloads.html and http://www.harrisgeospatial.com/ respectively. Together, the program files may be expected to take up to approximately 20 MB. The actual space requirements for the fitting process, however, will actually be much larger and depend on the number of data files to be fit and their file sizes. The minimum device requirements for fitting are roughly 8 GB RAM, dual- or quad-core processor with speeds above 2.0 GHz. Again, the requirements increase dramatically with the file sizes being fit.
   1. To download IDL Virtual Machine, go to the link provided and create an account. After receiving email confirmation, log in to the website and select "Downloads" under the tab "My account". Within downloads, there should be an option for the most recent IDL software for Windows, Mac, or Linux. For the video, the version 8.5 of IDL Virtual Machine was used.
      NOTE: For the video, version 1.7.3.12 of MAPS was used. Version 1.7.3.12 and above can be used for the fitting of data acquired in both stepscan and flyscan modes.
   2. Click the link for the most recent version of MAPS and download the zip folder. The ZIP file should contain the MAPS IDL binary file as well as the files "compound.dat", "henke.xdr", and "xrf_library.csv".
   3. Move the latter three files to the folder "lib" in the IDL folder created in the documents upon installation. These files contain X-ray fluorescence-specific information needed for MAPS. For instance, the XRF library file stores all of the excitation energies for all of the elements.
   4. Place the icon for the MAPS program anywhere, however, it is often easiest to place it on the desktop. Doing so makes it easy to locate and run the graphical user interface (GUI).
2. Gather necessary files for preliminary fitting
   NOTE: The files that are required before performing a fitting are named "maps_settings.txt", "maps_fit_parameters_override.txt", data files ending in ".mda" and a standard file ending in ".mca". An example set of these files may be found in the supporting documents. The standard file provided is the AXO standard that was measured at sector 2-ID-D of Argonne National Laboratory using an incident X-ray beam energy of 10.4 keV. The same settings were used for the measurements of the data shown in this demonstration.
   1. Transfer the fit parameters file, the data files, and the standard files in the directory used during data acquisition to the computer on which the fitting with MAPS will be performed. Additionally, the maps settings file provided in the supplementary information may be used for any situation.
   2. Create a folder on the desktop. For example, create "C:\Users\user\Desktop\Fittingfiles". It is very important that no files or folders included in the pathway for the fitting contain a space, as MAPS will not be able to access them.
   3. Create a subfolder of "Fittingfiles" named "mda" and place all of the ".mda" data files acquired from the X-ray fluorescence measurements inside. Be sure to include the file for the representative map that will be used to generate the fit. For instance, in the video, the file "2idd_0220.mda" is used because it is most similar in dimensions and resolution to the majority of the remaining maps to be fit.
   4. Place the remaining files from Step 1.2 in the parent folder. These files will be edited in the steps described below.
      1. Place the standard file(s) (ending in ".mca") in the folder "Fittingfiles".
         NOTE: A well-suited standard should contain at minimum two elements in common with the samples being studied. In cases where no suitable commercial standard exists, a representative sample containing elements of interest in known quantities may be fabricated and used as a standard. In this situation, the created sample should be measured in the same way as any other standard.
      2. When using the AXO Dresden standard ¹⁵, rename the file to be "axo_std.mca". For a 1 element detector, only one file is required and should end with ".mca". However, if a 4-quadrant detector was used, there should be four standard files ending with ".mca0" through ".mca3".
      3. If using the National Institute of Standards and Technology (NIST) standard either 1833 or 1832 for thin film samples, name the file anything as the NIST standard is later selected manually rather than referenced within the program.
         NOTE: At this time, only one standard may be applied for the fitting at a time. However, if there is concern that a certain standard does not cover enough elements that are also contained in the sample of interest, it is possible to rerun the fittings using different standards each time. The data from each standard may then be compared for accuracy.
      4. If more than one standard is used, either relocate the fit ".h5" files from each run to a distinct folder labeled for each standard or rename the files, for instance ending in "_ <standard used>"
      5. If neither the AXO or the NIST standard is sufficient for the samples being studied, measure any other sample as a standard as long as it contains a known quantity of elements. In order for MAPS to know to use this newly created standard, add the file "maps_standardinfo.txt" to the parent folder, "Fittingfiles". This file has been included in the supplementary information and may be adapted directly for use.
         1. To use the created standard, open the standard info file and enter the file name for the standard, which may be named anything ending in the proper ".mca" formats, to be used in the line "FILENAME:" (if using multiple quadrants, enter only the name ending in ".mca0"). Next, list the elements that are in the standard separated by commas in the line "ELEMENTS_IN_STANDARD:".
         2. By multiplying the density of each element in the standard by the standard's thickness, calculate the areal density for each element in µg/cm². List these values in order with respect to the order of the elements listed in step 1.2.4.4. in the line "WEIGHT:", also separated by commas.
      6. Match the number of files named "maps_fit_parameters_override.txt" for the number of detector elements used. If only one detector was used, the file maintains the format "maps_fit_parameters_override.txt".
      7. If a four-quadrant detector was used, copy and paste the parameters file four times into the parent folder and then rename the extensions to range from ".txt0" to ".txt3".
      8. Check in the file "maps_settings.txt" that it lists the correct number of detector elements in the line "DETECTOR_ELEMENTS:" (it should be either 1 or 4).

2. Performing the fitting

1. Run MAPS
   1. Double click on the "maps.sav" icon located on the desktop and then click anywhere on the IDL pop-up window to continue.
   2. On the first window after opening, called "start up: MAPS v <version being used>", select "press to change parent dir" and then select the "Fittingfiles" folder created previously.
   3. Select "O.K. and go to configuration".
2. Generate a spectrum from a representative map to use for fitting
   1. From the configuration window, which can be accessed through "config + generate maps" → "general configuration", change the beamline setting to correspond to the beamline used for the measurements.
      1. If measurements were completed at a different beamline, verify which option in the program is for a beamline most similar in parameters to that of the used setup. Beamline capabilities for the Advanced Photon Source (APS) at ANL can be found at https://www1.aps.anl.gov/Beamlines/Directory. Comparing certain parameters such as resolution and flux can determine which ANL setting in the configuration window is most similar to the beamline used for the measurements.
   2. Choose "select mda files (and directory)" and the folder should open up to the "Fittingfiles" folder containing all necessary files. Next select a ".mda" file that corresponds to a representative map (it should be a map of similar composition and measurement parameters to the majority of the scans that will be fit using the parameters established from that representative map) and click "open".
      NOTE: If it does not open to the correct folder, it can be changed by selecting "parent dir" and the appropriate folder.
   3. Type in the incident energy used in keV.
   4. Select "start processing". When the process is done, various new folders have been created in the directory, and within the "img.dat" folder, there should be 1 or 5 files (depending on the number of detectors used) named ".h5".
      NOTE: In the case of a multi-element detector, one h5 file is generated for each segment of the detector (for example, files ".h50" through ".h53" for a 4-element detector) and one file that is the average of the individual elements.
      1. To view certain elements as processed, but not fit or quantified, enter these elements in the line "ELEMENTS_TO_FIT:" of the "maps_fit_parameters_override.txt" file. Include elements with L- or M-line peaks as "In_L" or "Au_M" for example. Otherwise, the processed file will only contain map information for the elements that were included in the fit parameters file prior to processing.
   5. To view the spectrum, go to "file" → "Open XRF image - avg or single element only" and locate in the "img.dat" folder the generated ".h5" file that will be used for the fitting of the remaining maps, then select "open".
      NOTE: There are a variety of ways to view the processed file, which contains the integral spectrum of the raw data, or the sum of the individual spectra acquired at each pixel within a map, as well as the full maps of the unfit and unquantified data. In most cases, it is best to view the data normalized to the upstream ion chamber, which can be done by going to the second drop down menu of the MAPS directory and selecting "US-IC".
      1. View the generated data by selecting "viewing" → "multi-element view (M)", which will show the processed maps for each of the elements.
         NOTE: At this point, the data appear to have been quantified, as they are represented in units of µg/cm², however, they have not yet been fit and therefore do not represent the properly quantified data. When the actual fitting is completed, it will override the ".h5" file, so it is extremely important to keep track of which files have been fit and which have simply been converted to ".h5" format, as was described in step 2.2.4.
      2. For the sake of the fitting, view the integral spectrum, so go to "viewing" → "plot integral spectrum". Figure 1 shows an example of what an integral spectrum (in white) will look like.
   6. Save the integrated spectrum data to a ".txt" file by selecting "generate output" → "export raw integrated spectra series (long)". Close the window.
      1. To save the image, use a screen capture program, as MAPS itself does not have the option to save the image.
      2. To replot the data, plot the exported integrated spectrum data against the energy range using any data visualization software.
         NOTE: The file with the integrated spectrum will be named "intspec <beamline>_ <samplenumber>.h5.txt" and will be found in the parent directory within the folder named "output".
3. Prepare the override file for fitting
   1. Go to "Tools" → "spectrum tool" then select the ".txt" file named "intspec <beamline>_ <samplenumber>.h5.txt"
   2. Open the file named "maps_fit_parameters_override.txt", which should now be located in the main directory as described in step 1.2.3., and enter the known settings as discussed below. This file is used for all situations, irrespective of the number of detector elements.
      1. In the line "DETECTOR_ELEMENTS:", make sure the number is the appropriate number for the number of detector elements used for the beamline.
      2. In the line "ELEMENTS_TO_FIT:", enter any missing anticipated elements, labeling L and M lines with suffixes "_L" and "_M". K-lines are assumed by default.
      3. In the line "COHERENT_SCT_ENERGY:", enter the incident energy used. In the following two lines, include upper and lower bounds for the energy range, as MAPS will fit for the exact incident energy. Usually, a range of ± 0.2 keV to ± 0.5 keV of the incident energy is sufficient.
      4. In the line "MAX_ENERGY_TO_FIT:", enter a value no less than 1 keV above the incident energy and similarly, in the line "MIN_ENERGY_TO_FIT:", enter a value no less than 1 keV.
      5. Towards the bottom of the file, there are the options "SI_ESCAPE_ENABLE:" AND "GE_ESCAPE_ENABLE:". Depending on the material of the detector element used (Si or Ge), enter a 1 for the element used and a 0 for the element not used. This will incorporate an escape factor for the detector element into the fit.
      6. Beneath the lines for 2.3.2.5, enter detector element names. It is very important that this information is correct, otherwise the quantification will be incorrect because it did not reference the proper channels during the process.
         1. To find the appropriate file names, open the ".mda" file by selecting "file" → "open mda file" then going to "viewing" → "multi element view (M)" and selecting on the bottom right hand side "select elements/detectors". This will open a window containing all the channels stored in the ".mda" file. Copy and paste the process variable (PV) names for the SRCurrent (e.g. SRCURRENT:S:SRcurrentAI.VAL), upstream and downstream ion chambers (e.g. US_IC:2idd:scaler1_cts1.C and DS_IC:2idd:scaler1_cts1.B) and four files for the elapsed live time, the elapsed real time, the input count rate, and the output count rate (e.g. ELT1:2iddXMAP:ElapsedLive, ERT1:2iddXMAP:ElapsedReal, ICR1:2iddXMAP:dxp1.InputCountRate, OCR1:2iddXMAP:dxp1.OutputCountRate). Finally, include the naming for the airpath (e.g. AIRPATH:0.0).
            NOTE: If it is unclear what names to use, ask the beamline scientist for assistance, as this step is critical for the procedure's accuracy.
   3. Save the file.
4. Identifying fitting parameters
   1. Try the fit by going to "analysis" → "fit spectrum".
      1. First, check that the energy range in the top of the window is inclusive of all the elements of interest. Generally, it is easiest to use the same range as set in step 2.3.2.3.
         NOTE: Next, for the first fitting, it is fine for the "no of iters", or number of iterations of the fitting, to be zero. This will be increased later on in the fitting process to improve the quality of the fit.
      2. Finally, at the bottom of the window where it says "do BATCH fit of ALL spectra", select the third button from the top labeled "w/ free E, FWHM, scatter, fixed tails" in order to run the first fit. In the main directory folder, a new file named "average_resulting_maps_fit_parameters.txt" will be created.
   2. On the left of the spectrum tool, select all of the drop down menus named "spec" to read "none" except for one, which should read "fitted". This will show only the fit overlaid on top of the spectrum, with the colored line representing the fit and the white line representing the measured spectrum respectively. From this image, it may become clear that certain major peaks do not overlap very well with the spectrum or even that the fit does not contain a peak at all where the spectrum clearly demonstrates one. If this is the case, changes will need to be made in the fit parameters file.
   3. Start by using the feature "add" → "element" and the (+) and (-) signs at the bottom of the spec tool to search for missing elements. This can be done by lining up the energy lines with peaks that the fit does not appear to include.
   4. If it is not entirely clear what elements might be missing, run the fit with a greater number of iterations to improve the fit and help elucidate which improvements still need to be made. This can be done by changing in the "spec fit" window the option "no of iters". Usually, doing at least 50 iterations will improve the fit significantly enough such that other needed improvements can be more easily identified.
   5. Add identified missing elements to the "maps_fit_parameters.txt" file (note: not the "average_resulting" file mentioned before) and save the file.
      NOTE: If there still appears to be some peaks not being included in the fitting, it is possible there are elements with pile ups. An element pile up occurs when two XRF photons (often from the same element with the same energy) strike the detector at the same time, being read as one photon with an energy that is the sum of the two original photons.
   6. To search for and include pile-up elements, use the same procedure as in 2.4.3, but instead by selecting "add" → "element+pileup". Once pile-ups are identified, add the element combinations to the line "ELEMENTS_WITH_PILEUP:" with the elements included in one pile-up separated by an underscore (e.g. Si_Si for a silicon-silicon pile-up or Si_Cl for a pile-up of Si and Cl photons).
   7. Evaluate the branching ratios of the L-line elements. Most K-line elements are included in the fit parameters file already and these are largely accurate and cited in literature ^16,17. L-lines, however, often need improvement as they have been found to vary with excitation energy ¹⁴. Currently, there is no such procedure for M-lines.
   8. Look at the L-line elements in need of improved branching ratios both in the sections "BRANCHING_FAMILY_ADJUSTMENT_L:"and BRANCHING_RATIO_ADJUSTMENT_L:".
      NOTE: "BRANCHING_FAMILY_ADJUSTMENT_L:" describes the accessible energy levels L1, L2, L3, which depend on the incident energy. For instance, if L1 > incident energy > L2, then 0, 1, 1 should be used for the respective adjustment values.
      1. To adjust the branching family, start by creating individual lines formatted with the element and then three 1.'s, as shown below.
         BRANCHING_FAMILY_ADJUSTMENT_L: In_L, 1., 1., 1.
         BRANCHING_FAMILY_ADJUSTMENT_L: Pb_L, 1., 1., 1.
      2. Adjust these numbers to shift the ratios of the peak intensities belonging to each group in relation to each other in an attempt to best match the intensity of the fit to the peak intensity of the integrated spectrum.
         NOTE: "BRANCHING_RATIO_ADJUSTMENT_L:" alternatively describes each individual L-shell transition, each with a unique energy. Changing the branching ratio changes the value in reference to the literature-sourced value imbedded in the MAPS program by multiplying the two values.
      3. To adapt these values, form a comparison of the height of the reference line (blue, yellow, or pink usually, depending on the branching family) observed through the "add" → "element" feature and the actual peak height and then calculate the branching ratio from rough estimation.
         NOTE: For example, if the L_β1 line is represented twice as high as the actual peak appears, then a branching ratio for that line should be 0.5 or 50% of the literature value.
   9. Save the fitparameters file and repeat the steps starting with step 2.4.2 until the fit appears to be reasonable. When the fit appears to be within reason, run the fitting once more but with at least 10k iterations.
      NOTE: This is done because during the quantification process, it is not possible to change the number of iterations used. Therefore, increasing the number of iterations at this stage of the process ensures that the information in the average resulting fit parameters file, which is updated with each fit attempt and later employed for the quantification procedure, is as accurate as possible.

3. Run the fitting

1. Rename files
   1. As the "average_resulting_maps_fit_parameters_override.txt" file is updated with each fitting, use this file for the actual fitting that will be applied to all of the ".mda" files that need quantification. First, rename the "maps_fit_parameters_override.txt" file that was being used for the fitting as "maps_fit_parameters_override_input.txt". Then rename the "average_resulting_maps_fit_parameters_override.txt" file as "maps_fit_parameters_override.txt".
   2. If using a 4-element detector, copy and paste the newly named "maps_fit_parameters_override.txt" file to create four additional files, and then change the extension of each such that they are named "maps_fit_parameters_override.txt0" through "maps_fit_parameters_override.txt3".
2. Create configuration file
   1. Go to "config + generate maps" → "general configuration and generate maps" and change the settings as in the beginning of the procedure to reflect the measurement setup.
   2. Select the used beamline or representative beamline and check "use fitting".
   3. Click "select mda files (and directory)" and select all of the ".mda" files to be fit from the "mda" folder. These files may have been added to the folder previously in step 1.2.3.), but if not, they may be copied and pasted into the folder at this time.
   4. On the right-hand side of the window, using the (+) and (-) signs to move right and left, scroll through the elements and check off those that are included in the fit parameters file that will be used for the fitting.
      1. Add elements missing from this window by checking off a box of an unused element, and then renaming the element in the field "ROI name", including "_L" or "_M" just as it is written in the fit parameters file. In addition to renaming the element, enter the energy for the center position of the line with the highest energy (i.e. if creating a tab for In_L, enter the value for In_Lα1 energy) from literature.
         NOTE: An easy way to find this value is by using the Hephaestus program which can be downloaded online as part of the "Demeter with Strawberry Perl" package, which can be found currently at https://bruceravel.github.io/demeter/ ¹⁸. Another option is to download the X-ray data booklet from the page http://xdb.lbl.gov/. In the Hephaestus program, it is possible to select an element from the periodic table, and scroll down to find the proper energy (note the unit difference between Hephaestus and MAPS).
   5. Also check off the boxes for "s_i", "s_e", "s_a", "TFY", and "Bkgnd".
   6. Once all the changes have been made, select "write settings to config file" in the top right corner. The file can be named anything, but must end in the extension ".cfg" and must be placed in the main folder, "Fittingfiles". This file will save all the settings entered in step 3.2.) for future use.
      NOTE: Selecting "read settings from config file" allows the user to open the file containing the stored fit settings again in the future. Additionally, the saved settings may be changed and updated by opening a ".cfg" file, entering the changes, and then selecting "write settings to config file" once more.
   7. Finally, if using the NIST standard (1832 or 1833), click "NBS" for the correct standard and select the standard file that should be used for the fitting.
3. Applying the fitting
   1. Select start processing. A series of boxes will pop-up, one for each standard element that is fit (depending on the number of detector elements used). This will not happen, however, if a standard other than the NIST or AXO is used.
      NOTE: Depending on the number and size of the ".mda" files being fit, the program may take anywhere from 30 minutes to hours to complete.

4. Checking the fit

1. Open the files for the fitted spectra by going to "file" → "Open XRF image - avg or single element only" and select under the "img.dat" folder one of the ".h5" files that have been created.
2. Following the same procedure as described in step 2.2.5.1, open the multi-element viewing window and normalize the data to the upstream ion chamber.
   1. To select which elements/channels are displayed, use the drop down menus for "# images X:" and "# images Y:" to select the dimensions of maps to be displayed. Next, select "select elements/detectors" and a pop-up menu will be displayed with check boxes for all of the channels contained in the fit ".h5" file.
3. Check that the values for the elements known to be in the sample make sense. An estimation for the concentration can be calculated if the sample thickness is known. To calculate, use the following equation:
   Concentration = elemental density × sample thickness
   NOTE: For example, an estimation of the concentration of copper in a 2 µm thick CIGS solar cell is about 18 µg/cm². Comparing this to the values for copper in Figure 2, it can be seen that the estimation is on the lower end, but that the quantification is of the right order of magnitude.
4. To be able to click through multiple scans that have been fit, go to "file" → "Update List of Current Files from Directory". This will place all of the files in the "img.dat" folder in the third drop down menu from the left of the MAPS window.
5. To export the data to a spreadsheet file or an Igor file, select "make combined ASCII files of maps" or "make combined IGOR files of maps" to export the data for each currently selected channel being shown in the window. Therefore, in order to export the data for all the channels, first select enough rows and columns for the number of elements and detectors that want to be viewed and exported and then click "select elements/detectors" to choose them. If it is desirable to have each of the channels stored as separate files, use the option "make separate…" for the respective file type.
6. To export the data for a batch of files, go to "file" →"Update list of Current Files from Directory". This will show all of the files in the "img.dat" folder. Then, having selected the elements to be exported, the option "export combined (separate) ASCII files of maps" will generate spreadsheet files for all of the ".h5" files in the folder.
   NOTE: The exported data will be saved within the "output" folder within the parent directory.

Results

An example of proper fitting results can be seen in the following Figures. Firstly, in Figure 1 a direct comparison is shown between a poor fit and a good fit for the integral spectrum. The bad fit is reparable by both ensuring no elements are missing, for instance copper, which has a clear peak in Figure 1(left) but is not being included in the fit, and adjusting the branching ratios of the L and K lines to improve the accuracy....

Discussion

The figures show the importance of fitting data using this procedure. Figures 1 (right) and 2 (bottom) show a representative result that should arise from a proper fitting. If there is an insufficient fit, the integral spectrum image will look noticeably off and the resulting quantified data will have errors in it, although these will be hard to detect in most cases. For certain sample types for which the standard is not representative of the elements in the sample, particularly in that the samples do no...