-
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
flowClust segfault on a given hardcoded prior #17
Comments
Hi Mike! How did you build the prior? I didn't get any information in the help of the flowClust function. |
@SamGG see |
I am not able to pinpoint the exact line in > tmix_results <- flowClust(fr, varNames = channels, K = 5, trans = 0, usePrior = "yes", prior = prior)
Using the serial version of flowClust
==7673== Invalid read of size 1
==7673== at 0x4C2E0E2: strlen (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7673== by 0x4F32FD8: Rf_mkChar (envir.c:3722)
==7673== by 0x4F194B8: do_dotCode (dotcode.c:2504)
==7673== by 0x4F54D00: Rf_eval (eval.c:728)
==7673== by 0x4F55005: forcePromise (eval.c:520)
==7673== by 0x4F53A5E: bcEval (eval.c:4709)
==7673== by 0x4F546DF: Rf_eval (eval.c:624)
==7673== by 0x4F55005: forcePromise (eval.c:520)
==7673== by 0x4F53A5E: bcEval (eval.c:4709)
==7673== by 0x4F546DF: Rf_eval (eval.c:624)
==7673== by 0x4F55005: forcePromise (eval.c:520)
==7673== by 0x4F53A5E: bcEval (eval.c:4709)
==7673== Address 0x7ff8000000000000 is not stack'd, malloc'd or (recently) free'd
==7673==
*** caught segfault *** |
Here is the given prior > prior
$Mu0
[,1] [,2]
[1,] 0.10359586 0.03751837
[2,] 0.07607299 0.25967254
[3,] 0.03840841 0.28397826
[4,] 0.13033492 0.01071706
[5,] 0.01800955 0.12326509
$Lambda0
, , 1
[,1] [,2]
[1,] 413.4382049 0.1614980
[2,] -0.6939923 40.5273378
[3,] 4.8931884 7.0903981
[4,] -5.0695791 0.9772082
[5,] 0.9906558 0.4186971
, , 2
[,1] [,2]
[1,] -0.6939923 4.2322180
[2,] 13.1844080 7.0903981
[3,] -5.0695791 21.8155970
[4,] 70.8559750 0.4186971
[5,] 0.1614980 78.0131340
$Omega0
, , 1
[,1] [,2]
[1,] 4.442715e-07 0.000000e+00
[2,] 0.000000e+00 1.046215e-06
[3,] 7.673965e-08 0.000000e+00
[4,] 0.000000e+00 1.674699e-08
[5,] 3.078914e-08 0.000000e+00
, , 2
[,1] [,2]
[1,] 0.000000e+00 3.078914e-08
[2,] 4.442715e-07 0.000000e+00
[3,] 0.000000e+00 1.046215e-06
[4,] 7.673965e-08 0.000000e+00
[5,] 0.000000e+00 1.674699e-08
$nu0
[1] 5471.417 15281.385 8143.787 5255.161 22821.750
$w0
[1] 10942.83 30562.77 16287.57 10510.32 45643.50
> prior$nu0
[1] 5471.417 15281.385 8143.787 5255.161 22821.750 |
The help page of prior_flowClust of my current version of openCyto (1.12.1) does not give me much information about the value returned. |
I haven't verified it, but I suspect the invalid input value of Browse[2]> initprec
, , 1
[,1] [,2]
[1,] "0.0491791239549737" "0.00806431364015211"
[2,] "0" "0.486006746491884"
, , 2
[,1]
[1,] "Error in chol.default(solve(Lambda0[, , j])) : \n the leading minor of order 1 is not positive definite\n"
[2,] "Error in chol.default(solve(Lambda0[, , j])) : \n the leading minor of order 1 is not positive definite\n"
[,2]
[1,] "Error in chol.default(solve(Lambda0[, , j])) : \n the leading minor of order 1 is not positive definite\n"
[2,] "Error in chol.default(solve(Lambda0[, , j])) : \n the leading minor of order 1 is not positive definite\n"
which is captured here. But as far as I concern, ideally there should be a validity check (type and length) on each one of |
here is the reproducible data
The text was updated successfully, but these errors were encountered: