Forecasting
Holiday Savings
With Christmas rapidly approaching and neighborhoods throughout North America intricately decorated with a variety of Christmas lights, I can’t help but ponder how many folks are using LED Christmas lights, and whether or not I can identify an LED set from an incandescent as I stroll down the block.
For the sake of curiosity, I stopped by a store on the way home from the office one evening to compare the regular incandescent and LED Christmas lights. While, I’m not a Christmas light expert and I don’t know which may be better for certain weather conditions and visual effects, I do contend that most of the LED Christmas lights sold are just as good in terms of color and brightness as any incandescent set. For example, the advertised lights below are described as having a “warm, traditional glow” similar to that of incandescent.
Looks pretty good to me!
If there’s no discernible difference in lighting quality, then the deciding factor when it comes to buying LED Christmas lights is, “How much money will I save each Christmas season?” Obviously, savings depends on where you live, which lights are used, and how long the lights are on (and your level of Christmas spirit). But let’s consider the math. A 100-count string of incandescent lights runs at about 40 watts. A similar set with LED lights runs at about 5 watts (about 88% less power). With the average price of electricity in the U.S. of 11.3 cents per kilowatt hour (EnergyStar.Gov), the average cost of powering incandescent Christmas lights this season can range from $10.78 to $310.73. Using the same parameters for LED lights, the range is $1.63 to $40.15. That’s a pretty big price difference. I am interested to see if any utilities have noticed a change in loads during the Christmas season due to more homes adopting LEDs.
How much money do you think this home spends on Christmas lighting? How much do you think they would save if they used LEDs?
Happy Holidays everyone! See you in 2015!
For the sake of curiosity, I stopped by a store on the way home from the office one evening to compare the regular incandescent and LED Christmas lights. While, I’m not a Christmas light expert and I don’t know which may be better for certain weather conditions and visual effects, I do contend that most of the LED Christmas lights sold are just as good in terms of color and brightness as any incandescent set. For example, the advertised lights below are described as having a “warm, traditional glow” similar to that of incandescent.
Looks pretty good to me!
If there’s no discernible difference in lighting quality, then the deciding factor when it comes to buying LED Christmas lights is, “How much money will I save each Christmas season?” Obviously, savings depends on where you live, which lights are used, and how long the lights are on (and your level of Christmas spirit). But let’s consider the math. A 100-count string of incandescent lights runs at about 40 watts. A similar set with LED lights runs at about 5 watts (about 88% less power). With the average price of electricity in the U.S. of 11.3 cents per kilowatt hour (EnergyStar.Gov), the average cost of powering incandescent Christmas lights this season can range from $10.78 to $310.73. Using the same parameters for LED lights, the range is $1.63 to $40.15. That’s a pretty big price difference. I am interested to see if any utilities have noticed a change in loads during the Christmas season due to more homes adopting LEDs.
How much money do you think this home spends on Christmas lighting? How much do you think they would save if they used LEDs?
Happy Holidays everyone! See you in 2015!
Kesalahan terjadi ketika Memproses Template.
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>
The following has evaluated to null or missing: ==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1] ----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>