Difference between revisions of "WCmore's Graphs"

From webCoRE Wiki - Web-enabled Community's own Rule Engine
Jump to: navigation, search
m (twcweather.forecast.daypart[0])
m (twcweather.forecast.daypart[0])
 
(14 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
== twcweather.forecast.daypart[0] ==
 
== twcweather.forecast.daypart[0] ==
  
Twice a day, some of the data stored under [[TWC_Weather#Partial_day_forecast|twcweather.forecast.daypart[0]]] shifts.  Preliminary tests over 26 days (''52 data points'') shows it changes sometime between 2:58 and 3:36.  Frequently, it changed between 3:02 and 3:07, but in reality, the time varies quite a bit from day by day.
+
Twice a day, some of the data stored under [[TWC_Weather#Partial_day_forecast|twcweather.forecast.daypart[0]]] will shift.  Preliminary tests over 33 days (''67 data points'') shows it changes sometime between 2:58 and 3:36.  Frequently, it changed between 3:02 and 3:07, but in reality, the time varies quite a bit from day by day.
  
Here is a quick graph to show how much variety over 26 days...  (''the numbers show how many minutes past 3 AM/PM'')
+
Here is a quick graph to show how much variety over 33 days...  (''the numbers show how many minutes past 3 AM/PM'')
  
[[File:TwcChangeoverRotate4.jpg|none]]
+
[[File:TwcChangeoverRotate5.jpg|none]]
  
The change over can't automatically trigger a piston, so to determine the time it changes I have to query it multiple times, and take note of when it changes.  Each mark above denotes the last time the old data was seen, and the first time the new data was seen.  The long bars are when I was checking every 5 or 10 minutes... The short bars are when I was checking every minute (''to narrow it down more precisely'').  
+
The change over can't automatically trigger a piston, so to determine the time it changes I have to query it multiple times, and take note of when it changes.  Each mark above denotes the last time the old data was seen, and the first time the new data was seen. (''the changeover happened sometime in between'') The long bars are when I was checking every 5 or 10 minutes... The short bars are when I was checking every minute (''to narrow it down more precisely'').  
  
 
For those wanting a reliable piston, I would make your queries at 3:40 AM/PM (''or later'') to assure that you are getting the new data.  On the other hand, if you want to capture the old data right before it vanishes, I would grab that at 2:50 AM/PM (''or earlier'').
 
For those wanting a reliable piston, I would make your queries at 3:40 AM/PM (''or later'') to assure that you are getting the new data.  On the other hand, if you want to capture the old data right before it vanishes, I would grab that at 2:50 AM/PM (''or earlier'').
 +
 +
TL;DR...  Do '''not''' rely on the twcweather.forecast results from 2:59 - 3:35 (both AM & PM)
  
 
----
 
----
Line 16: Line 18:
 
WebCoRE's official page on [[TWC_Weather#Partial_day_forecast|$twcweather.forecast.daypart[0]]]
 
WebCoRE's official page on [[TWC_Weather#Partial_day_forecast|$twcweather.forecast.daypart[0]]]
  
== $twcweather.conditions.sunriseTimeLocal ==
+
== twcweather.conditions.sunriseTimeLocal ==
  
So far, the sunrise/sunset times seem to change over between 11:59 and 12:11, as seen here:
+
In the past four weeks, the sunrise/sunset times seem to change over between 11:59 and 12:11, as seen here:
  
[[File:TwcSunriseRotate3.jpg|none]]
+
[[File:TwcSunriseRotate5.jpg|none]]
  
It is important to note that once, I saw the '''new''' times come in, and one minute later it reverted back to the '''old''' data, and another minute later the '''new''' data returned (''and stuck this time'').
+
It is important to note that twice, I saw the '''new''' times come in, and one minute later it reverted back to the '''old''' data, and another minute later the '''new''' data returned (''and stuck this time'').
  
 
* 12:00:37 AM ¦2019-03-29T06:53:23-0700  <-- OLD
 
* 12:00:37 AM ¦2019-03-29T06:53:23-0700  <-- OLD
Line 28: Line 30:
 
* 12:02:33 AM ¦2019-03-29T06:53:23-0700  <-- OLD
 
* 12:02:33 AM ¦2019-03-29T06:53:23-0700  <-- OLD
 
* 12:03:48 AM ¦2019-03-30T06:52:00-0700  <-- NEW
 
* 12:03:48 AM ¦2019-03-30T06:52:00-0700  <-- NEW
 +
 +
For those wanting a reliable piston, I would make your queries at 12:15 AM (or later) to assure that you are getting the new data.  On the other hand, if you want to capture the old data right before it vanishes, I would grab that at 11:55 PM (or earlier).
 +
 +
TL;DR...  Do '''not''' rely on the sunrise & sunset results from 11:59pm - 12:11am
 +
 +
----
 +
 +
Just want to confirm (months later) that the time ranges listed above are still accurate.
 +
[[File:TimeCheck.jpg|none]]
  
 
----
 
----
  
 
WebCoRE's official page on [[TWC_Weather#Conditions|$twcweather.conditions]]
 
WebCoRE's official page on [[TWC_Weather#Conditions|$twcweather.conditions]]

Latest revision as of 01:48, 9 January 2022

twcweather.forecast.daypart[0]

Twice a day, some of the data stored under twcweather.forecast.daypart[0] will shift. Preliminary tests over 33 days (67 data points) shows it changes sometime between 2:58 and 3:36. Frequently, it changed between 3:02 and 3:07, but in reality, the time varies quite a bit from day by day.

Here is a quick graph to show how much variety over 33 days... (the numbers show how many minutes past 3 AM/PM)

TwcChangeoverRotate5.jpg

The change over can't automatically trigger a piston, so to determine the time it changes I have to query it multiple times, and take note of when it changes. Each mark above denotes the last time the old data was seen, and the first time the new data was seen. (the changeover happened sometime in between) The long bars are when I was checking every 5 or 10 minutes... The short bars are when I was checking every minute (to narrow it down more precisely).

For those wanting a reliable piston, I would make your queries at 3:40 AM/PM (or later) to assure that you are getting the new data. On the other hand, if you want to capture the old data right before it vanishes, I would grab that at 2:50 AM/PM (or earlier).

TL;DR... Do not rely on the twcweather.forecast results from 2:59 - 3:35 (both AM & PM)


WebCoRE's official page on $twcweather.forecast.daypart[0]

twcweather.conditions.sunriseTimeLocal

In the past four weeks, the sunrise/sunset times seem to change over between 11:59 and 12:11, as seen here:

TwcSunriseRotate5.jpg

It is important to note that twice, I saw the new times come in, and one minute later it reverted back to the old data, and another minute later the new data returned (and stuck this time).

  • 12:00:37 AM ¦2019-03-29T06:53:23-0700 <-- OLD
  • 12:01:36 AM ¦2019-03-30T06:52:00-0700 <-- NEW
  • 12:02:33 AM ¦2019-03-29T06:53:23-0700 <-- OLD
  • 12:03:48 AM ¦2019-03-30T06:52:00-0700 <-- NEW

For those wanting a reliable piston, I would make your queries at 12:15 AM (or later) to assure that you are getting the new data. On the other hand, if you want to capture the old data right before it vanishes, I would grab that at 11:55 PM (or earlier).

TL;DR... Do not rely on the sunrise & sunset results from 11:59pm - 12:11am


Just want to confirm (months later) that the time ranges listed above are still accurate.

TimeCheck.jpg

WebCoRE's official page on $twcweather.conditions