Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spliceCorrection #57

Closed
aloboa opened this issue Jun 28, 2023 · 1 comment
Closed

spliceCorrection #57

aloboa opened this issue Jun 28, 2023 · 1 comment
Assignees
Labels
help wanted Extra attention is needed

Comments

@aloboa
Copy link

aloboa commented Jun 28, 2023

The documentation for the splice correction in ViewSpec actually states:
"This is usually done only for presentations and documentation or when using the data to match against
a spectral library, it is not meant to correct the data."

I am confused by this final recommendation. Does it hold for prospectr::spliceCorrection() as well? I see all spectra with "no steps"...

@l-ramirez-lopez l-ramirez-lopez self-assigned this Jun 28, 2023
@l-ramirez-lopez l-ramirez-lopez added the help wanted Extra attention is needed label Jun 28, 2023
@l-ramirez-lopez
Copy link
Owner

Dear @aloboa
The spliceCorrection() function in prospectr is intented for spectra that originate from device sensors with multiple detectors. When the spectra (covering different spectra regions) is concatenated, at the points of transition you will usually see baseline shifts. The idea behind spliceCorrection() is to remove such shifts/disturbances which are not coming from the samples being analysed. In this respect the correction is not only for visualization purposes, but also for any kind of spectral analysis you need to conduct on the spectra. For example, splice correction is crucial if you need to perform any derivative processing of the spectra, without it you will get undesired artefacts in your spectra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants