Skip to content

Commit

Permalink
removed extra files and check if images are clickable
Browse files Browse the repository at this point in the history
  • Loading branch information
Ananya-Joshi committed Aug 10, 2024
1 parent ff56756 commit b10e8f2
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 10 deletions.
4 changes: 2 additions & 2 deletions content/blog/2024-01-01-flash-intro.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,11 @@ We care about finding data issues like these so that we can alert downstream dat
## Visualization and User Experience
*Perspectives from our expert data reviewer, who has been working with this system for over a year -- Tina Townes.*

<center><div class="float">![**Fig 2a.** Revised FlaSH Dashoard](/blog/2024-01-01-flash-intro/new_dash.png)</div></center>
<center><div class="float">[![**Fig 2a.** Revised FlaSH Dashoard](/blog/2024-01-01-flash-intro/new_dash.png)](/blog/2024-01-01-flash-intro/new_dash.png)</div></center>

<p>In its initial stages, the FlaSH dashboard (Fig 2b) only enabled me to assess potential anomalies by viewing graphs, line-by-line for each location of the numerous signals that have flagged anomalies, as generated by the FlaSH program. This was a particularly daunting task as daily FlaSH outputs generated and continue to produce a large number of reports in the form of compressed lines that required clicking on to expand and reveal more details. Without the new dashboard's features, I was spending a significant amount of time scrolling through the daily list of anomaly reports and manually sorting what I wanted to review by clicking on and expanding only certain report lines and leaving them expanded until I was done with my selection process and ready to review the expanded lines. I would also often make notes and document interesting patterns in anomalies in a separate notepad, decreasing the efficiency and speed of my review process. My attention became divided as I was parsing though the daily anomaly list to search for reports in certain geographies (I knew I wanted to examine these due to prior report patterns), while simultaneously trying to focus on assessing new anomalies.</p>

<center><div class="float">![**Fig 2b.** Prior FlaSH Dashoard](/blog/2024-01-01-flash-intro/old_dash.png)</div></center>
<center><div class="float">[![**Fig 2b.** Prior FlaSH Dashoard](/blog/2024-01-01-flash-intro/old_dash.png)](/blog/2024-01-01-flash-intro/old_dash.png)</div></center>


<p>With the old dashboard setup, it was not easy for me to review the lines of daily anomaly reports because I couldn't efficiently filter various incoming anomalies when I needed to examine specific geographic areas or signals. For example, one particular week I was seeing a lot of anomaly reports in a county in Puerto Rico Monday through Wednesday. By Thursday of that week I wanted to, upon logging into the platform, immediately proceed to filter the daily anomaly reports to look specifically at that Puerto Rican county right away, but had no way of filtering by geography with the old dashboard. The updated dashboard now has a menu that lets me efficiently select to filter lines not only by the geographic regions, but also by various indicators as well. This new setup speeds up my daily review process as it lets me quickly focus on specific geographies and finish reviewing those so that I can move on and focus on examining other anomaly reports in different geographies.
Expand Down
10 changes: 2 additions & 8 deletions content/blog/2024-01-01-flash-intro.html
Original file line number Diff line number Diff line change
Expand Up @@ -44,21 +44,15 @@ <h2>Visualization and User Experience</h2>
<p><em>Perspectives from our expert data reviewer, who has been working with this system for over a year – Tina Townes.</em></p>
<center>
<div class="float">
<div class="float">
<img src="/blog/2024-01-01-flash-intro/new_dash.png" alt="Fig 2a. Revised FlaSH Dashoard" />
<div class="figcaption"><strong>Fig 2a.</strong> Revised FlaSH Dashoard</div>
</div>
<a href="/blog/2024-01-01-flash-intro/new_dash.png"><img src="/blog/2024-01-01-flash-intro/new_dash.png" alt="Fig 2a. Revised FlaSH Dashoard" /></a>
</div>
</center>
<p>
In its initial stages, the FlaSH dashboard (Fig 2b) only enabled me to assess potential anomalies by viewing graphs, line-by-line for each location of the numerous signals that have flagged anomalies, as generated by the FlaSH program. This was a particularly daunting task as daily FlaSH outputs generated and continue to produce a large number of reports in the form of compressed lines that required clicking on to expand and reveal more details. Without the new dashboard’s features, I was spending a significant amount of time scrolling through the daily list of anomaly reports and manually sorting what I wanted to review by clicking on and expanding only certain report lines and leaving them expanded until I was done with my selection process and ready to review the expanded lines. I would also often make notes and document interesting patterns in anomalies in a separate notepad, decreasing the efficiency and speed of my review process. My attention became divided as I was parsing though the daily anomaly list to search for reports in certain geographies (I knew I wanted to examine these due to prior report patterns), while simultaneously trying to focus on assessing new anomalies.
</p>
<center>
<div class="float">
<div class="float">
<img src="/blog/2024-01-01-flash-intro/old_dash.png" alt="Fig 2b. Prior FlaSH Dashoard" />
<div class="figcaption"><strong>Fig 2b.</strong> Prior FlaSH Dashoard</div>
</div>
<a href="/blog/2024-01-01-flash-intro/old_dash.png"><img src="/blog/2024-01-01-flash-intro/old_dash.png" alt="Fig 2b. Prior FlaSH Dashoard" /></a>
</div>
</center>
<p>
Expand Down
Binary file removed content/blog/images/blog-lg-flash-expert.png
Binary file not shown.
Binary file removed content/blog/images/blog-thumb-flash-expert.png
Binary file not shown.

0 comments on commit b10e8f2

Please sign in to comment.