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

--salti is very time consuming #4

Open
yangwukaidi opened this issue Nov 30, 2023 · 12 comments
Open

--salti is very time consuming #4

yangwukaidi opened this issue Nov 30, 2023 · 12 comments

Comments

@yangwukaidi
Copy link

Dear Michael DeGiorgio, Ph.D.
Thank you very much for your reply.
As you said, the New software saltiLASSI works really well.
I found --salti to be very time-consuming.
I want to know a .vcf dataset of 650,000 loci from 30 individuals, and how long does it take to use --salti?
The commands I use are as follows:
lassip --spectra Z.chr12.lassip.hap.spectra.gz --salti --out Z.chr12
Looking forward to your reply.
Best wishs for you.
Yang

@szpiech
Copy link
Owner

szpiech commented Nov 30, 2023 via email

@yangwukaidi
Copy link
Author

Hi, Dear Zachary A. Szpiech Ph.D
Thank you very much for your reply.
As you said, increasing winstep size did reduce the time consuming, the software is running normally.
When I look at the result file for --salti(win51 step51), the m value is always 0, as follows,
1701418495825
However, this is not the case in the result file of -lassi(win51 step6), as follows,
1701418495820
Is it normal that m is always equal to 0? What's the point of m being equal to 0? Or how can I try to improve it?
Isn't this dataset only suitable for use -- lassi?
Looking forward to your reply.
Best.
Yang

@szpiech
Copy link
Owner

szpiech commented Dec 1, 2023 via email

@yangwukaidi
Copy link
Author

Hi.
The version I'm using is lassip v1.1.2.

@yangwukaidi
Copy link
Author

phase1Z12.vcf.gz
Z.chr12.lassip.hap.spectra.gz
Z.chr12.lassip.hap.stats.gz
Z.ids.pop.txt
Z.salti.chr12.lassip.hap.out.gz
All the relevant documents are attached, please check.
Yang.

@szpiech
Copy link
Owner

szpiech commented Dec 2, 2023 via email

@yangwukaidi
Copy link
Author

Hi, Dear Zachary A. Szpiech Ph.D
You're so helpful! I tested v1.1.1 using my test data and the results were normal.
So, I am currently running my complete data, I'll ask you if I have any questions.
Best.
Yang

@cgdmkns
Copy link

cgdmkns commented Jul 4, 2024

Dear @szpiech,
Since I'm facing the same issue as @yangwukaidi, I'm adding my comment here. I have a salti result for 780snp window with 100 step size, all m values are 0. I'm using v1.1.1.
The commands I used:(used parallel to estimate for each chromosome)
lassip --vcf chr1.vcf --hapstats --salti --calc-spec --winsize 780 --winstep 100 --out Chr1_bal --pop my_popID.txt
lassip --spectra Chr1_bal.lassip.hap.spectra.gz --salti --out chr1
Here is a part of the result.
image

Could it be related with win size?

@szpiech
Copy link
Owner

szpiech commented Jul 4, 2024 via email

@cgdmkns
Copy link

cgdmkns commented Jul 4, 2024

Sure, I'll do. 780 window size is based on the interval over which LD decayed below one-third of its original value relative to pairs of loci separated by 1 kb as stated in Harris and DeGiorgio,2020. I estimated the SNP density at that interval. But I'll give it a try for smaller windows as well. Thanks!

@cgdmkns
Copy link

cgdmkns commented Jul 10, 2024

Dear @szpiech,

It worked with the v1.2.0.Now I have m values different than 0.
I appreciate your help!

Cigdem

@szpiech
Copy link
Owner

szpiech commented Jul 10, 2024 via email

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

3 participants