Overview
The PL pipeline processes data in three stages:- File parsing: reads the spectral axis and intensity from uploaded .txt or .csv spectroscopy files, converting wavelength (nm) data to photon energy (eV)
- Metadata extraction: reads laser power, exposure time, accumulation count, and excitation wavelength from the filename, along with descriptive details such as sample identity and measurement location
- Intensity normalization: divides intensity by the product of power and exposure (and accumulation count, when present) so that spectra taken under different conditions can be compared on equal footing
Key Metrics
- Guide
- Technical Details
Adding Data
Upload .txt or .csv spectroscopy files through the data page. Each file should contain an energy (eV) or wavelength (nm) column and an intensity column. Processing starts automatically once the upload completes.The pipeline reads acquisition settings from the filename. Including laser power and exposure time in the filename enables automatic intensity normalization. Write each setting as a number followed by its unit, separated from other text by spaces, underscores, or hyphens:For example,
SampleA_center_532nm_2mW_30s_10ac.txt is read as 2 mW, 30 s, 10 accumulations, and 532 nm excitation. The pipeline also reads descriptive details such as sample ID and measurement location from the filename when it can.An x + digits token is read as an objective magnification instead when the number is a common objective (4, 5, 10, 20, 40, 50, 60, 63, 100, or 150). For those accumulation counts, use the ac form, such as 10ac.Viewing Results
Once processing completes, the workspace displays a spectrum chart plotting energy vs. intensity. A status badge indicates pipeline progress.If the filename does not include both laser power and exposure time, the spectrum displays unnormalized intensity. The chart doesn’t show whether normalization was applied; the
normalization_applied field in the API results indicates it. API only