-
Notifications
You must be signed in to change notification settings - Fork 8
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
crash in analyse_FadingMeasurement() #175
Comments
The best is here to throw a warning when the lengths differ and use the shortest common length. |
Using the shortest common length, the error moves further down: Error in data.frame(g_value, TC = tc, G_VALUE_2DAYS = g_value_2days[1], :
arguments imply differing number of rows: 1, 0 That occurs because Luminescence/R/analyse_FadingMeasurement.R Lines 591 to 613 in 759a114
Would it be OK in case T_0.5 <- data.frame(
T_0.5_INTERPOLATED = NA,
T_0.5_PREDICTED = NA,
T_0.5_PREDICTED.LOWER = NA,
T_0.5_PREDICTED.UPPER = NA
) The tests we have pass with that change, but I don't think that we actually test the output in such cases. |
Yes, this is a good solution! |
Another problem came up in this snippet of code: Luminescence/R/analyse_FadingMeasurement.R Lines 696 to 699 in 759a114
The evaluation of the expression() term generated this error:
Error in `plot_RLum.Analysis(object = object, subset = NULL, ...)`: object 'x' not found After a lengthy search, it turns out that using |
Fixed by #192. |
Using the object object built in
test_analyse_FadingMeasurement.R
, I can crash the function with a simple call:The crash occurs in this bit of code when
x = 2
as our object haslength(Lx_data) == 2
andlength(Tx_data) == 1
):Luminescence/R/analyse_FadingMeasurement.R
Lines 395 to 398 in 759a114
@RLumSK What's the best approach? Stopping if
length(Lx_data) != length(Tx_data)
, working only up to the longest common length, or something else again?The text was updated successfully, but these errors were encountered: