Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues raised by CCDP Review #51

Open
13 tasks
SarahG-579462 opened this issue May 28, 2024 · 0 comments
Open
13 tasks

Issues raised by CCDP Review #51

SarahG-579462 opened this issue May 28, 2024 · 0 comments

Comments

@SarahG-579462
Copy link
Collaborator

SarahG-579462 commented May 28, 2024

Bugs:

  • The main problem they had was the tool identifying a nearby location as an analogue and it being given the same name as their target city. I’ve attached that feedback with examples. They also mentioned the following points:

  • If we're not recommending the use of 6 scenarios we should maybe disable that option

Interface/Explanations:

  • This is a pretty interesting tool. It is quite technical though, so I did find myself flipping back and forth between the Help page and my search results quite a lot. It was a bit of a pain to have to scroll down the Help page to read about a certain graph for instance, scroll back up to be able to click on my search results tab, scroll down the search results to view the graph in question, forget what I’d read or get confused about something else, scroll back up to get to the Help tab, read again on the Help tab, and so on. If there was the capability to open the Help page in a separate tab in an internet browser that would be very helpful – that way if you have two monitors you could compare side-by-side a lot easier.

  • I think for Analogy quality and Representativeness in particular, it would be great if you could over a little question mark or something and have the definitions for those pop up right there in the search results tab. The Representativeness score for example, didn’t feel intuitive to me as the lower the score, the better. So I think having the definition for this being easily accessible right in the search results tab would be good, if possible.

  • For the graphs, my results only showed a legend under the first graph. A legend under the other two as well feels needed. It took me some time to decipher the Average change and Full timeseries graphs, and a lot of flipping back to the Help page. Also the Help page says that the analogue’s present distribution is represented in yellow in the graphs, but that changes between green, yellow, and blue depending on the quality of the analogue.

  • On the map, I would suggest potentially reordering the legend to have Excellent be listed first, then Good, then Average. I think best to worst feels like a more intuitive order for a legend? (That’s very subjective though).

  • There are also a lot of references to the “ensemble” in the Help tab, but I didn’t see a definition or explanation for this (I’m assuming it’s the same model ensemble used for all of ClimateData.ca but I think that would be good to explicitly say and explain).

  • it would be useful to include a sentence describing the projected indices at the target city compared to the analogue current climate, e.g., end of century projected mean temperature at Vancouver is 12.4°C compared to the analogue (Stamford, Connecticut) current value of 12.3°C.

  • labelling and explanation of the graphs could be improved – particularly the distribution plots

  • there’s no explanation of the dashed line in the average change graph

  • a short statement explaining the blue dashed line on the full timeseries graph would help users understand the matching of the analogue’s current climate to the target city’s future projection

  • it would be useful to have tooltip boxes explaining the quality of the analogue and the representativeness score on the results page

  • Typos:

  • Remove "new" from "Begin a new search"

  • In the French version of the app, the unit temperature is written "degC" while in the English version, it's "°C". In French, unit temperature is written like in English. It would make the text clearer to use the right nomenclature so "°C".

  • In the English version, the "C" of Celsius is in lowercase instead of uppercase

  • In the French version, there is a conjugation error in the text when results are interpreted. In the last sentence of the interpretation, an "e" is missing at "choisis". It should be "Sur les 12 simulations choisies, cette simulation est la meilleure représentation de la moyenne de l'ensemble." (refer to the image)

  • In the French version, a "n" is missing for the word "Coordonnées" (refer to the image).

  • In the French version, an "e" is missing at "Période ciblée"

  • In the French version, delete the "s" at "jour" for this index only: "Maximum du cumul sur 1 jour de la précipitation quotidienne"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant