Forecasting

I Have the Power

August 05, 2021

In econometrics generally and energy modeling specifically, variables in equations often include an exponent. In particular, this is often seen in price variables. That is, the price is raised to an exponent to impose a magnitude and direction for the responsiveness (of energy or sales) to changes in its price. In the case of electricity, the price is typically negative and fractional (e.g., -0.2. -0.1), which suggests that increases in price result in decreased consumption. If the absolute value of the exponent is greater than one (1.0), the variable is said to be elastic. If the absolute value of the exponent is less than one (1.0), the variable is said to be inelastic.

The meaning of the exponent is clear when the number is an integer greater than 1.

The following figure depicts x raised to the powers of 1, 2, 3, and 4. As the magnitude of the exponent increases, the steepness of the curve increases. That is, x4 is much steeper than x1. In fact, x1 is barely visible below, as the magnitude of x4 swamps it.

Power

That seems simple enough. Now let’s extend the idea. What is the mathematical interpretation of a decimal exponent? The best way to think about this is in terms of fractions, rather than decimals. Since any terminating decimal can be written as the quotient of two integers, this is easily represented by the following example:

Once the decimal is converted into a fraction, we can express the exponent more generally as follows:

The denominator (b) of the fraction is the root of the base (x) and the numerator (a) is the exponent to which the root is raised, which can also be written more intuitively as follows:

The following is a numerical example:

The following figure depicts x raised to the powers of 1/4, 2/4, 3/4, and 4/4 (respectively equal to 0.25, 0.5, 0.75, and 1). As in the case of the integer exponents above, the steepness of the curve increases as the magnitude of the exponent increases. Viewed alternatively, the curve flattens (i.e., gets closer to 0) as the decimal gets smaller. Thus, x1/4 is closer to 0 on the y-axis than x4/4 (which is equivalent to x1).

Power

As alluded to above, we often use negative exponents in energy forecasting.

The rule for evaluating this expression is to take the multiplicative inverse of the number and raise it to the positive power. Thus, the above expression becomes:

We can extend this idea to negative fractional exponents:

This can also be expressed as:

Let’s return to our original numerical example, except this time with a negative exponent:

After all of the intermediate steps, you should note that the result (1/125) is simply the inverse of the original result (125).

With this knowledge, you can now interpret exponents with a deeper level of understanding for your modeling with MetrixND. More importantly, you are now well-equipped to speak intelligently to the next 10th grader you meet.

There’s more great information on a variety of load forecasting topics available in the forecasting section of the Itron website and we invite you to also register for our regular free webinars. Let us help you improve your forecasts! Contact us at forecasting@itron.com.

Se ha producido un error al procesar la plantilla.
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>