-
Notifications
You must be signed in to change notification settings - Fork 42
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
Segmentation fault?? Can not run rvtest!! #23
Comments
Sorry for the inconvenience.
Can you paste the full command line?
…On Mon, Apr 24, 2017 at 4:12 AM, zishang30 ***@***.***> wrote:
Hi, Xiaowei:
We have prepared tabixed vcf.gz file and PED file and kinship matrix and
prepare to run the rvtest. But when we run the rvtest it response the
mistake about Segmentation fault as follows:
[INFO] Program version: 20170210
[INFO] Analysis started at: Mon Apr 24 10:14:36 2017
[INFO] Loaded [ 3788 ] samples from VCF files
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 602 [
922000077 922000077 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1243 [
922003426 922003426 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1456 [
922003311 922003311 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1624 [
922001212 922001212 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1625 [
922000100 922000100 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1996 [
922000199 922000199 0 0 NA NA ] ...
[INFO] Loaded [ 3782 ] sample pheontypes
[WARN] Total [ 6 ] samples are dropped from VCF file due to missing
phenotype.
[WARN] Drop sample [ 922000077 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922003426 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922003311 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922001212 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922000100 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922000199 ] from VCF file due to missing phenotype
[INFO] Loaded 1850 male, 1932 female and 0 sex-unknonw samples from
phenotypes_all_f4.ped
[INFO] Analysis begins with [ 3782 ] samples...
[INFO] load 1 parameters.
[INFO] Meta analysis uses window size 500,000 to produce covariance
statistics under additive model
[INFO] Family-based model specified. Loading kinship file...
[INFO] DONE: Loaded kinship file [ S4F4all_kinship_matrix.kinship ]
successfully in [ 20.8 ] seconds.
[INFO] DONE: Spectral decomposition of the kinship matrix succeeded in [
268.2 ] seconds.
[WARN] Autosomal kinship loaded, but no hemizygote region kinship
provided, some sex chromosome tests will be skipped.
[INFO] Impute missing genotype to mean (by default)
[INFO] Analysis started
Segmentation fault
Why this happen ? and How can we fix it ?
This is part of GIANT project and the deadline is approaching.
Thank you very much!
Best regards
Zishan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJoiGAk-PFlC7kuWfkQ3IKB8bHOqZ-Lks5rzGeYgaJpZM4NF4zm>
.
|
The full command line are: We already enlarged the memory to 200GB, and try to run it in an large disk space(5TB), and update the rvtest to newest version, but we still have this problem... Now I try to run the rvtest without the kinshipmatrix command, the full command as follow: And the analysis start: So this fault is because of kinshipmatrix? Thank you very much for your reply! Best regards Zishan |
When you used rvtests without the kinship option, did you get analysis outputs successfully? |
Dear Xiaowei I suddenly remembered one point may be important to this segmentation fault: |
I think you kinship matrix can still be helpful after you excluding related individuals and using only Europeans. |
Dear Xiaowei Thank you very much for your reply. What I means yesterday is: Is there any possibility that the generated kinship matrix are not work well with VCF file because our study actually don't need kinship matrix? |
Dear Xiaowei I guess this segmentation fault may not only due to the kinship matrix itself but also to the software...? ParameterList created at Mon Mar 13 18:19:13 2017--inVcf "chr1_notmonomorph.vcf.gz" --out HRC_Chr1" --pheno "phenotypes_all.ped" --pheno-name "HT_INV" --meta "score,cov[Windowsize=500000]" --kinship "1_kinship_matrix.kinship" ........... The same input and the same command but this time we still got the Segmentation fault.... Could you just show me how to debug this segmentation fault in my computer ? Sorry to bring you so much trouble..... Best regards Zishan |
Can you please list the files under the analysis directory? |
Dear xiaowei still failed with segmentation fault...... BY the way, I consult this problem with the computer scientist in our center, he give me 3 possible reason:
And then the scientist who responsible for our server try to download the source code of rvtest and try to compile rvtest on our server, and found some error: Does this help you to fix the problem? |
没准编译器版本太老?能贴一下运行这个的结果么: |
Close it for now as we have not heard back from the issue submitter @zishang30 |
Hi, [INFO] Loaded [ 5098 ] samples from VCF files This is however nor present in the log file obtained from retest. Any explanation? |
You can safely ignore this error "strtod: Invalid argument". |
Hi, Xiaowei:
We have prepared tabixed vcf.gz file and PED file and kinship matrix and prepare to run the rvtest. But when we run the rvtest it response the mistake about Segmentation fault as follows:
[INFO] Program version: 20170210
[INFO] Analysis started at: Mon Apr 24 10:14:36 2017
[INFO] Loaded [ 3788 ] samples from VCF files
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 602 [ 922000077 922000077 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1243 [ 922003426 922003426 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1456 [ 922003311 922003311 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1624 [ 922001212 922001212 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1625 [ 922000100 922000100 0 0 NA NA ] ...
strtod: Invalid argument
[WARN] Skip: Missing or invalid phenotype type, skipping line 1996 [ 922000199 922000199 0 0 NA NA ] ...
[INFO] Loaded [ 3782 ] sample pheontypes
[WARN] Total [ 6 ] samples are dropped from VCF file due to missing phenotype.
[WARN] Drop sample [ 922000077 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922003426 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922003311 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922001212 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922000100 ] from VCF file due to missing phenotype
[WARN] Drop sample [ 922000199 ] from VCF file due to missing phenotype
[INFO] Loaded 1850 male, 1932 female and 0 sex-unknonw samples from phenotypes_all_f4.ped
[INFO] Analysis begins with [ 3782 ] samples...
[INFO] load 1 parameters.
[INFO] Meta analysis uses window size 500,000 to produce covariance statistics under additive model
[INFO] Family-based model specified. Loading kinship file...
[INFO] DONE: Loaded kinship file [ S4F4all_kinship_matrix.kinship ] successfully in [ 20.8 ] seconds.
[INFO] DONE: Spectral decomposition of the kinship matrix succeeded in [ 268.2 ] seconds.
[WARN] Autosomal kinship loaded, but no hemizygote region kinship provided, some sex chromosome tests will be skipped.
[INFO] Impute missing genotype to mean (by default)
[INFO] Analysis started
Segmentation fault
Why this happen ? and How can we fix it ?
This is part of GIANT project and the deadline is approaching.
Thank you very much!
Best regards
Zishan
The text was updated successfully, but these errors were encountered: