# Correcting raw data, calculating peaks and indices in EEMS and absorbance (slope) parameters

### staRdom: spectroscopic analysis of dissolved organic matter in R

#### Matthias Pucher matthias.pucher@wcl.ac.at

#### March 13 2020

# 1 Introduction

staRdom is a package for R version 3 (R Core Team 2020) to analyse fluorescence and absorbance data of dissolved organic matter (DOM). The important features are:

- separating the components of the EEMs via PARAFAC/CANDECOMP (Murphy et al. 2013; Bro 1997; Helwig 2019).
- validating the model using a split-half analysis, the core consistency, the model fit or visually examining the residuals
- correcting excitation-emission-matrices (Murphy et al. 2013; Massicotte 2020)
- calculating fluorescence peaks and indices (Massicotte 2020)
- autochthonous productivity index / freshness index (BIX; Huguet et al. (2009), Fellman, Hood, and Spencer (2010))
- classical peaks based on manual peak picking (B, T, A, M, C; Coble (1996))
- fluorescence index (FI; McKnight et al. (2001))
- humification index (HIX; Ohno (2002))
- calculating common absorbance (slope) parameters:
  - absorbance at 254 nm (a254; Dobbs, Wise, and Dean (1972)),
  - absorbance at 300 nm (a300; Molot et al. (2005)),
  - ratio of absorbance at 250 to 365 nm (E2:E3; Haan and Boer (1987)),
  - ratio of absorbance at 465 to 665 nm (E4:E6; Summers, Cornel, and Roberts (1987)),
  - spectral slope within log-transformed absorption spectra range (S275-295, S350-400, S300-700) and the ratio of S275-295 to S350-400 (SR) (Helms et al. 2008),
  - the wavelength distribution of absorption spectral slopes (Loiselle et al. 2009) and
  - user-defined values and slopes can be extracted or calculated from the absorbance spectra.

