Closed frksteenhoff closed 4 years ago
Settings related to Children and elderly: current thermal indices and models (WBGT, PHS, PMV and IREQ) are not designed for Children and the elderly. But the models can be adjusted to fit Children and the elderly. In the ClimApp Sciencetific Documents, we have included them as users. The following tasks and deliverables are copied from the document:
Here is the updated logo (I try to attach it here, not sure if it works, if does not work, I will send by email.)
the app is working after my phone dropped to floor this morning during coffee break :). More comments below:
ClimApp interface design flowchart suggestions, a climapp interface design flowchart_XG.pptx ttached.
nice! good to add to the troubleshoot faq! :-)
Op ma 8 apr. 2019 17:26 schreef Chuansi-LU notifications@github.com:
the app is working after my phone dropped to floor this morning during coffee break :). More comments below:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/frksteenhoff/ClimApp/issues/82#issuecomment-480879591, or mute the thread https://github.com/notifications/unsubscribe-auth/AL--ztJ9RlehuOuypYnLkMWI2_C_UgYUks5ve1-JgaJpZM4cXSXt .
thanks Chuansi for the detailed and valuable feedback. we list all feedback and can report all findings soon
regards boris
Op ma 8 apr. 2019 17:26 schreef Chuansi-LU notifications@github.com:
- The gauge showed a values of “-1.2”, next 3 hours “-1.0”, etc. This value is somewhat confusing with the temperature (currently 9 °C). For a short moment, I was thinking “was the temperature outside -1.2 °C”? Suggest: add “cold stress level” after “-1.2, -1.0, etc.”, otherwise it can be easily confused with temperature.
- The warning message “-25% colder than yesterday 11:00”: this can be a kind of warning, although I am not sure what advice (actions) I should take if it is -25% or -45% colder or +45% warmer than yesterday? It gives only relative risk warning, but difficult to provide advice (adaptation strategies), the latter should also be an important integrated part of ClimApp.
- “Dress in layers to combat the cold stress”, which is based on “-1.2 cold stress”. I wonder if cold stress level is “-1.0”, “-1.8”, “2.2”, “-2.5” or “-3.7”, how the user dress should dress? Will the advice also be “Dress in layers”?
- Part of the text, e.g. activity level is outside the screen. The gauge and temperature sizes can be reduced in order to show all texts below the screen.
- “Details” for advanced users are very interesting. Change “Body temperature” to “Body heat balance” because “body temperature” in thermal physiology is a temperature weighed between skin and core temperature.
- On Details screen, some texts are outside the screen (need to scroll down to see more?)
- I think “Dashboard” and “Settings” do not need to be on the top of all screen pages all the time. I will attach or send a suggested FlowChart, where at the upper left corner of the screen, user can click an icon “---” and go to Settings,
- The icon for “Rest” under Activity Level looks like the person is doing exercise (commented and suggested before by Stephen in his deliverable report). Suggest changing to an icon – sitting on sofa.
- There will be more comments later. According to the weather today, the prototype seems to have used IREQ model and WindChill temperature behind. Kalev is an experience researcher with IREQ model and cold environments. I suggest including him (kalev.kuklane@design.lth.se) in this internal test.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/frksteenhoff/ClimApp/issues/82#issuecomment-480879888, or mute the thread https://github.com/notifications/unsubscribe-auth/AL--zgBUq9E1rzM2WTiUBkzJ4QhVQFvaks5ve1-xgaJpZM4cXSXt .
I have just tested again. When clicked Settings, then my personal data disappeared (replaced by default data). Suggest: user's personal setting should be remained/saved there, unless the user clicks "Re-set personal settings". It would be nice if the user can click a button "My settings" like "My wardrobe", then my personal data/input will appear again (dob't need to input again).
Another test just now, Tair=2 C, Cold stress level=-2.1, Tip of the moment: "Dress in layers to combact the cold stress".
More comments after having tested the app for several consecutive Days when the weather is still Cold/cool.
Thanks Chuansi,
I have addressed your comments/questions below.
Kind regards, Boris
Windspeed shown in weather services is standard at 10m altitude. Windspeed in Climapp is currently calculated windspeed at 2m, obtained from weather forecast. Similar to how the windchill index converts windspeed (at 10m) to windspeed at person level.
Windstopper criterium is currently whenever Tair - Twindchill > 2.5C , as far as I know, any criterium we use will be arbitrary because no study or guideline exists. I do agree it should be different than currently in app.
the weather forecast is for 11am, what was the temperature at 11am?
obtaining the "current" situation from openweathermap is an open issue, not difficult to solve, but not in this version.
Asking "current", or "forecast" are 2 different things for weather services.
Furthermore, openweathermap is by my knowledge the only service that allows up to 60 calls per minute for free. This is important, because other services may give 1h forecasts, but easily charge >100Euro per month. This is not sustainable for when ClimApp ends.
The climapp implementation stores the weather data, so that if somebody in the neighbourhood uses the app at the same time, no new call to openweathermap has to be made.
Also climapp stores the weather data so that a reference to yesterday can actually be made. There is no weather service that allows for historical data retrieval for free, and they are very, very expensive (e.g. 10 euro per retrieval!, and there is no distinghuisment between 1day or 1 year of historical data). So our solution seems the most practical way forward.
We can use a rule based system for this, but what should be the rules? We should also be careful with ruling out the module information, because it is the rational simulation result, not the subjective interpretation.
yes, this is something I look into. It is an issue in the ISO implementation. If I find the conditions this happens, we should inform ISO on these cases, as IREQ or PHS fail on these thermal environemnts.
Tglobe is used for mean radiant temperature. But this is without taking into account cloud cover, and also does not include the effect of wind.
I agree on an iteration, yet I see within the climapp community we cannot reach agreement on what a user should be able to input.
done!
On Sun, Apr 14, 2019 at 11:50 AM Chuansi-LU notifications@github.com wrote:
More comments after having tested the app for several consecutive Days when the weather is still Cold/cool.
- Wind speed seems to be fixed at 1 m/s all the time. for example, in Lund when the wind speed is about 6 m/s, but the app sitll shows 1 m/s. This may be the problem of OpenWeatherMap?
- I have noticed that many time it suggests wearing windstopper even when wind speed low (1m/s) and WindChill temperature is not very Cold e.g. 4 C. Wind stopper clothing suggestion can be modified based on wind speed, e.g. >3 or 5m/s and WindChill temperature is Cold enough, e.g. <0 C.
- The weather app (fromThe Weather Channel) seems to have weather data updated every hour? I noticed once at about 8:20 am, Weather app showed 3 C, but ClimApp showed 8 C (for 11:00 am), a big temperature difference (5 C).
- The combination of low temperature, e.g. 8 C and Intense Activity, will lead to WBGT and PHS modules (on Details screen). I think WBGT will never reach threshold/reference value when temperature is <10 C. PHS may not be valid either (work time limitation and hydration suggesions) when temperature is < 10 C. For majority of population, this is still cold/cool environment, we probably cannot apply "heat module".
- On details screen, sometimes the exposure time limit is a minus value, e.g. -83, -280866 minutes.
- On details screen, "Radiation in full sunlight" e.g. 699 W/m2. How is this value converted to "mean radiant temperature" as input for IREQ? The outputs of IREQ after a few tests may suggest the mean radiant temperature inpuy is a bit too high.
- On Dashboard, we could try to keep only one activity Icon (e.g. medium) intead of 5 icons, and add one clothing Icon (e.g. business suit) on the same row, then add possiblity to go to next screen after clicking the activity or clothing icon to change activity and clothing level. As it is now, user is not very clear which clothing level (insulation) is used (default insulation input).
- on Disclaimer screen, change "European Research Association ..." to "European Research Area..."
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/frksteenhoff/ClimApp/issues/82#issuecomment-482939196, or mute the thread https://github.com/notifications/unsubscribe-auth/AL--zicUSZZVT73OWI8in2AcDgH6jYRIks5vgvnTgaJpZM4cXSXt .
Thank you Boris for the quick fix and feedback. A few responses below:
Best regards, Chuansi
From: Boris notifications@github.com Sent: 14 April 2019 12:35 To: frksteenhoff/ClimApp ClimApp@noreply.github.com Cc: Chuansi Gao chuansi.gao@design.lth.se; Comment comment@noreply.github.com Subject: Re: [frksteenhoff/ClimApp] FEEDBACK (#82)
Thanks Chuansi,
I have addressed your comments/questions below.
Kind regards, Boris
Windspeed shown in weather services is standard at 10m altitude. Windspeed in Climapp is currently calculated windspeed at 2m, obtained from weather forecast. Similar to how the windchill index converts windspeed (at 10m) to windspeed at person level.
correct. We discussed this within the consortium before. I have forgotten this difference between 2m and 10m height and now intuitively compare it directly with the wind speed from weather forecast. Hope users will not be confused. Perhaps to show wind speed at 10m height is a better choice even although climapp will use wind speed at 2m for calculations. A rough estimation of wind speed at 2m is about 67% wind speed at 10m high. 1m/s seems a bit low when wind speed from weather forecast is 6m/s?
Windstopper criterium is currently whenever Tair - Twindchill > 2.5C , as far as I know, any criterium we use will be arbitrary because no study or guideline exists. I do agree it should be different than currently in app.
maybe add another criterion, Twindchill should be <4 C (the highest temperature in Windchill table).
the weather forecast is for 11am, what was the temperature at 11am? At 11am, the tempeature was 8 C. the forecast was correct. If I remember right, ClimApp used weather data at 11:00am instead of 8:00am when the time was 8:20am.
obtaining the "current" situation from openweathermap is an open issue, not difficult to solve, but not in this version.
Ok, understand it needs time to change. There were other suggestions at very beginning of this project to use German weather forecast (DWD), but the API was not easy to use. This can be further discussed. I am not sure if DWD has now improved API ? MeteoSwiss suggested DWD and said DWD data would be open from 2018. I heard before another O2 app used American NOAA weather forecast data (open).
Asking "current", or "forecast" are 2 different things for weather services.
Furthermore, openweathermap is by my knowledge the only service that allows up to 60 calls per minute for free. This is important, because other services may give 1h forecasts, but easily charge >100Euro per month. This is not sustainable for when ClimApp ends.
I see.
The climapp implementation stores the weather data, so that if somebody in the neighbourhood uses the app at the same time, no new call to openweathermap has to be made.
Good.
Also climapp stores the weather data so that a reference to yesterday can actually be made. There is no weather service that allows for historical data retrieval for free, and they are very, very expensive (e.g. 10 euro per retrieval!, and there is no distinghuisment between 1day or 1 year of historical data). So our solution seems the most practical way forward.
I see. Good solution if the comparison with yesterday’s data is a necessary functionality. According to my test experience, as long as we have “thermal stress level”, eg. -2.0, it seems there is no need to show, e.g. “-37% colder than yesterday”. this can be further discussed as well.
We can use a rule based system for this, but what should be the rules? We should also be careful with ruling out the module information, because it is the rational simulation result, not the subjective interpretation.
in fact, when activity is very high, metabolic rate will exceed upper limits for IREQ, PMV, PHS models. We may need a model/criterion for athletes, for example, your WBGT for sports? Or provide advice saying something like “water loss is expected to be more than …(PHS predicted at highest level)”.
yes, this is something I look into. It is an issue in the ISO implementation. If I find the conditions this happens, we should inform ISO on these cases, as IREQ or PHS fail on these thermal environemnts.
When it appeaers again, I will note down the conditions.
Tglobe is used for mean radiant temperature. But this is without taking into account cloud cover, and also does not include the effect of wind.
Here we may need some modifications. Attached are a few pappers with equations (e.g. Kruger et al. 2014, Equation 1) to calculate Tmean_radiant.
I agree on an iteration, yet I see within the climapp community we cannot reach agreement on what a user should be able to input.
done!
On Sun, Apr 14, 2019 at 11:50 AM Chuansi-LU notifications@github.com<mailto:notifications@github.com> wrote:
More comments after having tested the app for several consecutive Days when the weather is still Cold/cool.
- Wind speed seems to be fixed at 1 m/s all the time. for example, in Lund when the wind speed is about 6 m/s, but the app sitll shows 1 m/s. This may be the problem of OpenWeatherMap?
- I have noticed that many time it suggests wearing windstopper even when wind speed low (1m/s) and WindChill temperature is not very Cold e.g. 4 C. Wind stopper clothing suggestion can be modified based on wind speed, e.g. >3 or 5m/s and WindChill temperature is Cold enough, e.g. <0 C.
- The weather app (fromThe Weather Channel) seems to have weather data updated every hour? I noticed once at about 8:20 am, Weather app showed 3 C, but ClimApp showed 8 C (for 11:00 am), a big temperature difference (5 C).
- The combination of low temperature, e.g. 8 C and Intense Activity, will lead to WBGT and PHS modules (on Details screen). I think WBGT will never reach threshold/reference value when temperature is <10 C. PHS may not be valid either (work time limitation and hydration suggesions) when temperature is < 10 C. For majority of population, this is still cold/cool environment, we probably cannot apply "heat module".
- On details screen, sometimes the exposure time limit is a minus value, e.g. -83, -280866 minutes.
- On details screen, "Radiation in full sunlight" e.g. 699 W/m2. How is this value converted to "mean radiant temperature" as input for IREQ? The outputs of IREQ after a few tests may suggest the mean radiant temperature inpuy is a bit too high.
- On Dashboard, we could try to keep only one activity Icon (e.g. medium) intead of 5 icons, and add one clothing Icon (e.g. business suit) on the same row, then add possiblity to go to next screen after clicking the activity or clothing icon to change activity and clothing level. As it is now, user is not very clear which clothing level (insulation) is used (default insulation input).
- on Disclaimer screen, change "European Research Association ..." to "European Research Area..."
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/frksteenhoff/ClimApp/issues/82#issuecomment-482939196, or mute the thread https://github.com/notifications/unsubscribe-auth/AL--zicUSZZVT73OWI8in2AcDgH6jYRIks5vgvnTgaJpZM4cXSXt .
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/frksteenhoff/ClimApp/issues/82#issuecomment-482944588, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfkasncocPVGT3VP33T_s12tgoml8cWKks5vgwRegaJpZM4cXSXt.
Need to be added to list, feedback from Amitava Is nice to see that I don’t need to set repeatedly my subjective info. Great!
The showed temperature in the app varied a lot with the actual one at my living city, Lund. It’s been like this since I started using the app. It is difficult to rely on this. I do not want to open another app in order to confirm current temperature while I am using my preferred app for example, Climapp.
It is not understandable at least for me by that is appearing ‘next 3 hours, next 6 hours…. Something in green color what is that? The time shows just below green colored numbers are different than next 3 hours. I am understood it is 3 hour after the current time. For example I’m using the app at 8 am and next 3 hours for me is 11 am but it shows 2 pm. It think that it not clear for most of us.
However I opened the app with an expectation to get info about how the weather will be in next few hours when I wish to be outside for my physical training including running, plyometric etc.
In this case, I need a summary for the weather detail, my clothing types, no of layers (suggestion), hydration and so on. The suggestions can based on the activity, duration and weather.
Moreover, the tip is showing under each intensity of work does not match with activity levels and weather but the appeared ones are funny.
issue closed as versions have been solved in version 2.057
User feedback
Feedback from ClimApp testers (1st beta version). All feedback will be listed here, the rate with which we implement the changes (and whether we are going to implement the changes) will be decided by the developer team.
Please add comments if you have any.
Improvement of existing implementation
Experienced/expert users
age
,height
,weight
values to match range of most narrow model. Do they also work for children?Inexperienced users
x% colder/warmer than yesterday
could possibly be changed into/be accompanied by a textual description like "it is very much colder than yesterday) The percentage make it more accurate but also more scientific which might not be the best solution for the end user.Suggestions to new functionality