-
Notifications
You must be signed in to change notification settings - Fork 12
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
FAIL: test_common-uniq-inds.bash #23
Comments
(Everything works fine on my laptop with xUbuntu 14.04, R 3.3.1, MASS package 7.3.45, gcc 4.8.5, and GSL 1.16.) This test is executed from the bash script test_common-uniq-inds.bash. By comparing the log message and the bash script from line 124, I can say that the summary stats are fine, and that the problem arises when calculating the "raw" Bayes factors ("raw" because "not averaged over grid nor config"). Here is how I set up the tests. Each test has its own bash script, which does everything:
The test we are interested in, test_common-uniq-inds.bash, looks at the scenario where some individuals are common to all subgroups, but some are not. You can see this via the options Something must have changed in the C++ side or the R side. at this stage, I think something is more likely to have changed in the R side (from one version to a new one), no? (In any case, can you check your R version, as well as the MASS package, GSL and gcc versions?) So let's look at the R script. It "looks like" a C program: when it is executed, it loads all the functions and, at the very bottom of the file, it executes the function "main". Inside this 1st function, the problem must come from "getResultsOnSimulatedData". Inside this 2nd function, the problem must come from "calcRawAbfsOnSimulatedData". Inside this 3rd function, the problem may come from the "else" statement on line 1317. At this stage, one now has to debug where it comes from. I would suggest starting by re-running the C++ code and the R code on a single gene-snp pair. |
Tim, these are the versions of the software/libraries you and I are using:
So the only difference is the version of R. In your instructions, I don't see anywhere where you require a certain version of R. Have you tried running your tests with an earlier version of R (e.g., R 3.2)? Aside from the tests, it appears that you only use R to summarize and visualize the results of eqtlbma. Is this correct? If so, it seems that requiring a specific version of R is only critical for the tests; that is, it seems that |
In the installation instructions, I wrote: "If you want to run the tests successfully with As far as I remember, R is used in eqtlbma at 3 places:
I always use ps: to answer one of your previous question, in |
You are right, Tim---I didn't see the sentence about requiring R >= 2.15 for I was able to run all the tests successfully, but only after using R 3.3.1 instead of R 3.2.1. So it seems that the final test ( |
Thanks Peter for finding this! I updated the wiki. However, I didn't change the R code of |
Thanks, Tim! Peter On Thu, Oct 13, 2016 at 12:59 AM, Timothée Flutre notifications@github.com
|
Hi Tim,
I'm using eqtlbma 1.3.1. I successfully ran
./configure
andmake
(on a compute cluster with Scientific Linux 6). However, when I ranmake test
, this is the output I got (intest-suite.log
):Further:
A quick scan of the two files,
exp_bf_l10abfs_raw.txt.gz
andobs_bf_l10abfs_raw.txt.gz
, and the results are clearly not even close. I've attached the files from the test foilder so you can look at them yourself.Any idea what might be the problem? Perhaps it has something to do with the simulated data being different (e.g., because the sequence of pseudorandom numbers is different)?
Thanks,
Peter
tmp_test_30612.tar.gz
The text was updated successfully, but these errors were encountered: