Help

How to use RamanQuick

Upload Raman data, inspect spectra, fit components, and export editable results.

Quick start

Choose a workspace

Use Analyze for spectrum or map inspection. Use Fitting when you need numerical peak decomposition for one spectrum.

Supported files

Supported formats

CSVTXTDATASCXYWDF

Text-based files should include Raman shift and intensity columns. WDF files are supported for single-spectrum fitting workflows.

Analyze

Analyze workspace

Analyze is best for quick inspection, visual comparison, map-oriented workflows, and editable outputs.

1

Upload spectrum or map data

Load Raman spectral data for quick inspection, visualization, and material-oriented analysis.

2

Inspect key Raman features

Review peak positions, intensity trends, and processed spectra before interpreting the result.

3

Apply basic preprocessing

Use baseline correction and spike removal only when needed. Keep the raw spectrum available for comparison.

4

Export editable outputs

Save analysis-ready data and figures for reports, presentations, and manuscript preparation.

Fitting

Fitting workspace

Fitting is designed for single-spectrum peak decomposition. It helps compare center position, FWHM, amplitude, area percentage, residuals, and fit quality.

1

Upload one Raman spectrum

Fitting is designed for single-spectrum peak decomposition and numerical comparison.

2

Choose fitting range

The fitting range is automatically initialized from the uploaded spectrum and can be adjusted manually.

3

Prepare the signal

Optional spike removal and baseline correction are applied before fitting.

4

Set components

Component 1 is initialized near the strongest detected peak. Additional components can be added manually.

5

Check fit quality

Review the total fit, component curves, residual, R², RMSE, and warning messages.

6

Export workbook

Download an Excel-compatible workbook containing parameters, curves, processing log, and numerical fit results.

Baseline Correction

Use baseline correction when the spectrum has a slowly varying background. Start with Simple Baseline and compare the original and corrected signals before interpretation.

Spike Removal

Use spike removal for narrow cosmic-ray-like artifacts. Avoid Strong mode unless the artifact is clear, because sharp Raman features can also be affected.

Processed signal

In Fitting, the processed signal is the spectrum after optional spike removal and baseline correction. This signal is used for fitting and export.

Export

Export workbook

Fitting export creates an Excel-compatible workbook for later analysis, plotting, and manuscript preparation.

Parameters

Component name, initial center, fitted center, shift, FWHM, amplitude, area percentage, and model.

Curves

Raman shift, processed signal, total fit, component curves, and residual values in the selected range.

Processing Log

File name, fitting range, baseline mode, spike removal mode, selected points, and component count.

Numerical Fit

R², RMSE, residual maximum, fit quality, and overfitting risk.

Sample data

Try RamanQuick with demo spectra and maps

Use these synthetic demo datasets to test upload, preprocessing, fitting, mapping, and export before using your own data.

Graphene demo

Synthetic spectrum with D, G, and 2D peak regions. Best for testing component fitting and export.

MoS₂ demo

Synthetic low-wavenumber spectrum with E₂g and A₁g-like features. Useful for testing TMDC fitting.

WS₂ demo

Synthetic spectrum with 2LA/E overlap and A₁g-like features. Useful for checking peak-overlap behavior.

CNT demo

Synthetic CNT spectrum with D, G, and G′ features. Useful for testing CNT Raman fitting.

CNT RBM demo

Synthetic low-wavenumber spectrum with multiple RBM peaks. Useful for testing RBM workflow behavior.

Graphene map demo

Synthetic coordinate Raman map using #X, #Y, #Wave, and #Intensity columns. Useful for map upload and heatmap testing.

These files are synthetic demo datasets for software testing only. They are not experimental data.

Troubleshooting

Common issues and fixes

Use this checklist when upload, graph display, fitting, or export results look unexpected.

The file does not load

Check whether the file contains numeric Raman shift and intensity columns. For WDF files, RamanQuick currently uses the first spectrum for single-spectrum fitting.

The graph looks flat or empty

Confirm that the Raman shift range and intensity columns were parsed correctly. Also check whether the selected fitting range contains data points.

The fitted peak center looks wrong

Adjust the component center manually or narrow the fitting range around the expected Raman feature.

Baseline correction changes the spectrum too strongly

Use Simple Baseline first. If the result still looks unreasonable, compare Original, Corrected, and Both views before fitting.

The residual looks structured

A structured residual usually means the model, fitting range, baseline, or number of components should be reconsidered.

Export values look different from expectation

Check whether the exported workbook uses the selected fitting range and processed signal rather than the full raw spectrum.

Interpretation note

RamanQuick helps organize Raman analysis and fitting workflows, but numerical fitting alone does not prove material assignment. Always check the raw data, preprocessing choices, residual structure, peak width, instrument conditions, and physical plausibility before drawing conclusions.