<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>MyBlog</title>
<link>https://emi030.github.io/</link>
<atom:link href="https://emi030.github.io/index.xml" rel="self" type="application/rss+xml"/>
<description>A blog built with Quarto</description>
<generator>quarto-1.8.27</generator>
<lastBuildDate>Tue, 17 Mar 2026 04:00:00 GMT</lastBuildDate>
<item>
  <title>Patient No-Show Prediction Analysis</title>
  <dc:creator>Emi Rivera</dc:creator>
  <link>https://emi030.github.io/posts/noshow-analysis/</link>
  <description><![CDATA[ 





<section id="overview" class="level2">
<h2 class="anchored" data-anchor-id="overview">Overview</h2>
<p>In this project, I analyzed real appointment data from a primary care clinic to identify what drives patient no-shows and built a machine learning model to predict which appointments are at highest risk. This came from a real problem I see working as a Medical Assistant. No-shows waste provider time and are largely preventable with the right outreach.</p>
</section>
<section id="dataset" class="level2">
<h2 class="anchored" data-anchor-id="dataset">Dataset</h2>
<ul>
<li>52,973 de-identified appointment records (2023–2026)</li>
<li>Source: EHR export from JinCare Wellness Center (raw data not included)</li>
<li>Overall no-show rate: <strong>18.16%</strong></li>
<li>Features include insurance type, appointment type, age, sex, confirmation status, scheduling channel, chronic disease diagnosis, expected copay, and valid email status</li>
</ul>
</section>
<section id="key-findings" class="level2">
<h2 class="anchored" data-anchor-id="key-findings">Key Findings</h2>
<ul>
<li>Confirmed patients had a <strong>2.91% no-show rate</strong> vs <strong>29.63%</strong> for patients with no contact — a 10x difference</li>
<li>Uninsured (cash pay) patients had a <strong>77% no-show rate</strong>, while Medicare patients were the lowest at around 4–5%</li>
<li>Younger patients (mean age 45.4) no-showed more than patients who showed up (mean age 49.1, p &lt; 0.0001)</li>
<li>Staff-scheduled appointments had a <strong>6.8% no-show rate</strong> vs <strong>15.3%</strong> for patient portal appointments</li>
<li>Patients with <strong>no valid email had a 77% no-show rate</strong> vs 8% for patients with a valid email, suggesting patients without email contact are largely unreachable through the reminder system</li>
<li>Patients <strong>with chronic conditions (diabetes, hypertension, obesity, etc.) had near-zero no-show rates</strong>, while patients without any chronic diagnosis had a 23% no-show rate. This makes clinical sense: patients managing ongoing conditions tend to stay engaged with their care</li>
</ul>
</section>
<section id="visualizations" class="level2">
<h2 class="anchored" data-anchor-id="visualizations">Visualizations</h2>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_confirmation.png" class="img-fluid figure-img"></p>
<figcaption>Confirmation Effect</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_insurance.png" class="img-fluid figure-img"></p>
<figcaption>Insurance Type</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_age.png" class="img-fluid figure-img"></p>
<figcaption>Age Distribution</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_channel.png" class="img-fluid figure-img"></p>
<figcaption>Scheduling Channel</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_chronic.png" class="img-fluid figure-img"></p>
<figcaption>Chronic Condition</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_email.png" class="img-fluid figure-img"></p>
<figcaption>Valid Email</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_by_copay.png" class="img-fluid figure-img"></p>
<figcaption>Copay</figcaption>
</figure>
</div>
</section>
<section id="statistical-analysis" class="level2">
<h2 class="anchored" data-anchor-id="statistical-analysis">Statistical Analysis</h2>
<p>All predictors except sex were statistically significant (p &lt; 0.05).</p>
<p><strong>Key findings:</strong></p>
<ul>
<li>Insurance type, appointment type, confirmation status, age, chronic disease, copay, valid email, and scheduling channel all showed strong associations with no-show behavior (p &lt; 0.0001)</li>
<li><strong>Sex was the only non-significant predictor (p = 0.35)</strong>, suggesting no-show behavior is similar between male and female patients</li>
</ul>
</section>
<section id="machine-learning-model" class="level2">
<h2 class="anchored" data-anchor-id="machine-learning-model">Machine Learning Model</h2>
<p>Using patient age, appointment type, confirmation status, insurance type, scheduling channel, chronic disease flag, copay bucket, and valid email as features:</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/noshow-analysis/noshow_feature_importance.png" class="img-fluid figure-img"></p>
<figcaption>Feature Importance</figcaption>
</figure>
</div>
<table class="caption-top table">
<thead>
<tr class="header">
<th>Model</th>
<th>Accuracy</th>
<th>ROC-AUC</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Logistic Regression</td>
<td>59.14%</td>
<td>0.7669</td>
</tr>
<tr class="even">
<td>Random Forest + SMOTE</td>
<td>85.75%</td>
<td>0.8263</td>
</tr>
<tr class="odd">
<td>XGBoost + SMOTE</td>
<td>84.35%</td>
<td>0.8646</td>
</tr>
<tr class="even">
<td><strong>Random Forest (GridSearch tuned)</strong></td>
<td><strong>86.06%</strong></td>
<td><strong>0.8382</strong></td>
</tr>
</tbody>
</table>
<p>SMOTE was used to address class imbalance (82% showed up vs 18% no-show). GridSearch optimized hyperparameters with 5-fold cross-validation. The CV AUC of 0.9617 reflects performance during training, and the test AUC of 0.8382 is the more meaningful number, since it represents performance on held-out data the model had never seen before. The top predictors were patient age, appointment type, and chronic disease status.</p>
</section>
<section id="clinical-application" class="level2">
<h2 class="anchored" data-anchor-id="clinical-application">Clinical Application</h2>
<p>Beyond the analysis, I built two tools for daily clinical use:</p>
<ul>
<li><code>predict_noshow.py</code> — a command-line script that takes the clinic’s EHR schedule, parses each appointment, and outputs a color-coded Excel file with high-risk patients ranked at the top</li>
<li><code>noshow_risk_tool.html</code> — a browser-based version of the same tool, no coding required. Front desk staff can open it, paste the daily schedule, and instantly see which patients to call first</li>
</ul>
<p>The goal is to give the front desk a simple way to prioritize outreach calls each morning without needing any technical knowledge.</p>
</section>
<section id="tools-used" class="level2">
<h2 class="anchored" data-anchor-id="tools-used">Tools Used</h2>
<ul>
<li>Python, pandas, matplotlib, seaborn, scikit-learn, scipy, xgboost, imbalanced-learn</li>
</ul>
<p><a href="https://github.com/emi030/noshow-prediction">View full code on GitHub</a></p>


</section>

 ]]></description>
  <category>Python</category>
  <category>Machine Learning</category>
  <category>Healthcare</category>
  <category>Clinical Data</category>
  <guid>https://emi030.github.io/posts/noshow-analysis/</guid>
  <pubDate>Tue, 17 Mar 2026 04:00:00 GMT</pubDate>
  <media:content url="https://emi030.github.io/posts/noshow-analysis/noshow_by_confirmation.png" medium="image" type="image/png" height="103" width="144"/>
</item>
<item>
  <title>Diabetes Prediction Analysis</title>
  <dc:creator>Emi Rivera</dc:creator>
  <link>https://emi030.github.io/posts/diabetes-analysis/</link>
  <description><![CDATA[ 





<section id="overview" class="level2">
<h2 class="anchored" data-anchor-id="overview">Overview</h2>
<p>In this project, I analyzed the Pima Indians Diabetes Dataset to explore risk factors associated with diabetes and built a machine learning model to predict diabetes outcomes.</p>
</section>
<section id="dataset" class="level2">
<h2 class="anchored" data-anchor-id="dataset">Dataset</h2>
<p>The dataset contains 768 patients with 9 features including glucose levels, BMI, age, and blood pressure.</p>
</section>
<section id="key-findings" class="level2">
<h2 class="anchored" data-anchor-id="key-findings">Key Findings</h2>
<ul>
<li><strong>Glucose</strong> is the strongest predictor of diabetes (correlation: 0.47)</li>
<li>Diabetic patients have significantly higher <strong>BMI</strong> (median ~35 vs ~30)</li>
<li>Diabetic patients tend to be <strong>older</strong> (median age ~36 vs ~27)</li>
</ul>
</section>
<section id="visualizations" class="level2">
<h2 class="anchored" data-anchor-id="visualizations">Visualizations</h2>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/diabetes-analysis/glucose_distribution.png" class="img-fluid figure-img"></p>
<figcaption>Glucose Distribution</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/diabetes-analysis/bmi_age_analysis.png" class="img-fluid figure-img"></p>
<figcaption>BMI and Age Analysis</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/diabetes-analysis/correlation_heatmap.png" class="img-fluid figure-img"></p>
<figcaption>Correlation Heatmap</figcaption>
</figure>
</div>
</section>
<section id="machine-learning-model" class="level2">
<h2 class="anchored" data-anchor-id="machine-learning-model">Machine Learning Model</h2>
<p>Using Logistic Regression with an 80/20 train/test split, the model achieved <strong>74.68% accuracy</strong> in predicting diabetes outcomes.</p>
</section>
<section id="statistical-analysis" class="level2">
<h2 class="anchored" data-anchor-id="statistical-analysis">Statistical Analysis</h2>
<p>To validate the findings, I conducted t-tests comparing diabetic and non-diabetic groups.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/diabetes-analysis/pvalue_plot.png" class="img-fluid figure-img"></p>
<figcaption>Statistical Significance</figcaption>
</figure>
</div>
<p><strong>Key findings:</strong></p>
<ul>
<li>Glucose showed the strongest difference (p &lt; 0.0001) by far the most important predictor</li>
<li>BMI and Age were also highly significant (p &lt; 0.0001)</li>
<li>Insulin was significant (p = 0.0003)</li>
<li><strong>BloodPressure was the only non-significant feature (p = 0.0715)</strong> This is suggesting it may not be a reliable standalone diagnostic indicator</li>
</ul>
</section>
<section id="pca-analysis" class="level2">
<h2 class="anchored" data-anchor-id="pca-analysis">PCA Analysis</h2>
<p>PCA applied to key clinical features reveals partial separation between diabetic and non-diabetic patients.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/diabetes-analysis/pca_plot.png" class="img-fluid figure-img"></p>
<figcaption>PCA of Diabetes Clinical Features</figcaption>
</figure>
</div>
<p>PC1 and PC2 together explain <strong>49.5% of the variance</strong>. Compared to the PCOS dataset, the separation between groups is less distinct, reflecting the more complex and multifactorial nature of diabetes.</p>
</section>
<section id="tools-used" class="level2">
<h2 class="anchored" data-anchor-id="tools-used">Tools Used</h2>
<ul>
<li>Python, pandas, matplotlib, seaborn, scikit-learn</li>
</ul>
<p><a href="https://github.com/emi030/diabetes-project">View full code on GitHub</a></p>


</section>

 ]]></description>
  <category>Python</category>
  <category>Machine Learning</category>
  <category>Healthcare</category>
  <guid>https://emi030.github.io/posts/diabetes-analysis/</guid>
  <pubDate>Tue, 17 Mar 2026 04:00:00 GMT</pubDate>
  <media:content url="https://emi030.github.io/posts/diabetes-analysis/glucose_distribution.png" medium="image" type="image/png" height="108" width="144"/>
</item>
<item>
  <title>PCOS Risk Factor Analysis</title>
  <dc:creator>Emi Rivera</dc:creator>
  <link>https://emi030.github.io/posts/pcos-analysis/</link>
  <description><![CDATA[ 





<section id="overview" class="level2">
<h2 class="anchored" data-anchor-id="overview">Overview</h2>
<p>In this project, I analyzed a clinical PCOS dataset containing 541 patients to identify key risk factors and built a machine learning model to predict PCOS diagnosis with 86% accuracy.</p>
</section>
<section id="dataset" class="level2">
<h2 class="anchored" data-anchor-id="dataset">Dataset</h2>
<ul>
<li>541 patients, 45 features</li>
<li>32.72% of patients diagnosed with PCOS</li>
<li>Features include hormone levels, symptoms, BMI, and ultrasound measurements</li>
</ul>
</section>
<section id="key-findings" class="level2">
<h2 class="anchored" data-anchor-id="key-findings">Key Findings</h2>
<ul>
<li><strong>Weight gain</strong> is 3x more common in PCOS patients (68% vs 23%)</li>
<li><strong>Hair growth and skin darkening</strong> are 4x more prevalent in PCOS patients</li>
<li><strong>AMH levels</strong> are significantly elevated in PCOS patients is a key clinical marker</li>
</ul>
</section>
<section id="visualizations" class="level2">
<h2 class="anchored" data-anchor-id="visualizations">Visualizations</h2>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/pcos-analysis/symptoms_comparison.png" class="img-fluid figure-img"></p>
<figcaption>Symptom Comparison</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/pcos-analysis/hormone_analysis_clean.png" class="img-fluid figure-img"></p>
<figcaption>Hormone Analysis</figcaption>
</figure>
</div>
</section>
<section id="machine-learning-model" class="level2">
<h2 class="anchored" data-anchor-id="machine-learning-model">Machine Learning Model</h2>
<p>Using Logistic Regression with BMI, hormone levels, follicle count, and symptoms as features, the model achieved <strong>86.11% accuracy</strong> in predicting PCOS diagnosis.</p>
</section>
<section id="statistical-analysis" class="level2">
<h2 class="anchored" data-anchor-id="statistical-analysis">Statistical Analysis</h2>
<p>To validate the findings, I conducted t-tests comparing PCOS and non-PCOS groups.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/pcos-analysis/pvalue_plot.png" class="img-fluid figure-img"></p>
<figcaption>Statistical Significance</figcaption>
</figure>
</div>
<p><strong>Key findings:</strong></p>
<ul>
<li>AMH (p = 0.0001), BMI (p = 0.0002), and FSH (p = 0.0105) showed statistically significant differences between groups</li>
<li>All five symptoms were highly significant (p &lt; 0.0001)</li>
<li><strong>Interestingly, LH was the only non-significant marker (p = 0.6230)</strong>, suggesting it may not be a reliable standalone diagnostic indicator and raising questions about whether LH behaves differently across ethnic populations</li>
</ul>
</section>
<section id="pca-analysis" class="level2">
<h2 class="anchored" data-anchor-id="pca-analysis">PCA Analysis</h2>
<p>To explore the underlying structure of the data, I applied Principal Component Analysis (PCA) to key clinical features including BMI, hormone levels, and follicle counts.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/pcos-analysis/pca_plot.png" class="img-fluid figure-img"></p>
<figcaption>PCA of PCOS Clinical Features</figcaption>
</figure>
</div>
<p>PC1 and PC2 together explain <strong>49.1% of the variance</strong>. The plot shows a clear separation between PCOS (red) and non-PCOS (blue) patients along PC1, suggesting that the combination of hormone levels and follicle counts captures meaningful biological differences between the two groups.</p>
</section>
<section id="tools-used" class="level2">
<h2 class="anchored" data-anchor-id="tools-used">Tools Used</h2>
<ul>
<li>Python, pandas, matplotlib, seaborn, scikit-learn</li>
</ul>
<p><a href="https://github.com/emi030/pcos-analysis">View full code on GitHub</a></p>


</section>

 ]]></description>
  <category>Python</category>
  <category>Machine Learning</category>
  <category>Women&#39;s Health</category>
  <guid>https://emi030.github.io/posts/pcos-analysis/</guid>
  <pubDate>Wed, 11 Mar 2026 04:00:00 GMT</pubDate>
  <media:content url="https://emi030.github.io/posts/pcos-analysis/symptoms_comparison.png" medium="image" type="image/png" height="86" width="144"/>
</item>
<item>
  <title>Coding Assignment 2</title>
  <dc:creator>Emi Rivera</dc:creator>
  <link>https://emi030.github.io/posts/assignment 2/</link>
  <description><![CDATA[ 





<section id="overview" class="level2">
<h2 class="anchored" data-anchor-id="overview">Overview</h2>
<p>In this assignment, I analyzed a large NOAA climate dataset containing over 17 million temperature measurements from weather stations around the world. Using R and the tidyverse, I cleaned the data, filtered by country and time period, and visualized global temperature trends over time.</p>
<p><strong>Key tasks:</strong></p>
<ul>
<li>Imported and cleaned NOAA temperature data (17.9M rows)</li>
<li>Filtered data for Japan and Algeria (2000–2025)</li>
<li>Summarized temperature statistics by year and country</li>
<li>Visualized mean, min, and max temperature trends over time</li>
</ul>
</section>
<section id="tools-r-tidyverse-ggplot2" class="level2">
<h2 class="anchored" data-anchor-id="tools-r-tidyverse-ggplot2"><strong>Tools:</strong> R, tidyverse, ggplot2</h2>
</section>
<section id="problem-1-import-the-data" class="level2">
<h2 class="anchored" data-anchor-id="problem-1-import-the-data">Problem 1: Import the data</h2>
<p>First, I loaded the three required CSV files into RStudio. I saved them as <code>temperatures</code>, <code>stations</code>, and <code>countries</code>.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code>Rows: 17,911,764
Columns: 4
$ ID      &lt;chr&gt; "ACW00011604", "ACW00011604", "ACW00011604", "ACW00011604", "A…
$ Year    &lt;dbl&gt; 1961, 1961, 1961, 1961, 1961, 1961, 1961, 1961, 1961, 1961, 19…
$ Month   &lt;dbl&gt; 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 1, 2, 3, 4, 5, 6, 7, 8,…
$ AvgTemp &lt;dbl&gt; -142, 183, 419, 720, 1075, 1546, 1517, 1428, 1360, 1121, 457, …</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code>Rows: 27,585
Columns: 5
$ ID        &lt;chr&gt; "ACW00011604", "AE000041196", "AEM00041184", "AEM00041194", …
$ LATITUDE  &lt;dbl&gt; 57.7667, 25.3330, 25.6170, 25.2550, 24.4300, 24.4330, 24.262…
$ LONGITUDE &lt;dbl&gt; 11.8667, 55.5170, 55.9330, 55.3640, 54.4700, 54.6510, 55.609…
$ STNELEV   &lt;dbl&gt; 18.0, 34.0, 31.0, 10.4, 3.0, 26.8, 264.9, 3366.0, 378.0, 977…
$ NAME      &lt;chr&gt; "SAVE", "SHARJAH_INTER_AIRP", "RAS_AL_KHAIMAH_INTE", "DUBAI_…</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code>Rows: 279
Columns: 2
$ `FIPS 10-4` &lt;chr&gt; "AF", "AX", "AL", "AG", "AQ", "AN", "AO", "AV", "AY", "AC"…
$ Name        &lt;chr&gt; "Afghanistan", "Akrotiri", "Albania", "Algeria", "American…</code></pre>
</div>
</div>
</section>
<section id="problem-2-clean-the-data" class="level2">
<h2 class="anchored" data-anchor-id="problem-2-clean-the-data">Problem 2: Clean the data</h2>
<p>For problem 2, I cleaned the data as required. In the temperature file, I removed those rows that are -9999. AvgTemp is stored as “hundredths of a degree”, so I divided by 100 to get real °C. Also, I created a country code column from the first two letters of the station ID. Then I removed duplicate country codes so each code only shows once.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code>[1] 272</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 0 × 2
# ℹ 2 variables: FIPS 10-4 &lt;chr&gt;, n &lt;int&gt;</code></pre>
</div>
</div>
</section>
<section id="problem-3-set-parameters" class="level2">
<h2 class="anchored" data-anchor-id="problem-3-set-parameters">Problem 3: Set parameters</h2>
<p>For problem 3, I set my own parameters <code>country</code>, <code>year begin</code>, <code>year end</code> and <code>month</code>. This makes it easy to change the query without rewriting the whole code.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 1 × 5
  data_file     country year_begin year_end month
  &lt;chr&gt;         &lt;chr&gt;        &lt;dbl&gt;    &lt;dbl&gt; &lt;dbl&gt;
1 my_output.csv Japan         2000     2025     1</code></pre>
</div>
</div>
</section>
<section id="problem-4-join-filter-japan" class="level2">
<h2 class="anchored" data-anchor-id="problem-4-join-filter-japan">Problem 4: Join + Filter (Japan)</h2>
<p>For Problem 4, I joined the datasets and then filtered the data using my parameters. I selected the required columns, sorted by station <code>NAME</code>, and showed the first 7 and last 7 rows. Finally, I saved the result as a CSV file.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 7 × 7
  NAME     LATITUDE LONGITUDE Country  Year Month AvgTemp
  &lt;chr&gt;       &lt;dbl&gt;     &lt;dbl&gt; &lt;chr&gt;   &lt;dbl&gt; &lt;dbl&gt;   &lt;dbl&gt;
1 ABASHIRI     44.0      144. Japan    2000     1   -4.8 
2 ABASHIRI     44.0      144. Japan    2001     1   -7.57
3 ABASHIRI     44.0      144. Japan    2002     1   -4.4 
4 ABASHIRI     44.0      144. Japan    2003     1   -6.1 
5 ABASHIRI     44.0      144. Japan    2004     1   -4.1 
6 ABASHIRI     44.0      144. Japan    2005     1   -5.68
7 ABASHIRI     44.0      144. Japan    2006     1   -6   </code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 7 × 7
  NAME  LATITUDE LONGITUDE Country  Year Month AvgTemp
  &lt;chr&gt;    &lt;dbl&gt;     &lt;dbl&gt; &lt;chr&gt;   &lt;dbl&gt; &lt;dbl&gt;   &lt;dbl&gt;
1 YORON     27.0      128. Japan    2019     1    17.8
2 YORON     27.0      128. Japan    2020     1    18.2
3 YORON     27.0      128. Japan    2021     1    16.6
4 YORON     27.0      128. Japan    2022     1    17.3
5 YORON     27.0      128. Japan    2023     1    17.2
6 YORON     27.0      128. Japan    2024     1    17.7
7 YORON     27.0      128. Japan    2025     1    16.3</code></pre>
</div>
</div>
</section>
<section id="problem-4-repeat-join-filter-algeria" class="level2">
<h2 class="anchored" data-anchor-id="problem-4-repeat-join-filter-algeria">Problem 4 (Repeat): Join + Filter (Algeria)</h2>
<p>Then I repeated the same steps for Algeria (2000–2025, June) and saved it to a different CSV file.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 7 × 7
  NAME  LATITUDE LONGITUDE Country  Year Month AvgTemp
  &lt;chr&gt;    &lt;dbl&gt;     &lt;dbl&gt; &lt;chr&gt;   &lt;dbl&gt; &lt;dbl&gt;   &lt;dbl&gt;
1 ADRAR     27.9     -0.28 Algeria  2000     6    34.3
2 ADRAR     27.9     -0.28 Algeria  2001     6    35.6
3 ADRAR     27.9     -0.28 Algeria  2003     6    35.3
4 ADRAR     27.9     -0.28 Algeria  2004     6    33.8
5 ADRAR     27.9     -0.28 Algeria  2005     6    34.4
6 ADRAR     27.9     -0.28 Algeria  2006     6    35.1
7 ADRAR     27.9     -0.28 Algeria  2007     6    34.1</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 7 × 7
  NAME   LATITUDE LONGITUDE Country  Year Month AvgTemp
  &lt;chr&gt;     &lt;dbl&gt;     &lt;dbl&gt; &lt;chr&gt;   &lt;dbl&gt; &lt;dbl&gt;   &lt;dbl&gt;
1 ZENATA     35.0     -1.45 Algeria  2019     6    22.1
2 ZENATA     35.0     -1.45 Algeria  2020     6    23.2
3 ZENATA     35.0     -1.45 Algeria  2021     6    23.0
4 ZENATA     35.0     -1.45 Algeria  2022     6    24.6
5 ZENATA     35.0     -1.45 Algeria  2023     6    24.4
6 ZENATA     35.0     -1.45 Algeria  2024     6    22.9
7 ZENATA     35.0     -1.45 Algeria  2025     6    26.7</code></pre>
</div>
</div>
</section>
<section id="problem-5-summaries" class="level2">
<h2 class="anchored" data-anchor-id="problem-5-summaries">Problem 5: Summaries</h2>
<p>For Problem 5, I summarized the joined data. I made three tables: <code>summary_year</code>, <code>coverage_year</code>, and <code>coverage_country</code>. Then I reported the number of measurements in 2025 and the top 5 countries overall.</p>
<div class="cell">
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 1 × 2
   Year n_measurements
  &lt;dbl&gt;          &lt;int&gt;
1  2025         126155</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 5 × 2
  Name          n_measurements
  &lt;chr&gt;                  &lt;int&gt;
1 United States        7810379
2 Canada               1540423
3 Russia                788220
4 Australia             760851
5 Germany               518642</code></pre>
</div>
<div class="cell-output cell-output-stdout">
<pre><code># A tibble: 1 × 2
  min_year max_year
     &lt;dbl&gt;    &lt;dbl&gt;
1     1701     2026</code></pre>
</div>
</div>
</section>
<section id="problem-6-plot" class="level2">
<h2 class="anchored" data-anchor-id="problem-6-plot">Problem 6: Plot</h2>
<p>For Problem 6, I made a line plot using the yearly summary table. It shows the <code>mean</code>, <code>min</code>, and <code>max</code> temperature over time.</p>
<div class="cell">
<div class="cell-output-display">
<div>
<figure class="figure">
<p><img src="https://emi030.github.io/posts/assignment 2/index_files/figure-html/p6-plot-1.png" class="img-fluid figure-img" width="672"></p>
</figure>
</div>
</div>
</div>


</section>

 ]]></description>
  <category>R</category>
  <category>Data Wrangling</category>
  <category>Climate Data</category>
  <guid>https://emi030.github.io/posts/assignment 2/</guid>
  <pubDate>Sun, 01 Mar 2026 05:00:00 GMT</pubDate>
</item>
<item>
  <title>Coding Assignment 1</title>
  <dc:creator>Emi Rivera</dc:creator>
  <link>https://emi030.github.io/posts/assignment1/</link>
  <description><![CDATA[ 





<section id="overview" class="level2">
<h2 class="anchored" data-anchor-id="overview">Overview</h2>
<p>In this first assignment, I learned the basics of Quarto markdown, including text formatting, lists, images, and embedded R code. I used my passion for photography as the topic to practice these skills.</p>
<p><strong>Key tasks:</strong></p>
<ul>
<li>Formatted text using markdown (bold, italic, headers)</li>
<li>Created ordered and unordered lists</li>
<li>Embedded images and links</li>
<li>Wrote and ran basic R code</li>
</ul>
<p><strong>Tools:</strong> R, Quarto</p>
</section>
<section id="my-love-for-photography" class="level1">
<h1>My Love for Photography</h1>
<p>Photography is something I like to do during my free time. I like taking photos of food, people, pets and everyday moments.</p>
<section id="why-i-like-photography" class="level2">
<h2 class="anchored" data-anchor-id="why-i-like-photography">Why I like Photography</h2>
<p>I enjoy <strong>photography</strong> because <em>it lets me</em> be <strong><em>creative and expressive</em></strong>.</p>
</section>
<section id="things-i-like-to-photograph" class="level2">
<h2 class="anchored" data-anchor-id="things-i-like-to-photograph">Things I like to Photograph</h2>
<ul>
<li>Food</li>
<li>Nature and landcapes</li>
<li>People</li>
<li>My dog and cat</li>
</ul>
</section>
<section id="my-cameras" class="level2">
<h2 class="anchored" data-anchor-id="my-cameras">My Cameras</h2>
<ol type="1">
<li>Sony A7 IV</li>
<li>Fujifilm X-M5</li>
<li>Canon EOS R8</li>
<li>Canon Ae-1</li>
</ol>
</section>
<section id="helpful-resource" class="level2">
<h2 class="anchored" data-anchor-id="helpful-resource">Helpful Resource</h2>
<p>I learned how to do this from: <a href="https://quarto.org">Quarto</a></p>
</section>
<section id="a-sample-image" class="level2">
<h2 class="anchored" data-anchor-id="a-sample-image">A Sample Image</h2>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://emi030.github.io/posts/assignment1/cat.jpeg" class="img-fluid figure-img"></p>
<figcaption>Photo of my cat</figcaption>
</figure>
</div>
</section>
<section id="inline-code-example" class="level2">
<h2 class="anchored" data-anchor-id="inline-code-example">Inline Code Example</h2>
<p>We can use <code>mean()</code> to calculate averages.</p>
</section>
<section id="r-code-example" class="level2">
<h2 class="anchored" data-anchor-id="r-code-example">R Code Example</h2>
<p>age &lt;- c(17, 19, 20, 25, 30) mean(age)</p>


</section>
</section>

 ]]></description>
  <category>R</category>
  <category>Quarto</category>
  <category>Photography</category>
  <guid>https://emi030.github.io/posts/assignment1/</guid>
  <pubDate>Tue, 20 Jan 2026 05:00:00 GMT</pubDate>
</item>
</channel>
</rss>
