EMK:Ancillary Files - Revision history

Sisep: /* File Input Files */

2013-02-07T20:55:42Z

File Input Files

Sisep: /* File Input Files */

2013-02-07T20:55:30Z

File Input Files

Sisep: /* Inflows File */

2013-02-07T20:54:51Z

Inflows File

Sisep: /* Inflows File */

2012-12-04T03:41:43Z

Inflows File

Sisep: /* Demand Profile Files */

2012-12-04T03:41:08Z

Demand Profile Files

Sisep: /* File Input Files */

2012-12-04T03:40:26Z

File Input Files

Sisep at 02:46, 20 November 2012

2012-11-20T02:46:12Z

Sisep: /* File Input Files */

2012-11-20T02:45:17Z

File Input Files

Sisep: /* File Input Files */

2012-11-20T02:43:22Z

File Input Files

Sisep: /* File Input Files */

2012-11-20T02:42:17Z

File Input Files

@@ Line 41: / Line 41: @@
 ==File Input Files==
-User-defined input files containing static data can be imported by EMarket for use at Run time.  This feature allows you to use distributions of data series produced by an external application (or by hand) in your forecasts.  Each input file can only contain values for a single modelled variable and a single consistent time interval (weekly, daily or half hourly).  A variable name is assigned to an input file through the '''''File Input Box''''' in the '''''[[EMK:Run Window | Run Window]]'''''  Values for the variable used during a Run will be reported in the global output in the '''''Results Panel''''' of the '''''[[EMK:Main Window | Main Window]]''''''  It is also possible to include the variable (by name) in formulae throughout EMarket.
+User-defined input files containing static data can be imported by EMarket for use at Run time.  This feature allows you to use distributions of data series produced by an external application (or by hand) in your forecasts.  Each input file can only contain values for a single modelled variable and a single consistent time interval (weekly, daily or half hourly).  A variable name is assigned to an input file through the '''''File Input Box''''' in the '''''[[EMK:Run Window | Run Window]]'''''  Values for the variable used during a Run will be reported in the global output in the '''''Results Panel''''' of the '''''[[EMK:Main Window | Main Window]]'''''  It is also possible to include the variable (by name) in formulae throughout EMarket.
 [[File:User File hh.jpg|250px|thumb|right|Half-hourly data file format]]
 '''To create or edit a user-defined file:'''

@@ Line 41: / Line 41: @@
 ==File Input Files==
-User-defined input files containing static data can be imported by EMarket for use at Run time.  This feature allows you to use distributions of data series produced by an external application (or by hand) in your forecasts.  Each input file can only contain values for a single modelled variable and a single consistent time interval (weekly, daily or half hourly).  A variable name is assigned to an input file through the '''''File Input Box''''' in the [[EMK:Run Window | Run Window]]  Values for the variable used during a Run will be reported in the global output in the '''''Results Panel''''' of the [[EMK:Main Window | Main Window]]  It is also possible to include the variable (by name) in formulae throughout EMarket.
+User-defined input files containing static data can be imported by EMarket for use at Run time.  This feature allows you to use distributions of data series produced by an external application (or by hand) in your forecasts.  Each input file can only contain values for a single modelled variable and a single consistent time interval (weekly, daily or half hourly).  A variable name is assigned to an input file through the '''''File Input Box''''' in the '''''[[EMK:Run Window | Run Window]]'''''  Values for the variable used during a Run will be reported in the global output in the '''''Results Panel''''' of the '''''[[EMK:Main Window | Main Window]]''''''  It is also possible to include the variable (by name) in formulae throughout EMarket.
 [[File:User File hh.jpg|250px|thumb|right|Half-hourly data file format]]
 '''To create or edit a user-defined file:'''

@@ Line 17: / Line 17: @@
 |}
-The inflow identifier is a value from the ''Inflow Name'' field of the '''''Inflows Box''''' in the [[EMK:Run Window | Run Window]], and from the ''Controlled Inflow'' and ''Uncontrolled Inflow'' fields in '''''Hydro Station Generator Window''''', for example, Cobbcon and CobbUn for the controlled and uncontrolled inflows for Cobb.
+The inflow identifier is a value from the ''Inflow Name'' field of the '''''Inflows Box''''' in the '''''[[EMK:Run Window | Run Window]]''''', and from the ''Controlled Inflow'' and ''Uncontrolled Inflow'' fields in '''''Hydro Station Generator Window''''', for example, Cobbcon and CobbUn for the controlled and uncontrolled inflows for Cobb.
 The year is the inflow year and the Week 1 through Week 53 inflow data are the weekly average inflows in cumecs.

@@ Line 17: / Line 17: @@
 |}
-The inflow identifier is a value from the ''Inflow Name'' field of the '''''Inflows Box''''' in the '''''Run Window''''', and from the ''Controlled Inflow'' and ''Uncontrolled Inflow'' fields in '''''Hydro Station Generator Window''''', for example, Cobbcon and CobbUn for the controlled and uncontrolled inflows for Cobb.
+The inflow identifier is a value from the ''Inflow Name'' field of the '''''Inflows Box''''' in the [[EMK:Run Window | Run Window]], and from the ''Controlled Inflow'' and ''Uncontrolled Inflow'' fields in '''''Hydro Station Generator Window''''', for example, Cobbcon and CobbUn for the controlled and uncontrolled inflows for Cobb.
 The year is the inflow year and the Week 1 through Week 53 inflow data are the weekly average inflows in cumecs.

@@ Line 34: / Line 34: @@
 A Demand profile file ''(<Grid name>_DP.dat)'' contains a list of Nodes and their proportional share of Demand for a particular year (by period), where the year runs from 1st April of a year to 31st March of the next. The proportional share is calculated on the basis of actual metered data for a year and is stored to half hourly detail. So, for a particular Node on a particular day, in a particular half hour period, that Node's (proportional) share of total annual Demand at that time is held.
-The proportional demand figures are used in ''EMarket'' when Demand figures are set in the '''Demand Box''' of the '''''Run Window.''''' They are used in the following way:
+The proportional demand figures are used in ''EMarket'' when Demand figures are set in the '''Demand Box''' of the '''''[[EMK:Run Window | Run Window]]''''' They are used in the following way:
 Suppose that two Demand Regions, dem1 and dem2, have been created, and for these Regions annual demands of 16,000 and 12,000 GWh, respectively, have been assigned. dem1 contains the following Nodes: BOB, ROB and DOG, while dem2 contains RIB and NIB. For a particular half hour period in the Demand profile containing these Nodes, imagine that the Node's proportional Demand figures are 0.01, 0.03, 0.15, 0.001 and 0.02 respectively. Of course in reality these figures would be orders of magnitude smaller, but we'll use them for simplicity's sake. For the four hour period in question, BOB's share of Demand would then be 0.01/(0.01 + 0.03 + 0.15) × 16000 = 842 GWh, while RIB's would be 0.001/(0.001 + 0.02) × 12000 = 571 GWh.

← Older revision		Revision as of 02:46, 20 November 2012
Line 64:		Line 64:
	*In cases where a Run uses a Tick step smaller than the time interval used in the input file, EMarket will find the best fit value for the variable. For example a half hourly Run using input data provided in daily intervals will use the same value for the variable in every Tick during any given forecast day		*In cases where a Run uses a Tick step smaller than the time interval used in the input file, EMarket will find the best fit value for the variable. For example a half hourly Run using input data provided in daily intervals will use the same value for the variable in every Tick during any given forecast day
	*In cases where a Run uses a Tick step larger than the time interval used in the input file, EMarket will find the nearest point value from the input file for the variable. For example in the case of a 4 hourly Run using input data in half hourly intervals, the point value from the first half hour in the input file will be used for the first 4 hourly Tick and the point value from the ninth half hour will be used for the second 4 hourly Tick, and so on.		*In cases where a Run uses a Tick step larger than the time interval used in the input file, EMarket will find the nearest point value from the input file for the variable. For example in the case of a 4 hourly Run using input data in half hourly intervals, the point value from the first half hour in the input file will be used for the first 4 hourly Tick and the point value from the ninth half hour will be used for the second 4 hourly Tick, and so on.
		+
		+
		+	[[EMK:EMarket User Manual \| Back to User Manual Main Page]]

@@ Line 60: / Line 60: @@
 Note: When editing these files, ensure you have common year entries for each user defined input.
 When using the the input file feature the following points should be noted:
 *In cases where a Run uses a Tick step smaller than the time interval used in the input file, EMarket will find the best fit value for the variable. For example a half hourly Run using input data provided in daily intervals will use the same value for the variable in every Tick during any given forecast day
 *In cases where a Run uses a Tick step larger than the time interval used in the input file, EMarket will find the nearest point value from the input file for the variable.  For example in the case of a 4 hourly Run using input data in half hourly intervals, the point value from the first half hour in the input file will be used for the first 4 hourly Tick and the point value from the ninth half hour will be used for the second 4 hourly Tick, and so on.

← Older revision		Revision as of 02:43, 20 November 2012
Line 58:		Line 58:

	[[File:User File DW.jpg\|250px\|thumb\|right\|Daily or Weekly data file format]]		[[File:User File DW.jpg\|250px\|thumb\|right\|Daily or Weekly data file format]]
		+
	Note: When editing these files, ensure you have common year entries for each user defined input.		Note: When editing these files, ensure you have common year entries for each user defined input.
		+
		+
		+	When using the the input file feature the following points should be noted:
		+	*In cases where a Run uses a Tick step smaller than the time interval used in the input file, EMarket will find the best fit value for the variable. For example a half hourly Run using input data provided in daily intervals will use the same value for the variable in every Tick during any given forecast day
		+	*In cases where a Run uses a Tick step larger than the time interval used in the input file, EMarket will find the nearest point value from the input file for the variable. For example in the case of a 4 hourly Run using input data in half hourly intervals, the point value from the first half hour in the input file will be used for the first 4 hourly Tick and the point value from the ninth half hour will be used for the second 4 hourly Tick, and so on.

← Older revision		Revision as of 02:42, 20 November 2012
Line 58:		Line 58:

	[[File:User File DW.jpg\|250px\|thumb\|right\|Daily or Weekly data file format]]		[[File:User File DW.jpg\|250px\|thumb\|right\|Daily or Weekly data file format]]
		+	Note: When editing these files, ensure you have common year entries for each user defined input.