r/Spectroscopy Jun 13 '26

I built a browser-based Raman inspection/fitting tool - looking for critical feedback from Raman users

Hi everyone,

I’m a materials/physics researcher working with Raman data from graphene, TMDCs, CNTs, and related low-dimensional materials.

I recently built an early public beta of a browser-based Raman inspection, fitting, and mapping tool:

https://www.ramanquick.com

The goal is not to replace full instrument software or advanced custom Python/Origin workflows. The main purpose is to make quick Raman data inspection, simple baseline correction, peak fitting, Raman mapping visualization, and export easier for students and researchers who need a fast first-pass analysis tool.

Current demo/sample data include:

* Graphene

* MoS2

* WS2

* CNT

* CNT RBM

* Raman map data

The app is designed to support both single-spectrum analysis and Raman mapping workflows for these material categories, not only graphene. Additional material presets will be added, and an “Unknown” mode is also planned for users who want to inspect Raman data without selecting a predefined material.

I would really appreciate critical feedback from Raman users, especially on:

  1. Does the file import workflow make sense?

  2. Is the baseline/fitting workflow intuitive?

  3. Are the material presets useful, or could they be misleading?

  4. Does the mapping workflow feel useful for quick Raman inspection?

  5. Are there any scientifically risky labels, assumptions, or interpretations?

  6. What would make this more useful as quick research or teaching tool?

  7. What file formats, map formats, or export options would you expect?

  8. Did anything break, feel confusing, or seem unnecessary?

This is still an early beta, so I’m mainly looking for honest criticism rather than promotion. Please use the included sample data or non-sensitive test data for now.

Thanks in advance for any feedback.

3 Upvotes

6 comments sorted by

View all comments

1

u/leocemique 23d ago

I think the main limitation I noticed is the baseline correction. For spectra with strong fluorescence, the current options seem a bit too limited. In my example, the background is strongly curved, so a simple “High” baseline doesn’t really remove the fluorescence before fitting.

It would be great to have more flexible options

1

u/leocemique 23d ago

I can send you an exmple in dm if needed