- This topic has 11 replies, 4 voices, and was last updated 9 years, 5 months ago by
.
-
Posts
-
if I set the humidity to zero – I get a 123% water level
if I set the humidity to one – I get a 151% water level
if I set the humidity to 100 – I get 123%
10% = 149%looks like 0% is 100%
I am not sure what you mean. The weight you set to humidity basically controls how much ‘humidity’ influences the water level formula. Setting a weight to 0 means the humidity factor does not influence the water level at all (and therefore only temperature and rain fall have an effect on the water level).
Setting humidity to zero is giving the same result as setting it to 100. To ignore humidity I had to set it to one percent.
I think the validateValues function used by the weather.js has a flaw where it invalidates 0 when it is compared to null…then when the scale is calculated an invalid value causes the scale to result in 100. This would be the only cause I can find for the issue.
@Shawn what do you mean when comparing 0 to null? I am using the triple equal sign to compare meaning it should be exactly the same and not just similar.
If I am misunderstanding this, do you mind pointing it out so we can take a look at it?
Thank you!
Sorry I missed the triple = comparison. You are absolutely correct that should compare value and type. So the problem isn’t there, and after a second look, that function is checking weather data, not the values of the weights. I read way too fast.
We would need all of the weights and the temp, humidity,and precip values from weather to figure it out.
Can we start by getting what location you are using @pantonvich? I can start dumping the values and doing some comparisons with that information.
Thanks!
With your location known, I found the log entries for the queries to the weather service. One unique thing is the URL encoding. Here is what I am seeing in the log data:
[08/Aug/2015:01:11:18 +0000] "GET /weather1.py?loc=pws:KGAATLAN40&key=*removed*&fwv=215&wto=\x22h\x22:10,\x22t\x22:100,\x22r\x22:100 HTTP/1.1" 200Notice the quotes are replaced with \x22 when the URL encoding should be %22.
I am not sure if this is being changed on our end however I have noticed you are not the only one being affected by this. I am going to update the script to handle this situation and see if it resolves the issue.
Update: The changes are done. I still am not confident this is the fix needed since you saw some variability when changing the options. With that said, let me know if this makes any difference.
that looks to have fixed the issue setting humility I got the following water levels:
100% was 6%
10% was 47%
0% was 52%thanks
Okay great! I am still investigating where the encoding is coming from but at least we know we found the problem and fixed it.
Thanks!
- You must be logged in to reply to this topic.