Git Product home page Git Product logo

ncov's Introduction

GitHub release (latest by date) See recent changes

About

This repository analyzes viral genomes using Nextstrain to understand how SARS-CoV-2, the virus that is responsible for the COVID-19 pandemic, evolves and spreads.

We maintain a number of publicly-available builds, visible at nextstrain.org/ncov.

See our change log for details about backwards-incompatible or breaking changes to the workflow.

Visit the workflow documentation for tutorials and reference material.

Download formatted datasets

The hCoV-19 / SARS-CoV-2 genomes were generously shared via GISAID. We gratefully acknowledge the Authors, Originating and Submitting laboratories of the genetic sequence and metadata made available through GISAID on which this research is based.

In order to download the GISAID data to run the analysis yourself, please see this guide.

Please note that data/metadata.tsv is no longer included as part of this repo. However, we provide continually-updated, pre-formatted metadata & fasta files for download through GISAID.

Read previous Situation Reports

We issued weekly Situation Reports for the first ~5 months of the pandemic. You can find the Reports and their translations here.

FAQs

  • Can't find your sequences in Nextstrain? Check here for common reasons why your sequences may not be appearing. You can also use clades.nextstrain.org to perform some basic quality control on your sequences. If they are flagged by this tool, they will likely be excluded by our pipeline.
  • For information about how clades are defined, and the currently named clades, please see here. To assign clades to your own sequences, you can use our clade assignment tool at clades.nextstrain.org.

Bioinformatics notes

Site numbering and genome structure uses Wuhan-Hu-1/2019 as reference. The phylogeny is rooted relative to early samples from Wuhan. Temporal resolution assumes a nucleotide substitution rate of 8 × 10^-4 subs per site per year. There were SNPs present in the nCoV samples in the first and last few bases of the alignment that were masked as likely sequencing artifacts.

Contributing

We welcome contributions from the community! Please note that we strictly adhere to the Contributor Covenant Code of Conduct.

Contributing to software or documentation

Please see our Contributor Guide to get started!

Contributing data

Please note that we automatically pick up any SARS-CoV-2 data that is submitted to GISAID.

If you're a lab and you'd like to get started sequencing, please see:


Get in touch

To report a bug, error, or feature request, please open an issue.

For questions, head over to the discussion board; we're happy to help!

ncov's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ncov's Issues

German translation

Like for French and Portugese, there exists a branch sit-rep_de for German translation, already.
I wonder why the file names contain the date. I know, they are linked to different versions according to the date. But for a highly dynamic document updating frequently, it looks a bit strange to me.

Translate March 13 sit-rep to French

Happy weekend @meriemelkaroui, @Maijin, @DanielThedie, @Simon-LoriereLab !

The situation report from March 13 is ready to be translated to French. A branch exists as sit-rep_fr where this can be done, and the file to translate is ncov_sit-rep_fr_2020-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_fr/narratives/ncov_sit-rep_fr_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation! You should have access to push to the sit-rep_fr, so there’s no need to create a pull request.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.)

Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_fr/sit-rep/fr/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your French-speaking colleagues, so we can get the information out there!

Note: You may know of other great resources available in French; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Because Nextstrain team members only speak so many languages, this is our best system for doing so. Thanks for understanding.

Please coordinate amongst yourselves on how to best complete the translations. You can trade off weeks; you can use an online editor like hackmd to translate together, whatever works best for you. But when finished, please push it to GitHub for proofreading and review.

@Simon-LoriereLab, since you have a background in the field, I won’t send it live without a review from you. This is to ensure we provide accurate information.

Thank you so very much for your hard work; you all are amazing!

Missing link from Germany to Italy nCov occurence on La Gomera?

@trvrb
I write you here, because i don't have a twitter account (Edit i made an account now)

