-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Bacteria] Streptococcus agalactiae CC 17 #843
Comments
Yes? I don't see what else we'd do. |
We discussed this with Jerome and Franz, and we figured that we will do like this indeed. The issue that may come up at some point, is if people want to add another strain of the same species, especially if that strain is parametrized differently. |
I think we'll start adding the strain suffix to the species ID then @jeanrjc - but for now, let's not worry about it. |
yes, it was my follow up question. But I'll stick to StrAga for now. |
Closed in #854 |
Question : Should I add this clone as if I were adding a species, or should I proceed differently ?
Description: Virulent strain responsible for most of GBS late onset infection in neonates.
Demographic information:
No estimation was done for S agalactiae, but we can use estimates from E coli, which ranges from around 0.5 to 20 generations per day. The standard generation time used is 1.
Ranges depending on the range of mutation rate estimates : ~[80k; 3M]
ref for estimation of mutation rate: Da Cunha et al. "Streptococcus agalactiae clones infecting humans were selected and fixed through the extensive use of tetracycline", 2014, Nat. Comm., 10.1038/ncomms5544
Chromosome structure:
Note: The assembly should be chromosome-level, i.e., not composed of thousands of scaffolds.
Recombination rates:
In Bacteria, recombination rate is the gene conversion rate, cross-over recombination rate is 0.
It requires a parameter for the mean recombination track length.
Mutation rate:
Demographic model:
Other information:
These are things we don't currently use, but will want to use in the future:
The text was updated successfully, but these errors were encountered: