Burst Detection
About
Chapter 6: Burst Detection covers the case study on Burst Detection of Documents using Two Different Tools. It is divided into two parts: 6A, and 6B. 6A case study uses Sci-2 tool, whereas 6B case study uses R programming language to perform burst detection.
How to Cite
Please cite this compendium as: Lamba, Manika, & Madhusudhan, Margam. (2021). Burst Detection of Documents using Three Different Tools (Version 1.2). https://doi.org/10.5281/zenodo.5203298
Contents
The compendium contains the data, code, and notebook associated with the case studies. It is organized as follows:
- The
6a_dataset.csv
file contains the data for 6A case study.- The
6a_maximum_burst_level.csv
is a supplementary file that is associated with 6A case study. - The
6a_results_barSizes.csv
is a supplementary file that is associated with 6A case study. - The
6a_results_horizontal-line-graph.ps
is a supplementary file that is associated with 6A case study.
- The
- The
6b_dataset.csv
file contains the data for 6B case study. - The
burst_detection.R
file contatins the R code for 6B case study. - The
Case_Study_6B.ipynb
file contatins the Jupyter notebook for 6B case study.
In addition to the provided sample data, you can use dataset from Appendix A, Appendix B, Appendix C, Curated Datasets, or your own dataset to perform burst detection.
How to Download or Install
There are several ways to use the compendium’s contents and reproduce the analysis:
-
Download the compendium as a zip archive from the GitHub repository.
- After unpacking the downloaded zip archive, you can explore the files on your computer.
-
Reproduce the analysis in the cloud without having to install any software. The same Docker container replicating the computational environment used by the authors can be run using BinderHub on mybinder.org:
-
Click RStudio: to launch an interactive RStudio session in your web browser for hands-on practice for 6B case study. In the virtual environment, open the
burst_detection.R
file to run the code. -
Click Jupyter+R: to launch an interactive Jupyter Notebook session in your web browser using R kernel. When you execute code within the notebook, the results appear beneath the code.
^ Limitations of Binder
- The server has limited memory so you cannot load large datasets or run big computations.
- Binder is meant for interactive and ephemeral interactive coding so an instance will die after 10 minutes of inactivity.
- An instance cannot be kept alive for more than 12 hours.
-
Visualize the Results
A storyboard is built to summarize the visualizations for 13 case studies performed in the book. To know more about the case studies, and the methodology used to get the results, read the book.
Licenses
Text and Figures: ©2021 Lamba and Madhusudhan - all rights reserved, unless stated otherwise.
Code, Data: MIT License