Conversation
🆗 Pre-flight checks passed 😃This pull request has been checked and contains no modified workflow files or spoofing. Results of any additional workflows will appear here when they are done. |
Degoot-AM
left a comment
There was a problem hiding this comment.
Thanks @Karim-Mane for the suggestions, which improve the overall readability of this tutorials.
| In the process of analyzing outbreak data, it's essential to ensure that the dataset is clean, curated, standardized, and validated. This will increase the accuracy (i.e. you are analysing what you think you are analysing) and reproducibility (i.e. if someone wants to go back and repeat your analysis steps with your code, you can be confident they will get the same results) of the | ||
| downstream analyses. This episode focuses on cleaning epidemics and outbreaks data using the [{cleanepi}](https://epiverse-trace.github.io/cleanepi/) package. | ||
| To demonstrate the functionalities of this package, we'll apply them on a simulated dataset of Ebola cases. |
There was a problem hiding this comment.
| In the process of analyzing outbreak data, it's essential to ensure that the dataset is clean, curated, standardized, and validated. This will increase the accuracy (i.e. you are analysing what you think you are analysing) and reproducibility (i.e. if someone wants to go back and repeat your analysis steps with your code, you can be confident they will get the same results) of the | |
| downstream analyses. This episode focuses on cleaning epidemics and outbreaks data using the [{cleanepi}](https://epiverse-trace.github.io/cleanepi/) package. | |
| To demonstrate the functionalities of this package, we'll apply them on a simulated dataset of Ebola cases. | |
| In the process of analyzing outbreak data, it's essential to ensure that the dataset is clean, curated, standardized, and validated. This will increase the accuracy (i.e. you are analysing what you think you are analysing) and reproducibility (i.e. if someone wants to go back and repeat your analysis steps with your code, you can be confident they will get the same results) of the downstream analyses. This episode focuses on cleaning epidemics and outbreaks data using the [{cleanepi}](https://epiverse-trace.github.io/cleanepi/) package. | |
| To demonstrate the functionalities of this package, we'll apply them on a simulated dataset of Ebola cases. |
| In the process of analyzing outbreak data, it's essential to ensure that the dataset is clean, curated, standardized, and validated. This will increase the accuracy (i.e. you are analysing what you think you are analysing) and reproducibility (i.e. if someone wants to go back and repeat your analysis steps with your code, you can be confident they will get the same results) of the | ||
| downstream analyses. This episode focuses on cleaning epidemics and outbreaks data using the [{cleanepi}](https://epiverse-trace.github.io/cleanepi/) package. | ||
| To demonstrate the functionalities of this package, we'll apply them on a simulated dataset of Ebola cases. |
| The `::` in R lets you access functions or objects from a specific package without attaching the entire package to the search path. It offers several important | ||
| advantages including the followings: |
There was a problem hiding this comment.
| The `::` in R lets you access functions or objects from a specific package without attaching the entire package to the search path. It offers several important | |
| advantages including the followings: | |
| The `::` in R lets you access functions or objects from a specific package without attaching the entire package to the search path. It offers several important advantages including the followings: |
| You can get the number and location of the duplicated rows that where found. Run `cleanepi::print_report()`, wait for the report to open in your browser, and | ||
| find the "Duplicates" tab. |
There was a problem hiding this comment.
| You can get the number and location of the duplicated rows that where found. Run `cleanepi::print_report()`, wait for the report to open in your browser, and | |
| find the "Duplicates" tab. | |
| You can get the number and location of the duplicated rows that where found. Run `cleanepi::print_report()`, wait for the report to open in your browser, and find the "Duplicates" tab. |
| Each entry in the dataset represents a subject (e.g. a disease case or study participant) and should be distinguishable by a specific ID formatted in a | ||
| particular way. These IDs can contain numbers falling within a specific range, a prefix and/or suffix, and might be written such that they contain a specific number of characters. The `{cleanepi}` package offers the function `check_subject_ids()` designed precisely for this task as shown in the below code chunk. This function checks whether the IDs are unique and meet the required criteria specified by the user. |
There was a problem hiding this comment.
| Each entry in the dataset represents a subject (e.g. a disease case or study participant) and should be distinguishable by a specific ID formatted in a | |
| particular way. These IDs can contain numbers falling within a specific range, a prefix and/or suffix, and might be written such that they contain a specific number of characters. The `{cleanepi}` package offers the function `check_subject_ids()` designed precisely for this task as shown in the below code chunk. This function checks whether the IDs are unique and meet the required criteria specified by the user. | |
| Each entry in the dataset represents a subject (e.g. a disease case or study participant) and should be distinguishable by a specific ID formatted in a particular way. These IDs can contain numbers falling within a specific range, a prefix and/or suffix, and might be written such that they contain a specific number of characters. The `{cleanepi}` package offers the function `check_subject_ids()` designed precisely for this task as shown in the below code chunk. This function checks whether the IDs are unique and meet the required criteria specified by the user. |
episodes/read-cases.Rmd
Outdated
| A real-life connection to an external SQLite database would look like this: | ||
|
|
||
| ```r | ||
| ```{r} |
There was a problem hiding this comment.
| ```{r} | |
| ```{r, eval=FALSE} |
| ```{r} | |
| ```{r} |
There was a problem hiding this comment.
Do not run this code because it not excuetable
|
Hi @Karim-Mane, let me know when this is ready to review. I'll be able to review and assess merging tomorrow, ready for the start of next week's training. I can deal with solving some of the remining gh-action issues |
@avallecam - this is ready for review. |
No description provided.