staRdom has been developed and is maintained at WasserCluster Lunz (http://www.wcl.ac.at/) and the University of Natural Resources and Life Sciences, Vienna(http://www.boku.ac.at/).

staRdom comes with an Rmd template (infos on Rmd) where you can start your analysis with example data and add your personal data and parameters whenever you feel ready. We recommend to go interactively through the template while reading this vignette to get an overview of what is possible. Each version of staRdom provides a new template and usually using templates from different versions should be fine. In case you have difficulties running the calculations in the template, please use the template of the very same version as the installed staRdom package. As an advanced user, you can just include the functions in whatever calculations you want to do (please see details in the advanced vignetts). This vignette describes the template. If you are interested in the specific functions please refer to the help in R, which can be accessed by `help(function)` or in RStudio pressing F1 while the cursor is on the function name in the code.

Later in the vignette there is also a chapter about troubleshooting. If you experience problems you may find a useful solution there.

## 1.1 Aim of this document

> This file aims for beginners in R and describes an easy way of calculating EEM peaks and absorbance (slope) parameters by just setting variables (no use of functions) in an Rmd file. The options are limited and a PARAFAC analysis cannot be done this way. This way of more or less automatic analysis bears the risks of missing informations in the data and overlooking problems like outliers and noise in the data. For more possibilities, options and a PARAFAC analysis please refer to the vignette for the PARAFAC analysis.

## 1.2 Hint for beginners in R

If you are a beginner in R you may find some help at the R-Studio online-learning (https://docs.rstudio.com/), or Modern R with the tidyverse (https://b-rodrigues.github.io/modern_R/) by Bruno Rodrigues.

The package is available on CRAN and can be installed via `install.packages("staRdom")`.

# 2 Starting the analysis using the template

The template is accessible with the command `file.edit(system.file("EEM_simple_analysis.Rmd", package = "staRdom"))`. You can and should save this file if you want to preserve it. The example data is saved within the package structure and you can find the containing folders with the commands `system.file(package = "staRdom")`. Raw data is in the sub-folder “extdata”. The original settings in the template refer to sample data and you can do full featured test runs with that.

## 2.1 Output parameters

On top of the template there are the header parameters necessary to create a report with knitr (https://yihui.name/knitr/). Parameters can be changed and just show up in the final report (e.g. author, title) or alter the appearance of the document. It is possible to create reports in other file formats. Please find details at https://rmarkdown.rstudio.com/lesson-9.html.

The directory your generated files are saved in is set by output_dir at line 7. It is important that you keep the “;” at the end of the line. Folders are delimited by “/”. In RStudio, pressing the tab key while the cursor is in the path can reveal possible folders on your drive.

    title: "DOM analysis"
    subtitle: "EEM peak picking, absorbance slope parameters"
    date: "`r format(Sys.time(), '%B %e %Y')`"
    author: "WCL"
    knit: (function(inputFile, encoding) {
          output_dir = 'C:/some_folder/output/';
          rmarkdown::render(inputFile,
                            encoding=encoding,
                            output_file=file.path(output_dir,paste0('DOM_EEM_analysis_report_',format(Sys.time(), "%Y%m%d_%H%M%S"),'.htm')))
                            })

In case you want to run the code chunk-wise (https://rmarkdown.rstudio.com/lesson-3.html), you need to specify the output folder on line 61.

    # Set the directory where all output files are put in.
    # The directory is automatically created if it does not exist.
    # Folder delimiters can be / or \\. \, as it is usually used in Windows, will not work!
    output_dir = "C:/some_folder/another_folder" # e.g. output_dir = "C:/some_folder/output/"

## 2.2 Input parameters

Please be sure to use the same file names for your fluorescence data, absorbance data and meta data, as differing file names are often the reason for a non working analysis.

### 2.2.1 Fluorometer data (EEM)

The parameter sample_dir specifies the directory where your data files from the fluorometer are. They have to be in a text format (Cary Eclipse .csv files, Aqualog .dat files, Shimadzu .TXT files, Fluoromax-4 .dat files, Hitachi .TXT files, generic .CSV files). Samples can be stored in subfolders as well. Please be sure, that your file names are unique. File names must not contain " " (space) or “-” (minus) or start with a number. The command system.file() as used in the template EEM_simple_analysis.Rmd is used to access the example data and is not needed if you want to use your own data.

    # Set the directory with your sample files. Please see eem_read() help for details on file formats.
    # Sub folders are read in and are considered different sample sets.
    # Import is done with eem_read() (package eemR), please see details there.
    # The template refers to data coming with the package. Please use your data
    # by setting the path to your files!
    sample_dir = "C:/some_folder/input/fluor/" # e.g. sample_dir = "C:/some_folder/input/fluor/", system.file() accesses the example data coming with the package!
    # Set the used instrument (with hyphens!):
    # Cary Eclipse: "cary"
    # Aqualog: "aqualog"
    # Shimadzu: "shimadzu"
    # Fluoromax-4: "fluoromax4"
    # And furthermore, without hyphens:
    # generic csv, excitation column-wise: eem_csv
    # generic csv, emission column-wise: eem_csv2
    # Hitachi F-7000: eem_hitachi
    fluorometer = eem_csv

### 2.2.2 Photometer data (absorbance)

Absorbance data are needed for inner-filter effect correction and the calculation of the slope parameters. They are taken from the folder specified by `absorbance_dir`. The filenames or column designations must be identical to the EEM file names to link fluorescence and absorbance data distinctly. Please be sure, that your file names are unique. File names must not contain " " (space) or “-” (minus) or start with a number. For the calculations the light path length (in cm) used in the photometric measurement has to be set.

    ### Absorbance data ###
    #~~~~~~~~~~~~~~~~~~~~~#
    # Absorbance data is read from *.TXT or *.CSV files.
    # Either a directory containing one or more files can be named or a single file containing all samples.
    # Absorbance data is used for inner-filter-effect correction and calculation of the slope parameters.
    # Those steps can be skipped but keep in mind it is important for a profound analysis!
    #
    # path of adsorbance data as directory or single file, sub folders are not read:
    absorbance_dir = "C:/some_folder/input/absorbance/" # e.g. absorbance_dir = "C:/some_folder/input/absorbance/", system.file() accesses the exmaple data coming with the package!

    # Path length of absorbance measurement in cm that was used in absorbance measurement.
    # If it is set to "meta" data from the metadata table is used (details see below).
    absorbance_path = 5 # e.g. absorbance_path = 5

### 2.2.3 Meta data

In case your samples’ measurements differ and you need to set parameters sample-wise, you can set distinct dilution factors, photometer cuvette lengths and Raman areas in a table. You can skip that if dilution factors and cuvette lengths are similar and you used blank samples for calculating the Raman area. Distinct numbers can then be set as described below. A dilution factor of e.g. 10 means, there is 1 part sample and 9 parts ultrapure water added.

    ### Meta data ###
    #~~~~~~~~~~~~~~~#
    # Adding a table with meta data is OPTIONAL!
    # The table can contain dilution factors, path lengths of
    # the photometer and raman areas and is intended
    # for cases where different values should be used for different
    # samples. Each column can be used optionally.

    # read table with metadata as *.TXT or *.CSV
    # either a path or FALSE if no metadata file is used.
    metadata = system.file("extdata/metatable.csv",package = "staRdom") # e.g. metadata = "C:/some_folder/input/metatable.csv"", system.file() accesses the exmaple data coming with the package!

    ### Meta data: names of columns ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # designation of column with sample names
    col_samples = "sample"

    # if you want to use dilution factors (e.g. 10 if 1 part sample and 9 parts solvent) from the meta data table, state the name
    # of the column containing the dilution data and set dilution = "meta" (below)
    col_dilution = "dilution"

    # if you want to use the cuvette length (in cm) for the absorbance from the meta data table,
    # state the name of the column containing the cuvette lengths and set absorbance_path = "meta" (below)
    col_cuv_len = "cuv_len"

    # if you want to use the raman area (under the curve) data from the meta data table, state the name
    # of the column containing the raman areas and set raman_normalisation = "meta" (below)
    col_raman_area = "raman"

### 2.2.4 Spectral correction

Spectral correction is done to remove instrument-specific influences on the EEMs (DeRose and Resch-Genger 2010). Some instruments can do this automatically. Correction vectors should be provided in at least the same range as the EEM measurements. If this is not the case, the EEMs are cut to this range. Please provide paths to csv tables containing wavelengths in the first column and correction values in the second.

    #### Spectral correction of EEMs ####
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Some instruments, but not all need a spectral correction to compensate
    # for specific deviations in the measurements. A vector for emission and
    # excitation is used each. EEMs are cut to match the wavelength range of
    # the vectors if used. Please provide paths to csv tables containing
    # wavelengths in the first column and correction values in the second. If
    # you do not want spectral correction to be done, setting these two input
    # files it not necessary.
    # Emission correction vector
    Emcor <- system.file("extdata/CorrectionFiles/mcorrs_4nm.csv",package="staRdom") # e.g. "C:\folder\emcor.csv", FALSE
    # Excitation correction vector
    Excor <- system.file("extdata/CorrectionFiles/xc06se06n.csv",package="staRdom")

## 2.3 Write out results and plots

### 2.3.1 Results table

If you want to export your picked peaks and slope parameters as a table, set the parameter `output_xls = TRUE`. Exporting XLS files needs a properly configured Java environment. If any problems are encountered, a CSV is written to your output directory instead and can be opened with a spreadsheet software. Furthermore, you can specify the cell separator and decimal point of you data files in case a CSV file is written.

    ### Table output ###
    #~~~~~~~~~~~~~~~~~~#
    # Write a table with peaks and slope parameters.
    # Written as xls or, in case of missing java environment or the package xlsx as csv.
    output_xls = TRUE # e.g. TRUE

    # In case of a csv export you can define the separator and the decimal point here.
    out_sep_dec = c("\t",".") # e.g. out_sep_dec = c("\t",".")

### 2.3.2 Plots

The script offers several options for exporting plots. `output_overview_png` states whether overview plots containing a number of samples (`overview_number`) each are saved in the output directory and `output_single_png` is the parameter if you want to export single PNGs from each sample. The parameter `scale_col` defines if the colour range of all plots is synchronised. If you want to compare different samples, it is easier if the colour code has the same range. Weak peaks in samples with lower fluorophore presence than other samples can be found easier if the colours are not synchronised.

With the parameters `overview` and `single_plots` these plots can be included in the report using the same parameters `scale_col` and `overview_number`.

    ### Plot settings PNG ###
    #~~~~~~~~~~~~~~~~~~~~~~~#
    # State whether you want pngs of the single EEM spectra written in your output directory
    output_single_png = FALSE # e.g. TRUE

    ## State whether you want pngs of multiple EEM spectra written in your output directory
    output_overview_png = FALSE # e.g. TRUE

    ## number of EEM spectra plottet in each overview image
    overview_number = 6 # e.g. 6

    # The scaling of the different sample plots can be chosen.
    # Either all samples are coloured according to the range of the
    # complete sample set (TRUE) or each plot is scaled separately (FALSE).
    scale_col = FALSE # e.g. TRUE

    ### Plot settings report ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # This block defines which plots are included in the report.
    #
    # Add plots with several EEM samples per plot.
    # The number per plot is defined by overview_number above.
    overview = TRUE # e.g. TRUE

    # State whether you want plots from single EEM spectra in the report.
    single_plots = FALSE # e.g. TRUE

### 2.3.3 Save data to RData file

The data of the analysis can be stored in an Rdata file to keep track of your work or to deepen the analysis later (e.g. PARAFAC).

    #### Save data for further analysis in R ####
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # File name where data is stored in RData format in the output directory.
    # Set to FALSE if you dont want your eem data saved.
    # Date, time and file extension is added automatically so you do not overwrite previous saved data.
    data_file = "eem_data" # e.g. "eem_data"" or FALSE

    # Desired name for the variable containing the eem data.
    eem_name = "eem_list"

## 2.4 Data correction

Raw data from fluorometers and photometers bear several shortcomings. Murphy et al. (2013) addressed several ways of EEM data correction that are used in the staRdom template. Some correction methods need specific data (e.g. absorbance ) to be applied. Corrections can be necessary and can help you focus on certain aspects and information covered by noise otherwise. But depending on your aim they might not be necessary. Bro and Smilde (2003) offer additional information on correction of EEM data.

### 2.4.1 Absorbance baseline correction

The instrumental baseline drift in absorbance data can be removed by subtracting the mean of the absorbance at high wavelengths (Li and Hur 2017). The default is to use the spectrum between 680 and 700 nm but any other range can be set manually.

    #### Normalising absorbance data to baseline ####
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Absorbance data can be corrected by subtracting a baseline value from each sample.
    # In high wavelength ranges (default 680-700 nm), the absorbance is assumed to be 0.
    # The average value of that range (or any other range) is subtracted from the whole spectrum.
    # abs_norm can be set TRUE to use the default range, you can specify the desired range by a vector of length 2 and you can set it FALSE to skip this correction.
    abs_norm = TRUE # e.g. TRUE, c(700,800)

### 2.4.2 Dilution

If samples were diluted before the spectroscopic measurements, the dilution factor can be set here and the sample will be corrected accordingly. As an example a dilution factor of 10 means a 1:10 dilution (1 part sample and 9 parts ultrapure water). By setting `dilution = "meta"`, data from the meta table is used and each sample can be corrected by an individual dilution factor.

    ### Correction of diluted samples ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Set a dilution factor if your samples were diluted.
    # All samples are multiplied with this factor.
    # Please use a meta table (above) if your dilutions are differing
    # 1 for no dilution, 10 for dilution 1:10 (1 part sample and 9
    # parts ultrapure water), "meta" for data from meta table
    dilution = "meta" # e.g. 1 for undiluted samples

The reason of diluting a sample can be inner-filter effects that cannot be corrected conveniently if they are too high (Kothawala et al. 2013). On the contrary, absorbance data might be better analysed undiluted. To combine the results of diluted EEM measurements and undiluted absorbance measurements, the following parameter can be set to do this automatically. Please check the results because depending on your sample names, automatically guessed combinations might not be recognised correctly!

    # In case of diluted samples, two absorbance measurements of the
    # same sample in different dilutions might be present. If this is
    # the case, EEMs are renamed to the undiluted sample, absorbance
    # data might be multiplied by the dilution factor if it is only
    # presentas diluted sample. This can be done automatically. In the
    # final protocol a table shows, what has been done to the samples.
    # Please check this table and see, if the output is what you
    # wanted it to be!
    dil_sample_name_correction = FALSE

### 2.4.3 Spectral correction

The spectral correction is described above. Here you can set, whether a spectral correction should be applied. Correction vectors need to bet supplied above.

    #### Spectral correction of EEMs ####
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Some instruments, but not all need a spectral correction to compensate
    # for specific deviations in the measurements. Please sepecify, if you want
    # spectral correection to be done.
    spectral_cor = TRUE # e.g. TRUE, set to FALSE, if your instrument already provided EEMs with spectral correction

### 2.4.4 EEM range reduction

EEM data can be cut in both dimensions. Peaks are calculated before the reduction. Cut ranges are set with vectors containing the upper and lower limits: `c(lower,upper)`. If you want to avoid any cutting, set the vectors to `c(0,Inf)`. `Inf` means infinity, so the script keeps data from 0 to infinity. The script also allows to cut all samples to the size of the sample with the shortest range which is necessary if you want to perform a PARAFAC analysis. Cutting can be necessary to remove noisy data in advance of a PARAFAC analysis or to increase the visibility of important peaks in plots.

    ### Cut data to certain range ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Set a vector with range of wavelengths to be plotted and saved.
    # Peak picking is done before range reduction.
    # Emission wavelength:
    em_range = c(0,Inf) # e.g. c(300,500), c(0,Inf) to use everything

    # Excitation wavelength:
    ex_range = c(0,Inf) # e.g. c(300,500), c(0,Inf) to use everything

    # Cut all samples to fit largest range available in all samples
    cut_range_to_smallest = FALSE # e.g. FALSE

### 2.4.5 Blank correction

Blank samples are data from measuring ultrapure water. Systematic biases can be removed by subtracting the blank sample from each sample. The blank samples have to contain “nano”, “miliq”, “milliq”, “mq” or “blank” (cases are ignored) in the file name. Regular samples must not contain one of these words. Blanks have to be in the same (sub)folder as the samples that are corrected with the certain blank. Multiple blanks in one (sub)folder are averaged. It needs to be measured with each sample set (e.g. once a day) (Murphy et al. 2013) and kept together in one folder.

    ### Blank correction ###
    #~~~~~~~~~~~~~~~~~~~~~~#
    # A blank sample is subtracted from each sample. Blank samples have to be
    # in the same (sub)folder as the according EEM samples. So different blanks are used
    # for different subsets. The file names of the blanks have to contain nano,
    # miliq, milliq, mq or blank (cases are ignored). Other samples must not
    # contain these words in their names respectively!
    blank_correction = FALSE # e.g. FALSE

### 2.4.6 Correct inner filter effects

The inner-filter effect is caused by absorbance that blocks light in the pathway from the source to the sensor during fluorescence measurements. To apply the inner-filter effects correction described in Kothawala et al. (2013), absorbance data have to be measured for each sample. By knowing the exact absorbance, this effect can be mathematically corrected. In case of a total absorbance greater than 1.5, the sample has to be diluted because otherwise, the linear relationship is not appropriate anymore.

    ### Inner filter effect correction ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Inner filter effects are corrected. Absorbance data is needed. File or column designations
    # of the absorbance data have to resamble file names of the EEM data.
    ife_correction = TRUE # e.g. FALSE

### 2.4.7 Remove and interpolate scattering

Diagonal scatter peaks hinder the analysis of EEM data as they usually are much greater than peaks from DOM. They can be partly removed by subtracting the blank sample as described above. Diagonal peaks are called Rayleigh and Raman peaks of first and second order. They can also make a PARAFAC analysis impossible. Senesi (1990), Lakowicz (2006) and Coble et al. (1990) offer additional information.

The width of the removed scatter slot can be set. Make sure not to lose too much data while still removing the whole peak. If you use the interpolation below, a remaining diagonal peak hints at insufficient width. Elcoroaristizabal, Bro, and Alonso (2015), Bahram et al. (2006) and Zepp, Sheldon, and Moran (2004) suggest an interpolation of the removed scattering prior to a PARAFAC analysis and offer a description.

    ### Remove scattering and interpolate missing data ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Scattering is removed from the EEM spectra.
    remove_scatter <- c(TRUE, TRUE, TRUE, TRUE) # logical values, ordered by raman1,raman2,rayleigh1,rayleigh2

    # Set the width of removed scatter slot (usually 10 to 20).
    # If you can still see traces of scattering after interpolation,
    # this value should be increased. You can specify a vector containing
    # separate widths for each scatter c(15,16,16,14), ordered by raman1,raman2,rayleigh1,rayleigh2
    # In case one or more scatter peaks are skipped, this vector must remain of length 4 and positions of the certain widths must be kept.
    remove_scatter_width = c(15,15,15,15) # e.g. 15 or c(15,15,15,15)

    # state whether removed scattering should be interpolated
    interpolation <- TRUE # e.g. TRUE

### 2.4.8 Raman normalisation

Fluorescence intensities can differ between analyses on different fluorometers, different settings or different days on the same fluorometer. The so-called Raman normalisation makes samples comparable and normalises fluorescence intensities to Raman units. In staRdom, it can be applied in two ways. Either you use a blank sample (details see at chapter Blank correction above) to calculate the value for the normalisation (Lawaetz and Stedmon 2009) or you provide a certain value, that is used. Fixed values for each sample can be set in the meta table as well.

    ### Raman normailsation ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~#
    # State whether a Raman normalisation should be performed
    # Either "blank" if a blank is present in each (sub)folder of the EEM data.
    # Blank samples have to be in the same (sub)folder as the EEM samples. So
    # different blanks are used for different subsets. The file names of the
    # blanks have to contain nano, miliq, milliq, mq or blank (cases are ignored).
    # Other samples must not contain these words in their names respectively!
    # Normalisation is then calculated with this blank, the raman area as a number
    # or "meta" if the raman areas should be taken from the meta data table.
    raman_normalisation = "blank" # e.g. "blank", FALSE, 160, "meta"

### 2.4.9 Smoothing

For calculating the peaks, the EEMs can be smoothed. If so, peaks and indices are calculated from smoothed EEMs but these are not saved. The smoothing parameter specifies the size of a moving average window in nm.

    ### Smooth data for peak picking ###
    #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
    # Moving window size for smoothing data along excitation wavelengths.
    # Data must be interpolated if you want to use smoothing.
    # This is used for peak picking but not saved.
    smooth = 4 # e.g. FALSE, 4

## 2.5 Running the analysis

If you reach the box below in the template, all parameters are set and you can finally run the analysis.

    #############################################
    #                                           #
    #       THERE ARE NO SETTINGS BELOW.        #
    #  YOU CAN KLICK "KNIT" AT THE MENU BAR.    #
    #  In case of errors, chunk-wise execution  #
    #     of the code can reveal problems!      #
    #                                           #
    #     Please read the help of the used      #
    #        functions if you encounter         #
    #               any problems:               #
    #   Press F1 while cursor in function or    #
    #   type help(function) in command line!    #
    #                                           #
    #             Please read the               #
    #        error messages carefully!          #
    #    Naming of the input files and table    #
    #     column and row names is crucial!      #
    #                                           #
    #############################################

You can run the script by clicking the “Knit” button in the toolbar of RStudio. At the first run of the script you may be asked if you want to install several packages. Please confirm. This can take some time. Your generated files are placed in your specified output folder. In case you experience problems, consider to start over with a “fresh” template.

# 3 Installation

The script is running in R environment (R Core Team 2020). Using a graphical user interface like RStudio (https://www.rstudio.com/) can help beginners to get into it.

You can install staRdom via RStudio by klicking Tools -> Install Packages… or by entering the command `install.packages("staRdom")` in the command line.

If any of the programs are already installed on your computer, you can skip the respective step. In case of problems while running the script, consider re-installing/updating the respective programs.

## 3.1 R

Download:

https://cran.r-project.org/mirrors.html

Installation manual:

https://cran.r-project.org/doc/manuals/r-release/R-admin.html#R-Installation-and-Administration

## 3.2 RStudio

Download:

https://www.rstudio.com/products/rstudio/download/#download

Please choose the installer for your operating system, not the zip/tarballs.

Install RStudio by running the setup.

## 3.3 Optional software

Optionally(!) you need a Java runtime environment to import data from XLS files and a TeX environment (e.g. MikTeX for Windows) to export PDF files. You can use the script to the full extend without those.

# 4 Troubleshooting

## 4.1 Peaks table shows NAs

NA stands for ‘Not available’ and means the wavelength range of the certain peak is missing. Be sure that you measured the range of the certain peak on your instrument.

## 4.2 Only some sample plots show peaks

If samples differ considerably in the amount of DOM, scaling might be a problem. You can scale each sample plot separately by setting `scale_col = FALSE`.

## 4.3 I cannot read csv files in MS Excel

If you encounter problems with reading csv files please visit:

https://support.office.com/en-us/article/Import-data-using-the-Text-Import-Wizard-40c6d5e6-41b0-4575-a54e-967bbe63a048

## 4.4 I get error messages concerning my output directory

Be sure the specified drive and folder existis on your system (e.g. C:/) and you have write access.

# References

Bahram, Morteza, Rasmus Bro, Colin Stedmon, and Abbas Afkhami. 2006. “Handling of Rayleigh and Raman Scatter for PARAFAC Modeling of Fluorescence Data Using Interpolation.” Journal of Chemometrics 20 (3-4). Wiley: 99–105. https://doi.org/10.1002/cem.978.

Bro, Rasmus. 1997. “PARAFAC. Tutorial and Applications.” Chemometrics and Intelligent Laboratory Systems 38 (2). Elsevier BV: 149–71. https://doi.org/10.1016/s0169-7439(97)00032-4.

Bro, Rasmus, and Age K. Smilde. 2003. “Centering and Scaling in Component Analysis.” Journal of Chemometrics 17 (1). Wiley: 16–33. https://doi.org/10.1002/cem.773.

Coble, Paula G. 1996. “Characterization of Marine and Terrestrial DOM in Seawater Using Excitation-Emission Matrix Spectroscopy.” Marine Chemistry 51 (4). Elsevier BV: 325–46. https://doi.org/10.1016/0304-4203(95)00062-3.

Coble, Paula G., Sarah A. Green, Neil V. Blough, and Robert B. Gagosian. 1990. “Characterization of Dissolved Organic Matter in the Black Sea by Fluorescence Spectroscopy.” Nature 348 (6300). Springer Science; Business Media LLC: 432–35. https://doi.org/10.1038/348432a0.

DeRose, Paul C., and Ute Resch-Genger. 2010. “Recommendations for Fluorescence Instrument Qualification: The New ASTM Standard Guide.” Analytical Chemistry 82 (5). American Chemical Society (ACS): 2129–33. https://doi.org/10.1021/ac902507p.

Dobbs, Richard A., Robert H. Wise, and Robert B. Dean. 1972. “The Use of Ultra-Violet Absorbance for Monitoring the Total Organic Carbon Content of Water and Wastewater.” Water Research 6 (10). Elsevier BV: 1173–80. https://doi.org/10.1016/0043-1354(72)90017-6.

Elcoroaristizabal, Saioa, Rasmus Bro, and Jose Antonio Garcand Lucio Alonso. 2015. “PARAFAC Models of Fluorescence Data with Scattering: A Comparative Study.” Chemometrics and Intelligent Laboratory Systems 142 (March). Elsevier BV: 124–30. https://doi.org/10.1016/j.chemolab.2015.01.017.

Fellman, Jason B., Eran Hood, and Robert G. M. Spencer. 2010. “Fluorescence Spectroscopy Opens New Windows into Dissolved Organic Matter Dynamics in Freshwater Ecosystems: A Review.” Limnology and Oceanography 55 (6). Wiley: 2452–62. https://doi.org/10.4319/lo.2010.55.6.2452.

Haan, H. De, and T. De Boer. 1987. “Applicability of Light Absorbance and Fluorescence as Measures of Concentration and Molecular Size of Dissolved Organic Carbon in Humic Lake Tjeukemeer.” Water Research 21 (6). Elsevier BV: 731–34. https://doi.org/10.1016/0043-1354(87)90086-8.

Helms, John R., Aron Stubbins, Jason D. Ritchie, Elizabeth C. Minor, David J. Kieber, and Kenneth Mopper. 2008. “Absorption Spectral Slopes and Slope Ratios as Indicators of Molecular Weight, Source, and Photobleaching of Chromophoric Dissolved Organic Matter.” Limnology and Oceanography 53 (3). Wiley: 955–69. https://doi.org/10.4319/lo.2008.53.3.0955.

Helwig, Nathaniel E. 2019. Multiway: Component Models for Multi-Way Data. https://CRAN.R-project.org/package=multiway.

Huguet, A., L. Vacher, S. Relexans, S. Saubusse, J.M. Froidefond, and E. Parlanti. 2009. “Properties of Fluorescent Dissolved Organic Matter in the Gironde Estuary.” Organic Geochemistry 40 (6). Elsevier BV: 706–19. https://doi.org/10.1016/j.orggeochem.2009.03.002.

Kothawala, Dolly N., Kathleen R. Murphy, Colin A. Stedmon, Gesa A. Weyhenmeyer, and Lars J. Tranvik. 2013. “Inner Filter Correction of Dissolved Organic Matter Fluorescence.” Limnology and Oceanography: Methods 11 (12). Wiley: 616–30. https://doi.org/10.4319/lom.2013.11.616.

Lakowicz, Joseph R., ed. 2006. Principles of Fluorescence Spectroscopy. Springer US. https://doi.org/10.1007/978-0-387-46312-4.

Lawaetz, A. J., and C. A. Stedmon. 2009. “Fluorescence Intensity Calibration Using the Raman Scatter Peak of Water.” Applied Spectroscopy 63 (8). SAGE Publications: 936–40. https://doi.org/10.1366/000370209788964548.

Li, Penghui, and Jin Hur. 2017. “Utilization of UV-Vis Spectroscopy and Related Data Analyses for Dissolved Organic Matter (DOM) Studies: A Review.” Critical Reviews in Environmental Science and Technology 47 (3). Informa UK Limited: 131–54. https://doi.org/10.1080/10643389.2017.1309186.

Loiselle, Steven A., Luca Bracchini, Arduino M. Dattilo, Maso Ricci, Antonio Tognazzi, Andres C’ozar, and Claudio Rossi. 2009. “The Optical Characterization of Chromophoric Dissolved Organic Matter Using Wavelength Distribution of Absorption Spectral Slopes.” Limnology and Oceanography 54 (2). Wiley: 590–97. https://doi.org/10.4319/lo.2009.54.2.0590.

Massicotte, Philippe. 2020. EemR: Tools for Pre-Processing Emission-Excitation-Matrix (Eem) Fluorescence Data. https://github.com/PMassicotte/eemR.

McKnight, Diane M., Elizabeth W. Boyer, Paul K. Westerhoff, Peter T. Doran, Thomas Kulbe, and Dale T. Andersen. 2001. “Spectrofluorometric Characterization of Dissolved Organic Matter for Indication of Precursor Organic Material and Aromaticity.” Limnology and Oceanography 46 (1). Wiley: 38–48. https://doi.org/10.4319/lo.2001.46.1.0038.

Molot, Lewis A., Jeff J. Hudson, Peter J. Dillon, and Sean A. Miller. 2005. “Effect of pH on Photo-Oxidation of Dissolved Organic Carbon by Hydroxyl Radicals in a Coloured, Softwater Stream.” Aquatic Sciences 67 (2). Springer Science; Business Media LLC: 189–95. https://doi.org/10.1007/s00027-005-0754-9.

Murphy, Kathleen R., Colin A. Stedmon, Daniel Graeber, and Rasmus Bro. 2013. “Fluorescence Spectroscopy and Multi-Way Techniques. PARAFAC.” Analytical Methods 5 (23). Royal Society of Chemistry (RSC): 6557. https://doi.org/10.1039/c3ay41160e.

Ohno, Tsutomu. 2002. “Fluorescence Inner-Filtering Correction for Determining the Humification Index of Dissolved Organic Matter.” Environmental Science & Technology 36 (4). American Chemical Society (ACS): 742–46. https://doi.org/10.1021/es0155276.

R Core Team. 2020. R: A Language and Environment for Statistical Computing. Vienna, Austria: R Foundation for Statistical Computing. https://www.R-project.org/.

Senesi, Nicola. 1990. “Molecular and Quantitative Aspects of the Chemistry of Fulvic Acid and Its Interactions with Metal Ions and Organic Chemicals.” Analytica Chimica Acta 232. Elsevier BV: 77–106. https://doi.org/10.1016/s0003-2670(00)81226-x.

Summers, R.S., P.K. Cornel, and P.V. Roberts. 1987. “Molecular Size Distribution and Spectroscopic Characterization of Humic Substances.” Science of the Total Environment 62 (January). Elsevier BV: 27–37. https://doi.org/10.1016/0048-9697(87)90478-5.

Zepp, Richard G, Wade M Sheldon, and Mary Ann Moran. 2004. “Dissolved Organic Fluorophores in Southeastern US Coastal Waters: Correction Method for Eliminating Rayleigh and Raman Scattering Peaks in Excitationemission Matrices.” Marine Chemistry 89 (1-4). Elsevier BV: 15–36. https://doi.org/10.1016/j.marchem.2004.02.006.