I think there is a possibility that the missing link for the transmission in europe is on the canary islands.
After the virus was detected at Webasto employees, one contact of a employee went to his holiday to the canary islands with 4 friends, to La Gomera to be precise. (https://www.epochtimes.de/politik/deutschland/coronavirus-erreicht-la-gomera-deutscher-tourist-ist-erster-coronafall-in-spanien-a3142994.html sorry, it's german). He was hospitalized there (and may have infected others on Teneriffe). At least one of the friends went back to germany. I do not know which flight they used or if they were put into quarantine. There was no news report after this.

Sadly it seems neither the strain from La Gomera nor from mainland spain is on the GISAID database. It would be really interesting to see if there was a mutation which fits the others in europe. But i think the chance for that is quite high.
Maybe you have sources you can activate to get a genome analysis for the virus in spain/canary islands.

Thanks for your hard work and for the great tool at nextstrain.org.
Be healthy and good luck

Algorithman
(I watch this if you have questions)

Help

How canni make a 3player connect4 game using python(pygame) and sublime

Mandarin translation

@alvinxhan -- would be great if we would have a mandarin translation.

Emma just make placeholders for a spanish and zh translation. Feel free to get going. we can always rename files etc later.

Testing full-width marks in Japanese & Mandarin

I've set back up the sit-rep_zh branch so that @fzhang12 can test full-width marks in the narratives to ensure they work correctly in Markdown.

Both the zh and the ja files could be modified here if that's helpful! (To test both, if you want)

The files are here:
https://github.com/nextstrain/ncov/blob/sit-rep_zh/narratives/ncov_sit-rep_zh_2020-03-05.md (Mandarin)

https://github.com/nextstrain/ncov/blob/sit-rep_zh/narratives/ncov_sit-rep_ja_2020-03-05.md (Japanese)

And you can preview them live (after pushing) here:
https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_zh/sit-rep/zh/2020-03-05 (Mandarin)

https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_zh/sit-rep/ja/2020-03-05 (Japanese)

Translate situation report to French

The narrative from 2020-03-05 should be translated to French. A branch exists as sit-rep_fr where this can be done, and the file to translate is ncov_sit-rep_fr_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_fr/narratives/ncov_sit-rep_fr_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_fr/sit-rep/fr/2020-03-05

Please remember to push often as multiple people may be working on this translation!

perhaps replace s/COVID-19/SARS-CoV-2/g

The narratives talk about genomic analysis of COVID-19. I suppose technically this should be SARS-CoV-2 as that is what the virus is called, while the disease is COVID-19 (compare HIV and AIDS).

Update German Translation

This is an issue for updating the German version of the Situation Report to match the 30 Jan 2020 English version, when possible! Tagging @nicfel @tolot27 @rneher - sorry if I've missed anyone!

I have already created a branch sit-rep_de with the new file to be translated: ncov_sit-rep_de_2020-01-30.md

To make it easier to see what's changed, I've created a 'fake' diff file which shows the changes only in the text. You still must use the latest ncov_sit-rep_(lang)_2020-01-30.md file as your basis, because the code parts of the file have changed!

You can view the text differences here.

Note there are two entirely new slides - these I've put in the diff file with code so that you can spot them more easily. You see them in the newer version from line 207.

Sequence numbers now sometimes followed by </tag> - you do not have to this if you don't want - it was just to make it easier for us - in the time it took to update the narrative the number of sequences kept changing so this makes it easier to search and replace!

There may be multiple people working on this translation. so I recommend committing and pushing often to help avoid the work being done twice! Thank you all for your efforts!

Translate situation report to Spanish

The narrative from 2020-03-05 should be translated to Spanish. A branch exists as sit-rep_es where this can be done, and the file to translate is ncov_sit-rep_es_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_es/narratives/ncov_sit-rep_es_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_es/sit-rep/es/2020-03-05

Please remember to push often as multiple people may be working on this translation!

About json data using in "ncov \ auspice"

@emmahodcroft
Sorry to bother you again. We are currently engaged in scientific research and analysis of related new coronaviruses, hoping to help solve the epidemic situation in China. After learning about your data set and visualization, we have have benefited a lot. Would you mind us using the json results of your data in "ncov \ auspice"? We won't use it for commercial purposes and will sign the data source.
Thank you so much.

Translate Situation Report to Korean

The narrative from 2020-03-05 should be translated to Korean. A branch exists as sit-rep_ko where this can be done, and the file to translate is ncov_sit-rep_ko_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_ko/narratives/ncov_sit-rep_ko_2020-03-05.md

Note this file is in Markdown - it's important not to change any links! (Links to other-language versions of articles on Wikipedia are ok.)

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ko/sit-rep/ko/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Please also write your twitter handle and/or full name if you'd like to be attributed when we announce!

Translate Mar13 situation report into Dutch

Happy weekend @roanvanscheppingen, @Van-Doorslaer, @pleunipennings, @JSHuisman, @JiscaH !

The situation report from March 13 is ready to be translated to Dutch. A branch exists at sit-rep_nl where this can be done, and the file to translate is ncov_sit-rep_nl_2020-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_nl/narratives/ncov_sit-rep_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation! You should have access to push to the sit-rep_nl, so there’s no need to create a pull request. Please make sure you’ve accepted an invitation from me to join the ncov repo.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.)

Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_nl/sit-rep/nl/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your Dutch-speaking colleagues, so we can get the information out there!

Note: You may know of other great resources available in Dutch; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Because Nextstrain team members only speak so many languages, this is our best system for doing so. Thanks for understanding.

Please coordinate amongst yourselves on how to best complete the translations. You can trade off weeks; you can use an online editor like hackmd to translate together, whatever works best for you. But when finished, please push it to GitHub for proofreading and review.

@Van-Doorslaer, @pleunipennings, @JSHuisman, since you have backgrounds in phylogenetics, I won’t send it live without a review from one of you. This is to ensure we provide accurate information.

Thank you so very much for your hard work; you all are amazing!

one of the commands exited with non-zero exit code

[Wed Feb 19 21:48:25 2020]
Finished job 13.
1 of 17 steps (6%) done
ERROR: Problem reading in data/sequences.fasta:
Duplicate key 'Italy/INMI1/2020'
[Wed Feb 19 21:48:26 2020]
Error in rule filter:
jobid: 17
output: results/filtered.fasta
shell:

    augur filter             --sequences data/sequences.fasta             --metadata data/metadata.tsv             --include config/include.txt             --exclude config/exclude.txt             --min-length 15000             --output results/filtered.fasta
    
    (one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)

Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message

when I put the sequences.fasta into data file, this error was raised.
I have tried many ways but faild.
I don't know whether is the problem from my sequences.fasta. But I have arranged these data like what described in readme.

image

Update zh translation

We updated the situation report. It would be great if this update was reflected in the translations in a timely manner: @fzhang12 @alvinxhan @wdingx (Wei was a PhD student/post-doc with me and offered to help as well).

  • make a branch update-sit-rep_zh
  • copy old report
  • make changes (see diff below) and other updates/corrections that are necessary.

The list of changes seems long, but the biggest chunks of text are completely touched. many are mainly updated numbers.
Thank you very much for your work!

2c2
< title: Genomic analysis of nCoV spread. Situation report 2020-01-30.
---
> title: Genomic analysis of nCoV spread. Situation report 2020-01-25.
6,7c6,7
< date: "2020 Jan 30"
< dataset: "https://nextstrain.org/ncov/2020-01-30?d=map"
---
> date: "2020 Jan 25"
> dataset: "https://nextstrain.org/ncov/2020-01-25?d=map"
11c11
< # [Executive summary](https://nextstrain.org/ncov/2020-01-30/2020-01-30)
---
> # [Executive summary](https://nextstrain.org/ncov/2020-01-25)
16c16
< Using 42</tag> publicly shared novel coronavirus (nCoV) genomes, we examined genetic diversity to infer date of common ancestor and rate of spread.
---
> Using 27 publicly shared novel coronavirus (nCoV) genomes, we examined genetic diversity to infer date of common ancestor and rate of spread.
18c18
< * the 42</tag> sampled genomes are very similar, differing from the consensus by 0-7 mutations
---
> * 27 sampled genomes are very similar, differing by 0-5 mutations
25c25
< # [Coronaviruses](https://nextstrain.org/ncov/2020-01-30)
---
> # [Coronaviruses](https://nextstrain.org/ncov/2020-01-25)
29,31c29,31
< * General information on coronaviruses on [Wikipedia](https://en.wikipedia.org/wiki/Coronavirus) _2020-01-30_
< * Summary of the nCov outbreak on [Wikipedia](https://en.wikipedia.org/wiki/2019%E2%80%9320_Wuhan_coronavirus_outbreak) _2020-01-30_
< * Material provided by the [US CDC](https://www.cdc.gov/coronavirus/index.html) _2020-01-29_
---
> * General information on coronaviruses on [Wikipedia](https://en.wikipedia.org/wiki/Coronavirus) _2020-01-25_
> * Summary of the nCoV outbreak on [Wikipedia](https://en.wikipedia.org/wiki/2019%E2%80%9320_Wuhan_coronavirus_outbreak) _2020-01-25_
> * Material provided by the [US CDC](https://www.cdc.gov/coronavirus/index.html) _2020-01-23_
33,34d32
< * Interactive risk analysis by [MOBS-lab](https://datastudio.google.com/reporting/3ffd36c3-0272-4510-a140-39e288a9f15c/page/U5lCB) _2010-01-29_
< * Interactive risk analysis by [ROCS-lab](http://rocs.hu-berlin.de/corona/) _2010-01-29_
68c66
< # [Novel coronavirus (nCoV) 2019-2020](https://nextstrain.org/ncov/2020-01-30)
---
> # [Novel coronavirus (nCoV) 2019-2020](https://nextstrain.org/ncov/2020-01-25)
83c81
< As of January 30th over 7,914 cases and 170 deaths [have been reported](https://en.wikipedia.org/wiki/2019%E2%80%9320_outbreak_of_novel_coronavirus_(2019-nCoV)).
---
> As of January 25th, 2020 over 1400 cases and 42 deaths [have been reported](https://en.wikipedia.org/wiki/2019%E2%80%9320_outbreak_of_novel_coronavirus_(2019-nCoV)).
87c85
< While the outbreak seems to be centered in Wuhan, which is now [under quarantine](https://twitter.com/PDChina/status/1220060879112282117), the virus has spread throughout China and abroad, including Hong Kong, Singapore, Japan, and Thailand, as well as Europe, North America, South Asia, the Middle East, and Australia. Limited local transmission outside of China has been reported.
---
> While the outbreak seems to be centered in Wuhan, which is now [under quarantine](https://twitter.com/PDChina/status/1220060879112282117), the virus has spread throughout China and abroad, including Hong Kong, Macau, Thailand, Japan, South Korea, USA, and France. Limited local transmission outside of China has been reported.
102c100
< # [How to interpret the phylogenetic trees](https://nextstrain.org/ncov/2020-01-30)
---
> # [How to interpret the phylogenetic trees](https://nextstrain.org/ncov/2020-01-25)
137c135
<   <img alt="cartoon of phylogenetic tree and corresponding alignment, with samples labelled A-E" width="500" src="https://data.nextstrain.org/toy_alignment_tree.png"/>
---
>   <img alt="cartoon of phylogenetic tree and corresponding alignment, with samples labelled A-E" width="500" src="https://nextstrain-data.s3.amazonaws.com/toy_alignment_tree.png"/>
146c144
< # [Phylogenetic analysis](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree)
---
> # [Phylogenetic analysis](http://localhost:4000/ncov/2020-01-25?m=div&d=tree)
148c146
< Here we present a phylogeny of 42</tag> strains of nCoV that have been publicly shared.
---
> Here we present a phylogeny of 27 strains of nCoV that have been publicly shared.
153c151
< The colours represent the within-country region or US-state of isolation, with the x-axis representing nucleotide divergence.
---
> The colours represent the city/US-state of isolation, with the x-axis representing nucleotide divergence.
159c157
< Other viruses have between one and seven mutations.
---
> Other viruses have between one and five mutations.
167c165
< # [Phylogenetic Interpretation](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree)
---
> # [Phylogenetic Interpretation](https://nextstrain.org/ncov/2020-01-25?m=div&d=tree)
169c167
< We currently see little genetic diversity across the nCoV sequences, with 11</tag> out of 42</tag> sequences having no unique mutations.
---
> We currently see little genetic diversity across the nCoV sequences, with 8 out of 27 sequences having no unique mutations.
179,183c177
< We are starting to see groups of sequences that share mutations.
< One cluster contains sequences from Guangdong and four isolates from the US.
< Other clusters contain two to four isolates.
< Sequences in these clusters tend to be from more recent samples, suggesting that the virus has started to accumulate mutations as it spread in Wuhan and subsequently to other cities.
< There is currently no evidence that these mutations change how the virus behaves -- it is expected that RNA viruses mutate.
---
> At the moment, most mutations that can be observed are singletons – they are unique to individual genomes. Only the sequences that form the two clusters from Guangdong and the sequence form the USA share mutations – we will explore these in later slides.
185c179
< # [Within-family transmission 1](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree&f_location=Zhuhai)
---
> # [Within-family transmission 1](https://nextstrain.org/2020-01-25/ncov?m=div&d=tree&f_location=Zhuhai)
187c181
< There are three genetically-identical isolates from Zhuhai (Southeastern China, Guangdong Province) which form a cluster, sharing one unique mutation seen in no other isolate (you can hover your mouse over the branches to see which mutations are present).
---
> There are two genetically-identical isolates from Zhuhai (Southeastern China, Guangdong Province) which form a cluster, sharing one unique mutation seen in no other isolate (you can hover your mouse over the branches to see which mutations are present).
191,192c185
< Two of these cases (ending 028 and 040) are [known to come from a single family](https://twitter.com/JingLu_LuJing/status/1220143773532880896), again indicating human-to-human transmission.
< We don't have information about the third case.
---
> These two cases are [known to come from a single family](https://twitter.com/JingLu_LuJing/status/1220143773532880896), again indicating human-to-human transmission.
195c188
< # [Within-family transmission 2](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree&f_location=Shenzhen)
---
> # [Within-family transmission 2](https://nextstrain.org/ncov/2020-01-25?m=div&d=tree&f_location=Shenzhen)
197c190
< Of the six isolates from Guangdong Province (which includes the city of Shenzhen) we see four isolates which are genetically identical.
---
> Of the six isolates from Shenzhen (Southeastern China, Guangdong Province) we see four isolates which are genetically identical.
198a192,193
> Two of these mutations are also found in the sequence of the case in Washington, USA (more below).
> One sequence from Shenzhen has two additional mutations.
202,203c197
< Three of the sequences from Guangdong (ending F025, F013, and F012) are [known to come from a single family](https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(20)30154-9/fulltext), and almost certainly represent human-to-human transmission.
< 
---
> The sequences form Shenzhen are [known to come from a single family](https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(20)30154-9/fulltext), and almost certainly represent human-to-human transmission.
207d200
< # [Within-family transmission 2 - shared mutations](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree&f_location=Shenzhen,Los%20Angeles,Orange%20County,Seattle,Chicago,Phoenix)
209c202
< The three mutations found in this cluster are also present in the Arizona, USA isolate, and two of the mutations are found in three other USA isolates.
---
> # [Cases outside China](https://nextstrain.org/ncov/2020-01-25?c=country&d=tree&m=div)
210a204,205
> There are reported diagnostically confirmed nCoV cases in many East and South-East Asian countries, USA, Australia, and Europe.
> Vietnam has reported a case without travel history to Wuhan who possibly got infected from a [relative visiting from Wuhan](https://www.aljazeera.com/news/2020/01/china-coronavirus-outbreak-latest-updates-200123133559818.html).
214,216c209,211
< # [Within-family transmission 3](https://nextstrain.org/ncov/2020-01-30?m=div&d=tree&f_location=Paris)
< 
< Finally, the two sequences from France are identical, sharing one unique mutation, and one mutation also found in one of the USA isoaltes and the Taiwanese isolate.
---
> The only currently available sequence data for cases outside of China are the two cases from Thailand and one case from the USA, which are coloured here in yellow and red, respectively.
> The Thai samples are genetically identical to six Chinese sequences, including five isolated in Wuhan.
> The sequence from Washington, US, shares two mutations with the cluster of sequences from Shenzhen.
220,228c215,216
< The two french sequences are [known to be from the same family](https://www.thelocal.fr/20200129/coronavirus-in-france-what-you-need-to-know) - a Chinese couple from Wuhan.
< 
< 
< # [Cases outside China](https://nextstrain.org/ncov/2020-01-30?c=country&d=tree&m=div)
< 
< There are reported diagnostically confirmed nCoV cases in many East and South-East Asian countries, USA, Australia, the Middle East, and Europe.
< Vietnam, Japan, and Germany have reported transmission within the country, albeit always with a known link to Wuhan, China.
< 
< <br>
---
> The case from Washington, USA, had travelled to Wuhan.
> The most parsimonious explanation for the observed pattern of mutation sharing is the virus variant with the two shared mutations was circulating in Wuhan and was independently exported to Shenzhen and to the USA.
230,233d217
< The only currently available sequence data for cases outside of China are the two cases from Thailand, five from the USA, two from France, and one from Taiwan.
< The Thai samples are genetically identical to nine Chinese sequences, including seven isolated in Wuhan.
< Four sequences from the US share two mutations with the cluster of sequences from Shenzhen.
< The remaining sequence from the US shares a mutation with the sequence from Taiwan and the two from France.
235,240c219
< <br>
< 
< The most parsimonious explanation for the observed pattern of mutation sharing between the US and Shenzhen sequences is a virus variant with the two shared mutations was circulating in Wuhan and was independently exported to Shenzhen and multiple times to the USA.
< There is no evidence for a link between US sequences other than a link to Wuhan.
< 
< # [Dating the time of the most recent common ancestor](https://nextstrain.org/ncov/2020-01-30?d=tree)
---
> # [Dating the time of the most recent common ancestor](https://nextstrain.org/ncov/2020-01-25?d=tree)
253,257c232,233
< With the additional sequences shared during the past week, the tree now shows several distinct clusters such that our analysis from 2020-01-25 assuming a star-like topology is no longer appropriate.
< 
< We reproduce here our analysis based on data available up to 2020-01-25
< assuming a star-like phylogeny structure along with a Poisson distribution of mutations through time to estimate the time of the most recent common ancestor ('TMRCA') of sequenced viruses.
< **We found that the common ancestor most likely existed between mid-Nov and the beginning of Dec 2019. The biggest source of uncertainty is the substitution rate.**
---
> Here, we assume a star-like phylogeny structure along with a Poisson distribution of mutations through time to estimate the time of the most recent common ancestor ('TMRCA') of sequenced viruses.
> **We find that the common ancestor most likely existed between mid-Nov and the beginning of Dec 2019.**
260c236
<   <img alt="graph of TMRCA estimates based on different mutation rates" width="500" src="https://data.nextstrain.org/ncov_poisson-tmrca.png"/>
---
>   <img alt="graph of TMRCA estimates based on different mutation rates" width="500" src="https://nextstrain-data.s3.amazonaws.com/ncov_poisson-tmrca.png"/>
263,266c239,240
< Using the entire data set, the nextstrain analysis pipeline estimates that the common ancestor most likely existed between late-Nov and the beginning of Dec 2019.
< 
< There is a [confirmed case in Wuhan with onset date of Dec 1, 2019](https://twitter.com/trvrb/status/1220749265380593664), which would put an upper bound on the date of most recent common ancestor.
< The common ancestor of viruses sequenced to date might be later than this date though.
---
> As the more samples are sequenced, we expect the tree to show more structure, such that the star-like phylogeny topology is no longer a good assumption.
> At this point, phylodynamic estimates of the age of the epidemic will become feasible.
268,269c242
< More detailed modeling of the onset of the outbreak are onging.
< Despite considerable uncertainty, our best guess is remains late November/early December.
---
> There is a [confirmed case in Wuhan with onset date of Dec 1, 2019](https://twitter.com/trvrb/status/1220749265380593664), which would put an upper bound on the date of most recent common ancestor. And strongly suggests evolutionary rates of ~3.0 x 10^-4 are more plausible.
273c246
< # [Estimating the growth rate](https://nextstrain.org/ncov/2020-01-30?d=tree)
---
> # [Estimating the growth rate](https://nextstrain.org/ncov/2020-01-25?d=tree)
284,285c257
< Scientists at Imperial College London have used the number of cases observed outside of China to estimate the [total number of cases](https://www.imperial.ac.uk/mrc-global-infectious-disease-analysis/news--wuhan-coronavirus/) and suggested that there have been at least several thousand cases by 2020-01-22.
< With the additional exported cases since and the continued growth of confirmed cases in China, we currently have to expect at least 50000 cases to date.
---
> Scientists at Imperial College London have used the number of cases observed outside of China to estimate the [total number of cases](https://www.imperial.ac.uk/mrc-global-infectious-disease-analysis/news--wuhan-coronavirus/) and suggested that there have been at least several thousand cases.
288c260
< **We find plausible estimates of R0 between 1.8 and 3.5.**
---
> **We find plausible estimates of R0 between 1.5 and 3.5.**
290c262
< If we assume the outbreak started at the beginning of November 2019 (12 weeks ago), we find that R0 should range between 1.8 and 2.5, depending on how large ('n') the outbreak is now.
---
> If we assume the outbreak started at the beginning of November 2019 (12 weeks ago), we find that R0 should range between 1.5 and 2.5, depending on how large ('n') the outbreak is now.
292c264
<   <img alt="graph of R0 estimates with epidemic start 12 weeks ago" width="500" src="https://data.nextstrain.org/ncov_branching-R0-early_2020-01-29.png"/>
---
>   <img alt="graph of R0 estimates with epidemic start 12 weeks ago" width="500" src="https://nextstrain-data.s3.amazonaws.com/ncov_branching-R0-early.png"/>
295c267
< If we assume a more recent start, at the beginning of December 2019 (8 weeks ago), the estimates for R0 range between 2.2 and 3.5:
---
> If we assume a more recent start, at the beginning of December 2019 (8 weeks ago), the estimates for R0 range between 1.8 and 3.5:
297c269
<   <img alt="graph of R0 estimates with epidemic start 8 weeks ago" width="500" src="https://data.nextstrain.org/ncov_branching-R0-recent_2020-01-29.png"/>
---
>   <img alt="graph of R0 estimates with epidemic start 8 weeks ago" width="500" src="https://nextstrain-data.s3.amazonaws.com/ncov_branching-R0-recent.png"/>
299,300d270
< This estimates are broadly consistent with those by other scientists which mostly fall between R0=2-3, see for example <a href="https://www.biorxiv.org/content/10.1101/2020.01.25.919787v1">this preprint</a>.
< Importantly, R0 is a quantitity that depends strongly on the socio-economic context and infection control measures.
303c273
< # [Scientific credit](https://nextstrain.org/ncov/2020-01-30?d=map&c=author)
---
> # [Scientific credit](https://nextstrain.org/ncov/2020-01-25?d=map&c=author)
320,321d289
<  * Centers for Disease Control, R.O.C., Taipei, Taiwan
<  * Institut Pasteur, Paris, France
323c291
< # [Detailed scientific credit](https://nextstrain.org/ncov/2020-01-30?d=map&c=author)
---
> # [Detailed scientific credit](https://nextstrain.org/ncov/2020-01-25?d=map&c=author)
357d324
<    - Guangdong/20SF001/2020
364,370d330
<    - Guangdong/20SF174/2020
<    - Guangdong/20SF206/2020
<    - Guangdong/20SF207/2020
<    - Foshan/20SF207/2020
<    - Foshan/20SF210/2020
<    - Foshan/20SF211/2020
< 
376,384d335
<    - USA/AZ1/2020
<    - USA/IL1/2020
<    - USA/CA1/2020
<    - USA/CA2/2020
<  * Centers for Disease Control, R.O.C., Taipei, Taiwan
<    - Taiwan/2/2020
<  * Institut Pasteur, Paris, France
<    - France/IDF0372/2020
<    - France/IDF0373/2020

Update Spanish Translation

This is an issue for updating the Spanish version of the Situation Report to match the 30 Jan 2020 English version, when possible! Tagging @Chjulian

I have already created a branch sit-rep_es with the new file to be translated: ncov_sit-rep_es_2020-01-30.md

To make it easier to see what's changed, I've created a 'fake' diff file which shows the changes only in the text. You still must use the latest ncov_sit-rep_(lang)_2020-01-30.md file as your basis, because the code parts of the file have changed!

You can view the text differences here.

Note there are two entirely new slides - these I've put in the diff file with code so that you can spot them more easily. You see them in the newer version from line 207.

Sequence numbers now sometimes followed by </tag> - you do not have to this if you don't want - it was just to make it easier for us - in the time it took to update the narrative the number of sequences kept changing so this makes it easier to search and replace!

There may be multiple people working on this translation. so I recommend committing and pushing often to help avoid the work being done twice! Thank you all for your efforts!

French translation

@PierreBarrat has said he'll have a go at a French translation of the narrative! :)
I've created a page for it in the narratives folder, and will now create a branch as well. This issue is just for any necessary discussion/questions etc.

How to construct phylogenetic tree

I want to know the method for constructing phylogenetic tree used in this project.
Is it NJ or MP or ML?
Are there any informations?
Thank you.

Translate situation report to Mandarin

The narrative from 2020-03-05 should be translated to Chinese. A branch exists as sit-rep_zh where this can be done, and the file to translate is ncov_sit-rep_it_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_zh/narratives/ncov_sit-rep_zh_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_zh/sit-rep/zh/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Narratives Instructions Always in English

Instructions for how to use Narratives are always in English.

The instructions at the top of the first Narrative page are not from the Markdown file being loaded, so they are always in English.
image

It would be nice if we could inject different translations of this into different language versions somehow. (Perhaps we could add a language tag in the Markdown header that Auspice could use to use the corresponding translation of instructions?)

I don't think this is urgent, but it would be nice to have for future!

GISAID all-sequences fasta should be directly usable by nextstrain/ncov

Filing this as an issue as suggested by @emmahodcroft:

GISAID provides an all-sequences download button for SARS-CoV-2 sequences. The provided file is not directly usable as a sequences.fasta file in nextstrain/ncov because of several issues in the GISAID file:

  1. There is at least one duplicate sequence name (Italy/INMI1/2020) that causes errors in augur filter, and often other duplicates exist before they are renamed on GISAID
  2. There are several sequences with "Hong Kong" in their names that cause errors in augur filter due to the sequence name being truncated at whitespace
  3. The sequence names are appended with the EPI_ISL identifier and a datestamp, which are not stripped when loaded and cause mismatches with sequence names in metadata.tsv
  4. The sequence names are prepended with 'BetaCoV' or 'BetaCov' which is not stripped when loaded and causes mismatches with metadata.tsv

I suggest a new bash script in ncov/scripts/ that would optionally normalize the GISAID all-sequences download file so that users can use it directly without a need to manually remove duplicates or edit sequence names or maintain their own automated pipeline to generate data/sequences.fasta.

I also suggest automating this in the Snakefile if possible, but I'm not sure how. If no data/sequences.fasta file exists, but data/gisaid_cov2020_sequences.fasta exists, run scripts/normalize-gisaid-fasta.sh before the rest of the pipeline.

I can likely have a base script written to do the normalization by this evening if there is interest.

Thank you for considering this idea.

Translate situation report into Arabic

Hello @SalehA74 -- I made a branch sit-rep_ar where you can start translating the report into Arabic. We can see how it looks, and you can see if it translates okay with the narratives format. The file to translate is ncov_sit-rep_ar_2020-03-05.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_ar/narratives/ncov_sit-rep_ar_2020-03-05.md

You can translate directly in this file, and you should have access to push to the sit-rep_ar.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.)

Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing your translation, you can preview it here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ar/sit-rep/ar/2020-03-05

Let me know if you've got any questions. Thank you so much for your help! It would be really exciting if this works.

Translate Situation Report to Japanese

The narrative from 2020-03-05 should be translated to Japanese. A branch exists as sit-rep_ja where this can be done, and the file to translate is ncov_sit-rep_ja_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_ja/narratives/ncov_sit-rep_ja_2020-03-05.md

Note this file is in Markdown - it's important not to change any links! (Links to other-language versions of articles on Wikipedia are ok.)

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ja/sit-rep/ja/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Please also write your twitter handle and/or full name if you'd like to be attributed when we announce!

Translate situation report to Portuguese

The narrative from 2020-03-05 should be translated to Portuguese. A branch exists as sit-rep_pt where this can be done, and the file to translate is ncov_sit-rep_pt_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_pt/narratives/ncov_sit-rep_pt_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_pt/sit-rep/pt/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Translate March13 sit-rep to Farsi

Happy weekend @dahaj1897, @mg878!

The situation report from March 13 is ready to be translated to Farsi. A branch exists as sit-rep_fa where this can be done, and the file to translate is ncov_sit-rep_fa_2020-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_fa/narratives/ncov_sit-rep_fa_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation! You should have access to push to the sit-rep_fa, so there’s no need to create a pull request. Please make sure you’ve accepted an invitation from me to join the ncov repo.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.)

Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_fa/sit-rep/fa/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your Farsi-speaking colleagues, so we can get the information out there!

Note: You may know of other great resources available in Farsi; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Because Nextstrain team members only speak so many languages, this is our best system for doing so. Thanks for understanding.

Thank you so very much for your hard work; you all are amazing!

Translate Situtation Report to Hindi

The narrative from 2020-03-05 should be translated to Hindi. A branch exists as sit-rep_hi where this can be done, and the file to translate is ncov_sit-rep_hi_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_hi/narratives/ncov_sit-rep_hi_2020-03-05.md

Note this file is in Markdown - it's important not to change any links! (Links to other-language versions of articles on Wikipedia are ok.)

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_hi/sit-rep/hi/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Please also write your twitter handle and/or full name if you'd like to be attributed when we announce!

Translate situation report to German

The narrative from 2020-03-05 should be translated to German. A branch exists as sit-rep_de where this can be done, and the file to translate is ncov_sit-rep_de_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_de/narratives/ncov_sit-rep_de_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_de/sit-rep/de/2020-03-05

Please remember to push often as multiple people may be working on this translation!

augur: error: unrecognized arguments: --weights config/weights.tsv when build with augur6.3.0

After installing augur 6.3.0 via pip, when build again with command nextstrain build .
job 12 failed:
Job 12:
Inferring ancestral traits for division
- increase uncertainty of reconstruction by 2 to partially account for sampling bias
augur traits --tree results/tree.nwk --metadata data/metadata.tsv --weights config/weights.tsv --output results/traits.json --columns division --confidence --sampling-bias-correction 2
usage: augur [-h]
{parse,filter,mask,align,tree,refine,ancestral,translate,reconstruct-sequences,clades,traits,sequence-traits,lbi,distance,titers,frequencies,export,validate,version,import}
...
augur: error: unrecognized arguments: --weights config/weights.tsv

I did not encounter this issue with augur 6.2.0. After checking augur traits -h, seems --weights is a valid argument. Could you please help with this issue? Thanks.

Translate March 13 sit-rep to Italian

Happy weekend @al-epo, @enkelejdamiho, @whispererindarkness, @aliceLedda!

The situation report from March 13 is ready to be translated to Italian. A branch exists as sit-rep_it where this can be done, and the file to translate is ncov_sit-rep_it_2020-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_it/narratives/ncov_sit-rep_it_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation! You should have access to push to the sit-rep_it, so there’s no need to create a pull request. Please make sure you’ve accepted an invitation from me to join the ncov repo.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.) Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_it/sit-rep/it/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your Italian-speaking colleagues, so we can get the information out there!

Note: You may know of other great resources available in Italian; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Because Nextstrain team members only speak so many languages, this is our best system for doing so. Thanks for understanding.

Please coordinate amongst yourselves on how to best complete the translations. You can trade off weeks; you can use an online editor like hackmd to translate together, whatever works best for you. But when finished, please push it to GitHub for proofreading and review.

@aliceLedda, since you have a background in the field, I won’t send it live without a review from you. This is to ensure we provide accurate information.

Thank you so very much for your hard work; you all are amazing!

Translate situation report to Italian

The narrative from 2020-03-05 should be translated to Italian. A branch exists as sit-rep_it where this can be done, and the file to translate is ncov_sit-rep_it_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_it/narratives/ncov_sit-rep_it_2020-03-05.md

Note this file is in Markdown - it's important to to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_it/sit-rep/it/2020-03-05

Please remember to push often as multiple people may be working on this translation!

DIVERGENCE different with yours

Sorry to bother you.
These days I am using nextstrain to analysis the data I have.
But after I download sequences from gisaid. And I checked the sequences I download with sequences you used in you network, it is the same.
However I discovered that the DIVERGENCE in my result is different with yours in nextstrain.org/ncov.
But interestingly, I checked some of samples, mutations in my result just matched in yours.
So It should't be error in my sequence.
For example, the DIVERGENCE of "Wuhan/WIV04/2019" in my result is 0.996, but the mutation is none(which is impossible) . And I tried it for many times, finally I found my result is unstable even I did not change data-set and config.
So, I'm sorry again to bother you. I just wonder whether you had the same issue before.

Translate March 13 sit-rep into German

Happy weekend @astridgall, @rneher, @nicfel !

The situation report from March 13 is ready to be translated to German. A branch exists as sit-rep_de where this can be done, and the file to translate is ncov_sit-rep_de_20202-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_de/narratives/ncov_sit-rep_de_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation!

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.) Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_de/sit-rep/de/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your German-speaking colleagues, so we can get the information out there!

Thank you so very much for your hard work; you all are amazing!

Russian Translation of 30 Jan Situation Report

Thanks to @ivan-aksamentov, we have a Russian translation! I will push live tomorrow if we are ready. Ivan, if you hadn't seen it yet, here's the preview link, so you can check it out: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ru/sit-rep/ru/2020-01-30

A couple of the markdown links are broken (space between the ] and ( in [link text](link) ). I can fix this very easily tomorrow if needed - don't worry about it!

I think Vadim may proofread before push - will tag him here when added! @vpuller

Translate Situation Report to Dutch

The narrative from 2020-03-05 should be translated to Dutch. A branch exists as sit-rep_nl where this can be done, and the file to translate is ncov_sit-rep_nl_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_nl/narratives/ncov_sit-rep_nl_2020-03-05.md

Note this file is in Markdown - it's important not to change any links! (Links to other-language versions of articles on Wikipedia are ok.)

Comments to help with translation are noted in comment symbols like

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_nl/sit-rep/nl/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Please also write your twitter handle and/or full name if you'd like to be attributed when we announce!

Update Portuguese Translation

This is an issue for updating the Portuguese version of the Situation Report to match the 30 Jan 2020 English version, when possible! Tagging @7glaucio @andersonbrito

I have already created a branch sit-rep_pt with the new file to be translated: ncov_sit-rep_pt_2020-01-30.md

To make it easier to see what's changed, I've created a 'fake' diff file which shows the changes only in the text. You still must use the latest ncov_sit-rep_(lang)_2020-01-30.md file as your basis, because the code parts of the file have changed!

You can view the text differences here.

Note there are two entirely new slides - these I've put in the diff file with code so that you can spot them more easily. You see them in the newer version from line 207.

Sequence numbers now sometimes followed by </tag> - you do not have to this if you don't want - it was just to make it easier for us - in the time it took to update the narrative the number of sequences kept changing so this makes it easier to search and replace!

There may be multiple people working on this translation. so I recommend committing and pushing often to help avoid the work being done twice! Thank you all for your efforts!

Spanish Translation

We are super-pleased to have @Chjulian working with us on a Spanish translation of narratives! I am simply making this issue so that there's a place where everyone can discuss, contribute, etc to the Spanish narratives!

Need translators for weekly situation reports

Greetings all -- we’re working hard to start publishing weekly situation reports on hCov-19; we’d like to get these weekly reports translated too.

I’ve been really impressed and appreciative of all your efforts to get the last situation report out so quickly. Is anyone available to commit to translating reports on a weekly basis?

We plan to publish situation reports in English every Friday at 5 pm PST / Saturday 1am CET. So we need people who can commit to translating them over the weekend. Ideally, all reports are translated by Monday, if not sooner.

To ensure we’re sharing quality and accurate information, we’d like to have at least two people translating/proofreading each translation. One of these people should have a background in phylogenetics. However, we can definitely have more than two people volunteer for each language because not everyone may be available every week.

If you can commit to translating weekly situation reports, please comment below with the name you’d like to use to receive credit, your Twitter handle (so we can tag you upon sharing), and the language(s) you will be translating to.

THANK YOU SO MUCH everyone. It’s incredible to be part of such a worldwide effort to share accurate information on hCov-19. I feel honored to work with you all.

@hmkim, @ivan-aksamentov, @KanikaNahata, @ronakb128, @roanvanscheppingen, @JiscaH, @satotake, @fzhang12, @rneher, @nicfel, @tolot27, @Simon-LoriereLab, @PierreBarrat, @meriemelkaroui, @Maijin, @andersonbrito, @7glaucio, @Chjulian, @miparedes, @fillorkill, @fzhang12, @alvinxhan, @wdingx, @whispererindarkness, @aliceLedda

Translate situation report to Russian

The narrative from 2020-03-05 should be translated to Russian. A branch exists as sit-rep_ru where this can be done, and the file to translate is ncov_sit-rep_ru_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_ru/narratives/ncov_sit-rep_ru_2020-03-05.md

Note this file is in Markdown - it's important not to change any links!

Comments to help with translation are noted in comment symbols like <!-- Comment -->

You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ru/sit-rep/ru/2020-03-05

Please remember to push often as multiple people may be working on this translation!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.