Skip to content
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

vcf to gds #47

Closed
wangshuang2024 opened this issue Feb 24, 2024 · 7 comments
Closed

vcf to gds #47

wangshuang2024 opened this issue Feb 24, 2024 · 7 comments

Comments

@wangshuang2024
Copy link

Hello, @xihaoli.
In the script of "Varinfo_gds.R" and "gds2agds.R", it has two gds name.
gds_file_name_1 <- "freeze.5.chr"
gds_file_name_2 <- ".pass_and_fail.gtonly.minDP0.gds"

I wonder what the two documents represent and how they are produced? Thank you.

@xihaoli
Copy link
Owner

xihaoli commented Feb 24, 2024

Hi @wangshuang2024,

Thanks for reaching out. The gds_file_name_1 and gds_file_name_2 are both part of the target gds file name, separated by the chr number. For example, if the target gds file is for chromosome 1, and

gds_file_name_1 <- "freeze.5.chr"
gds_file_name_2 <- ".pass_and_fail.gtonly.minDP0.gds"

then after string concatenation, the target GDS file should have name freeze.5.chr1.pass_and_fail.gtonly.minDP0.gds.

Hope this helps.

Best,
Xihao

@wangshuang2024
Copy link
Author

Hi @wangshuang2024,

Thanks for reaching out. The gds_file_name_1 and gds_file_name_2 are both part of the target gds file name, separated by the chr number. For example, if the target gds file is for chromosome 1, and

gds_file_name_1 <- "freeze.5.chr"
gds_file_name_2 <- ".pass_and_fail.gtonly.minDP0.gds"

then after string concatenation, the target GDS file should have name freeze.5.chr1.pass_and_fail.gtonly.minDP0.gds.

Hope this helps.

Best, Xihao

Thank you , I got it.

@wangshuang2024
Copy link
Author

wangshuang2024 commented Feb 27, 2024

Hello, @xihaoli . I got another problem and hope you can help me.
In step 2 Annotate the variants.
for i in 'seq 1 22'; do Rscript /Rscript/staarpipeline/Annotate.R ${i}; done
After I run this code. I got an error.

Warning message:
NAs introduced by coercion
Error in 1:chr_splitnum : NA/NaN argument
Execution halted

How can I solve this? Thank you for your help.

@xihaoli
Copy link
Owner

xihaoli commented Feb 27, 2024

Hi @wangshuang2024,

It seems like your chr_splitnum in line 33 of Annotate.R is NA. Can you make sure whether the path of your file_DBsplit is set correctly? You may perform a manual check by setting chr <- 1 in line 24 of Annotate.R).

Thanks,
Xihao

@wangshuang2024
Copy link
Author

wangshuang2024 commented Feb 28, 2024

Hi @wangshuang2024,

It seems like your chr_splitnum in line 33 of Annotate.R is NA. Can you make sure whether the path of your file_DBsplit is set correctly? You may perform a manual check by setting chr <- 1 in line 24 of Annotate.R).

Thanks, Xihao

Thank you, @xihaoli . I figure out this problem. There is another error.

     used (Mb) gc trigger (Mb) max used (Mb)

Ncells 269061 14.4 654582 35 444042 23.8
Vcells 448538 3.5 8388608 64 1771786 13.6
[1] 1
No such file or directory (os error 2)
[1] 2
No such file or directory (os error 2)
[1] 3
No such file or directory (os error 2)
Selector index 1 is out of bounds. Index must be >= 1 and <= 0.

I check the path of "file_DBsplit","DB_path“,”xsv” and "output_path", they are all correct.

DB name like this "/reference/FAVOR/essentialDB/chr1.tar.gz"

@xihaoli
Copy link
Owner

xihaoli commented Feb 28, 2024

Hi @wangshuang2024,

You would need to first uncompress the chr1.tar.gz file before running Annotate.R.

Best,
Xihao

@wangshuang2024
Copy link
Author

Hi @wangshuang2024,

You would need to first uncompress the chr1.tar.gz file before running Annotate.R.

Best, Xihao

Thank you, Xihao. I solve these problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants