cleanup main.py and add section ids so that hrefs can work

main.py

@@ -183,7 +183,6 @@ def main():
     )
 
 
-
 dataset_comparison1 = pd.DataFrame(
     {
         "Dataset": [
@@ -459,202 +458,6 @@ table_html_data = styled_table._repr_html_()
 table_div_data = Div(NotStr(table_html_data), style="margin: 40px;")
 
 
-def get_curated_chart():
-    # Dataset
-    data = {
-        "Source": [
-            "ArXiv",
-            "PubMed Central",
-            "PubMed Abstract",
-            "S2ORC Full Text",
-            "S2ORC Abstract",
-            "PhilPapers",
-            "Wikipedia",
-            "StackExchange",
-            "EuroParl",
-            "Ubuntu IRC",
-            "Freelaw",
-            "PG19",
-            "USPTO",
-            "HackerNews",
-            "DM Maths",
-        ],
-        "Category": [
-            "Papers",
-            "Papers",
-            "Papers",
-            "Papers",
-            "Papers",
-            "Papers",
-            "Internet",
-            "Conversational",
-            "Legal/Formal",
-            "Conversational",
-            "Legal/Formal",
-            "Books",
-            "Legal/Formal",
-            "Conversational",
-            "Reasoning",
-        ],
-        "Count": [
-            100,
-            200,
-            150,
-            120,
-            80,
-            90,
-            300,
-            250,
-            180,
-            150,
-            150,
-            250,
-            180,
-            120,
-            90,
-        ],
-        "Details": [
-            "A repository of scientific papers in various disciplines, including computer science, physics, mathematics, and more.",
-            "A database of biomedical and life sciences research articles.",
-            "Abstracts of biomedical literature from various sources.",
-            "Full-text articles from the Semantic Scholar Open Research Corpus.",
-            "Abstracts of articles from the Semantic Scholar Open Research Corpus.",
-            "Papers from the PhilPapers database, a comprehensive index and bibliography of philosophy research.",
-            "A collaborative online encyclopedia that covers a wide range of topics.",
-            "A network of question-and-answer websites on various subjects, including programming, science, mathematics, and more.",
-            "A collection of multilingual parallel corpora of parliamentary debates from the European Parliament.",
-            "Chat logs from the Ubuntu Internet Relay Chat (IRC) channels.",
-            "Legal documents and court cases from various jurisdictions.",
-            "A collection of books from Project Gutenberg, a digital library of public domain works.",
-            "Patent documents from the United States Patent and Trademark Office.",
-            "User-generated news and discussion platform focused on technology and startups.",
-            "Deep Mind Maths dataset with generated questions.",
-        ],
-    }
-    # Calculate percentage for each data source
-    total_count = sum(data["Count"])
-    data["Percentage"] = [count / total_count * 100 for count in data["Count"]]
-
-    # Create treemap
-    fig = px.treemap(
-        data,
-        path=["Category", "Source"],
-        values="Count",
-        hover_data=["Details", "Percentage"],
-        hover_name="Source",
-    )
-
-    # Set the size of the chart
-    fig.update_layout(width=800, height=600)
-
-    # Display treemap
-    st.plotly_chart(fig)
-
-
-overview_div = Div(
-    Section(
-        H2("Overview"),
-        H3("What This Section Contains"),
-        Ul(
-            Li("Motivation Behind TxT360", style="margin-bottom: 5px"),
-            Li("The Highlevel Data Process Approach", style="margin-bottom: 5px"),
-            Li("Introduction to Global Deduplication", style="margin-bottom: 5px"),
-        ),
-        H2("Motivation Behind Txt360"),
-        H3(
-            "TxT360 is the first dataset to combine both web and curated data sources commonly used in pretraining."
-        ),
-        P(
-            "The quality and size of a pre-training dataset play a crucial role in the performance of large language models (LLMs). Data is often referred as low quality if it has not been filtered to review unwanted text. The community has introduced a variety of filtered datasets including purely web-based datasets."
-        ),
-        P(
-            "In pretraining, it is common to combine web data and curated sources (cite). Web data is included to provide a vast quantity of long tail and diverse data, while curated datasets are often information rich and provide the 'deep-dive' domain information. Both datasets play critical for effective LLM pre-training."
-        ),
-        H4("The Gap TxT360 Fills"),
-        P(
-            "Despite advancements in filtering and source material for both data types, each type of dataset has its limitations. RefinedWeb is known for its high quality content but and only about 10% of the entire dataset has been disclosed and the processing scripts have not been released. For datasets that have combined curated sources with web data, the web component is relatively small (NEED TO UPDATE - citation needed)."
-        ),
-        P(
-            "By integrating the extensive reach of web data with the exceptional quality of curated sources, TxT360 meets and surpasess the rigorous standards required for state-of-the-art LLM pre-training as demostated in the Results section."
-        ),
-        P(
-            "Table 1: The following table shows TxT360 and other well-known datasets on the coverage and size of data sources."
-        ),
-        table_div_1,
-        table_div_2,
-        P("Table 2: Basic TxT360 Statistics."),
-        table_div_data,
-    ),
-    Section(
-        H2("Our Generalizable Approach to Data Processing"),
-        P(
-            "To produce TxT360, a comprehensive and transparent data processing pipeline was designed to account for the nuances of both web and curated datasets. The pipeline presents a unified framework for processing both data types, making it convenient and easily adaptive for users to revise and fine-tune the pipeline for their own use cases."
-        ),
-        P(
-            "Web datasets are inherently noisy and varied. Thus, the pipeline includes sophisticated filtering and deduplication techniques to clean the data and remove redundancies or irrelevant information."
-        ),
-        P(
-            "Curated datasets are typically already structured and consistently formatted. TxT360 filters these sources with selective steps to maintain their integrity while providing seamless integration into the larger dataset."
-        ),
-        P(
-            "We will open-source the scripts for the whole pipeline, allowing the community to review, replicate, and build upon our processes."
-        ),
-        Img(src="images/pipeline.png", height="300", width="600"),
-        P(
-            "Figure 1: Data processing pipeline. All the steps are adopted for processing web data while the yellow blocks are adopted for processing curated sources."
-        ),
-    ),
-    Section(
-        H2("Introducing Global Deduplication"),
-        P(
-            "Deduplication is crucial in language model pre-training for several reasons (NEEDS CITATION). Main hypothesis on why deduplicaiton is necessary and help include:"
-        ),
-        Ul(
-            Li(
-                "reducing data volume reduces training time (and cost)",
-                style="margin-bottom: 5px",
-            ),
-            Li(
-                "removing duplicataive data can lead to better accuracy",
-                style="margin-bottom: 5px",
-            ),
-            Li("prevent train-test overlap", style="margin-bottom: 5px"),
-            Li(
-                "minimizes the risk of memorization leading to test loss",
-                style="margin-bottom: 5px",
-            ),
-        ),
-        P(
-            "Furthermore, by controlling the pretraining data distribution through deduplication and selective upsampling avoida relying on the often inconsistent distribution of internet-sourced data."
-        ),
-        H3("Highlights of the TxT360 Deduplication Process"),
-        P(
-            "Our deduplication process began with 61.8 TB of filtered, and compressed documents, totaling approximately 48.83 billion documents. We first performed exact deduplication using a Bloom filter, reducing the dataset by 17% to 40.21 billion documents. For global near-deduplication, we scaled methodologies from prior works like SlimPajama to handle the entire dataset, including 87 Common Crawl dumps and other curated data. This involved generating document signatures, matching them to identify near-duplicates, and clustering these to retain only one document per cluster. We prioritized retaining documents from curated sources and more recent CommonCrawl dumps. Throughout the deduplication stages, we extensively used Dask for distributed data processing."
-        ),
-        P(
-            "After the global near-deduplication of all 87 CommonCrawl dumps and other curated data, we removed around 85% of the total documents. This leaves us with approximately 4.24 trillion deduplicated tokens, which aligns with what FineWeb has reported for their iterative global deduplication. Along with the list of duplicated documents to delete, our deduplication code also saves some metadata about the duplicate clusters that we find. We save statistics about every duplicate cluster we find, with the document ID of the document we retain from the cluster as the key and with a value capturing the distribution of the duplicates within the cluster over the CommonCrawl dumps (identified by the first 2 digits of every document ID). This way, we always have information about the duplicates we have deleted, allowing us to upsample any data distribution we want for training."
-        ),
-        P(
-            "During deduplication, it is not feasible to store all the duplicate clusters we form, but we do save some samples at every size. Here are some observations we made by examining these sample duplicate clusters:"
-        ),
-        Ul(
-            Li(
-                "Smaller components tend to have more overlap in their MinHash bands. The smallest components, which are essentially pairs, consist of exact duplicate documents that local exact deduplication missed."
-            ),
-            Li(
-                "When clusters contain three or more documents, incremental changes in the text become apparent. For example, there may be a growing list of personnel over the years."
-            ),
-            Li(
-                "In sizable clusters comprising 1,000 or more documents, we observe a trend towards templatization. This involves the recurrent use of standardized language to convey general topics such as terms and conditions, warnings, and disclaimers. Such language is prevalent on commercial websites, offering a consistent and efficient way to communicate commonly encountered information."
-            ),
-        ),
-        P(
-            "All Deduplication details can be found in the Global Data Processing Steps section."
-        ),
-    ),
-)
-
-
 @app.get("/intro")
 def intro():
     return Div(
@@ -674,16 +477,108 @@ def intro():
             ),
             id="section1",
         ),
-        overview_div,
+        Section(
+            H2("Motivation Behind Txt360"),
+            H3(
+                "TxT360 is the first dataset to combine both web and curated data sources commonly used in pretraining."
+            ),
+            P(
+                "The quality and size of a pre-training dataset play a crucial role in the performance of large language models (LLMs). Data is often referred as low quality if it has not been filtered to review unwanted text. The community has introduced a variety of filtered datasets including purely web-based datasets."
+            ),
+            P(
+                "In pretraining, it is common to combine web data and curated sources (cite). Web data is included to provide a vast quantity of long tail and diverse data, while curated datasets are often information rich and provide the 'deep-dive' domain information. Both datasets play critical for effective LLM pre-training."
+            ),
+            H4("The Gap TxT360 Fills"),
+            P(
+                "Despite advancements in filtering and source material for both data types, each type of dataset has its limitations. RefinedWeb is known for its high quality content but and only about 10% of the entire dataset has been disclosed and the processing scripts have not been released. For datasets that have combined curated sources with web data, the web component is relatively small (NEED TO UPDATE - citation needed)."
+            ),
+            P(
+                "By integrating the extensive reach of web data with the exceptional quality of curated sources, TxT360 meets and surpasess the rigorous standards required for state-of-the-art LLM pre-training as demostated in the Results section."
+            ),
+            P(
+                "Table 1: The following table shows TxT360 and other well-known datasets on the coverage and size of data sources."
+            ),
+            table_div_1,
+            table_div_2,
+            P("Table 2: Basic TxT360 Statistics."),
+            table_div_data,
+            id="section2",
+        ),
+        Section(
+            H2("Our Generalizable Approach to Data Processing"),
+            P(
+                "To produce TxT360, a comprehensive and transparent data processing pipeline was designed to account for the nuances of both web and curated datasets. The pipeline presents a unified framework for processing both data types, making it convenient and easily adaptive for users to revise and fine-tune the pipeline for their own use cases."
+            ),
+            P(
+                "Web datasets are inherently noisy and varied. Thus, the pipeline includes sophisticated filtering and deduplication techniques to clean the data and remove redundancies or irrelevant information."
+            ),
+            P(
+                "Curated datasets are typically already structured and consistently formatted. TxT360 filters these sources with selective steps to maintain their integrity while providing seamless integration into the larger dataset."
+            ),
+            P(
+                "We will open-source the scripts for the whole pipeline, allowing the community to review, replicate, and build upon our processes."
+            ),
+            Img(src="images/pipeline.png", height="300", width="600"),
+            P(
+                "Figure 1: Data processing pipeline. All the steps are adopted for processing web data while the yellow blocks are adopted for processing curated sources."
+            ),
+            id="section3",
+        ),
+        Section(
+            H2("Introducing Global Deduplication"),
+            P(
+                "Deduplication is crucial in language model pre-training for several reasons (NEEDS CITATION). Main hypothesis on why deduplicaiton is necessary and help include:"
+            ),
+            Ul(
+                Li(
+                    "reducing data volume reduces training time (and cost)",
+                    style="margin-bottom: 5px",
+                ),
+                Li(
+                    "removing duplicataive data can lead to better accuracy",
+                    style="margin-bottom: 5px",
+                ),
+                Li("prevent train-test overlap", style="margin-bottom: 5px"),
+                Li(
+                    "minimizes the risk of memorization leading to test loss",
+                    style="margin-bottom: 5px",
+                ),
+            ),
+            P(
+                "Furthermore, by controlling the pretraining data distribution through deduplication and selective upsampling avoida relying on the often inconsistent distribution of internet-sourced data."
+            ),
+            H3("Highlights of the TxT360 Deduplication Process"),
+            P(
+                "Our deduplication process began with 61.8 TB of filtered, and compressed documents, totaling approximately 48.83 billion documents. We first performed exact deduplication using a Bloom filter, reducing the dataset by 17% to 40.21 billion documents. For global near-deduplication, we scaled methodologies from prior works like SlimPajama to handle the entire dataset, including 87 Common Crawl dumps and other curated data. This involved generating document signatures, matching them to identify near-duplicates, and clustering these to retain only one document per cluster. We prioritized retaining documents from curated sources and more recent CommonCrawl dumps. Throughout the deduplication stages, we extensively used Dask for distributed data processing."
+            ),
+            P(
+                "After the global near-deduplication of all 87 CommonCrawl dumps and other curated data, we removed around 85% of the total documents. This leaves us with approximately 4.24 trillion deduplicated tokens, which aligns with what FineWeb has reported for their iterative global deduplication. Along with the list of duplicated documents to delete, our deduplication code also saves some metadata about the duplicate clusters that we find. We save statistics about every duplicate cluster we find, with the document ID of the document we retain from the cluster as the key and with a value capturing the distribution of the duplicates within the cluster over the CommonCrawl dumps (identified by the first 2 digits of every document ID). This way, we always have information about the duplicates we have deleted, allowing us to upsample any data distribution we want for training."
+            ),
+            P(
+                "During deduplication, it is not feasible to store all the duplicate clusters we form, but we do save some samples at every size. Here are some observations we made by examining these sample duplicate clusters:"
+            ),
+            Ul(
+                Li(
+                    "Smaller components tend to have more overlap in their MinHash bands. The smallest components, which are essentially pairs, consist of exact duplicate documents that local exact deduplication missed."
+                ),
+                Li(
+                    "When clusters contain three or more documents, incremental changes in the text become apparent. For example, there may be a growing list of personnel over the years."
+                ),
+                Li(
+                    "In sizable clusters comprising 1,000 or more documents, we observe a trend towards templatization. This involves the recurrent use of standardized language to convey general topics such as terms and conditions, warnings, and disclaimers. Such language is prevalent on commercial websites, offering a consistent and efficient way to communicate commonly encountered information."
+                ),
+            ),
+            P(
+                "All Deduplication details can be found in the Global Data Processing Steps section."
+            ),
+            id="section4",
+        ),
         id="inner-text",
     )
 
 
-# rt("/overview")(overview.overview)
-
 rt("/update/{target}")(data_viewer.update)
 
-
 rt("/curated")(curated.curated)
 
 rt("/webdata")(web.web_data)