Open Access
Table F.2.
GAUSSPY+ keywords mentioned throughout the text.
Symbol | Description | GAUSSPY+ keyword | Default |
---|---|---|---|
Essential parameters | |||
α1 | First smoothing parameter used in GAUSSPY decomposition (Sect. 2.1) | alpha1 | None |
α2 | Second GAUSSPY smoothing parameter; only used in two-phase decomposition (Sect. 2.1) | alpha2 | None |
S/Nmin | Minimum S/N for signal peaks in the data (Sect. 3.2.1) | snr | 3 |
𝒮min | Minimum significance value for signal peaks and fitted Gaussian components (Sect. 3.2.1) | significance | 5 |
More advanced settings | |||
Δμmax | Maximum difference in offset positions of Gaussian components for grouping (Sect. 3.3.1) | mean_separation | 2 (*) |
ΔΘmax | Maximum difference in FWHM values of Gaussian components for grouping (Sect. 3.3.1) | fwhm_separation | 4 (*) |
Θmin | Minimum value for the FWHM of fitted Gaussian components | min_fwhm | 1 (*) |
Θmax | Maximum value for the FWHM of fitted Gaussian components | max_fwhm | None(*) |
fa | Factor by which the maximum data value is multiplied to get a maximum limit for the fitted amplitude ai | max_amp_factor | 1.1 |
fΘ | Factor by which the FWHM value of a fit component has to exceed all other (neighbouring) fit components to get flagged (Sect. 3.2.2) | fwhm_factor | 2 |
fsep | Factor to determine the minimum required separation between two fit components before they are counted as blended (Sect. 3.2.2) | separation_factor |
![]() |
fw | Factor that determines the weight given to neighbouring spectra located at a distance of 1 and 2 pixels (Sect. 3.3.2) | weight_factor | 2 |
ℱneg. res. peak | Flag criterion for negative residual features (Sect. 3.2.2) | flag_neg_res_peak | True |
ℱΘ | Flag criterion for broad fit components (Sect. 3.2.2) | flag_broad | True |
ℱblended | Flag criterion for blended fit components (Sect. 3.2.2) | flag_blended | True |
ℱresidual | Flag criterion for fit results whose normalised residual values do not pass the tests for normality (Sect. 3.2.2) | flag_residual | True |
ℱNcomp | Flag criterion for fit results whose number of components are not compatible with neighbouring fits (Sect. 3.2.2) | flag_ncomps | True |
Npad | Number of spectral channels added to the left and right of signal intervals (Sect. 3.1.2) | pad_channels | 5 (*) |
Nmin | Minimum number of spectral channels the signal intervals in a spectrum must have (Sect. 3.1.2) | min_channels | 100 (*) |
ΔNmax | Maximum allowed difference in Ncomp between fit solution and weighted median number of components determined from all immediate neighbours (Sect. 3.2.2) | max_diff_comps | 1 |
ΔNjump | Maximum allowed difference in Ncomp between individual neighbouring spectra (Sect. 3.2.2) | max_jump_comps | 2 |
Njump | Maximum number of allowed ΔNjump occurrences for a single spectrum (Sect. 3.2.2) | n_max_jump_comps | 1 |
PLimit | Probability threshold for features of consecutive positive or negative channels to be counted as more likely to be a noise feature (Sect. 3.1.1, Appendix A) | p_limit | 0.02 |
p-value | p-value for the null hypothesis that the residual resembles a normal distribution (Sect. 3.3.1) | min_pvalue | 0.01 |
S/Nmin, fit | Minimum S/N (=ai/σrms) for fitted Gaussian components (Sect. 3.2.1) | snr_fit | None |
S/Nmin, neg | Minimum S/N for negative peaks in the spectrum (Sect. 3.2.2) | snr_negative | None |
S/Nspike | S/N threshold for noise spikes (Sect. 3.1.3) | snr_noise_spike | 5 |
SNR1 | S/N threshold used by GAUSSPY for the original spectrum | snr_thresh | None |
SNR2 | S/N threshold used by GAUSSPY for the second derivative of the smoothed spectrum | snr2_thresh | None |
ξ | Minimum number of spectral channels a peak has to contain on either side (Sect. 3.1.4) | order | 6 (*) |
𝒲min | Minimum weight threshold before phase 2 of the spatially coherent refitting routine is terminated (Sect. 3.3.2) | min_weight | 0.5 |
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.