Adding Tinas Blog #969
Adding Tinas Blog #969
Conversation
Ananya-Joshi
requested review from
rlunde,
melange396 and
carlynvandyke
as code owners
✅ Deploy Preview for cmu-delphi-main ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
This looks good but i find it kinda confusing.... It talks about this abstract/esoteric dashboard interface, and its mostly meaningless to a reader who lacks context for the app. Do you want to add some screenshots (preferably before and after) to make things more concrete for people who havent seen FlaSH in action?
|
That sounds great, I'll add them in! |
|
@melange396 Let me know if you think there should be any more changes! |
There was a problem hiding this comment.
This is a lot better with the sample images, but i still think it would benefit from more descriptions and/or example images. You could maybe even do some short .gif clips of the different interfaces while they are in use (though this could be too distracting/noisy).
You mention that fig 1a comes from a paper... Can we provide a link to that?
Can we make it so that clicking the images zooms them? The source image is a much larger size / higher res (and thus more detailed) than whats shown in the post, so that should be available to us... I'm just not sure how to do it without looking up markdown/hugo documentation.
Its natural that we talk about the "old" flash before the "new", but then incongruent/awkward that we show the picture of the "new" flash before the "old"... At the same time, it makes sense to want the "shininess" of the "new" flash at the top of the page, so i'm not sure what to do here.
| </center> | ||
|
|
||
|
|
||
| In its initial stages, the FlaSH dashboard (Fig 1b) only enabled me to assess potential anomalies by viewing graphs, line-by-line, as generated by the FlaSH program. There wasn’t an efficient way to filter various incoming anomalies when I needed to examine specific geographic areas or signals. Nor was there an easy way to see a daily overview map of the aggregated average FlaSH scores for nationwide anomalies. Without the current dashboard, I was spending a good amount of time scrolling, manually sorting, documenting, and searching for specific anomaly reports I wanted to examine rather than focusing solely on identifying, marking, and analyzing anomalies. |
There was a problem hiding this comment.
w.r.t. "graphs, line-by-line": might wanna expand on this and mention that there is a "line" for each location of each signal that has a flagged anomaly, and that there are a relatively large number of these to go through. More example images or scenarios might help.
w.r.t. "manually sorting": what does this interaction look like and what makes it so undesirable?
There was a problem hiding this comment.
I've forwarded this link to Tina and will let her cover content questions!
There was a problem hiding this comment.
Hi, sorry for the delay! Thanks so much for the suggestions, here are my edits. Please let me know if more clarification is needed:
In its initial stages, the FlaSH dashboard (Fig 1b) 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.
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 side 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.
Furthermore, with the former FlaSH dashboard setup, I didn't have an easy way to get a quick bigger picture of geography of the day's flagged anomalies. The old dashboard didn't provide an overview map of the aggregated average FlaSH scores for nationwide anomalies, I would log into the platform and just see a list of daily reported anomalies. Here, only after I assessed a significant number of reported anomalies would I develop a sense of the geographies where significant anomalies were occurring. The updated platform now immediately upon logging in displays a heat map that provides me with an overview of the locations and severities of the day's anomaly reports. This overview map is color-coded to highlight the geographies with the day's with highest aggregated FlaSH scores indicated in dark red on a sliding scale ending with the lowest scores in light red. This new map also speeds up my daily review process by giving me a heads-up on geographies I may want to focus on for the day before I even begin assessing the first anomaly report.
I have this demo video: https://www.youtube.com/watch?v=fWe6M-rTQQ0&list=PLSevl77QCZMa8T1CnConQHk3Xbc6kbNac&index=4
Unfortunately, the paper (and the demo above) aren't published yet so I'm not sure how to go about this.
I'm also not entirely sure, but I can potentially split it into several different images. What do you think about that?
It's definitely a conundrum. Still, our intention is to have a separate visualization deep dive post once the paper gets accepted. We just wanted to make Tina's experiences reviewing data for our stakeholders public. |
|
@melange396 Just wanted to send this update your way! Let me know what you think! |
There was a problem hiding this comment.
Looks good to me, except for the 2 extraneous files!
You might want to see if you can make the FlaSH app screenshots clickable/zoomable (i had a suggestion for that at #969 (review) ), but thats up to you.
Here is Tina's Blog for her experience with the new dashboard.