Create a Pathway - Revision history

Aanjum: /* Internal Links */

2012-01-24T19:18:07Z

Internal Links

← Older revision		Revision as of 19:18, January 24, 2012
Line 37:		Line 37:
	==Internal Links==		==Internal Links==
	* [[How_to\|How to]]		* [[How_to\|How to]]
			* [[Stationary Process#Editor\|Stationary Process Editor]]

Cmcooney: /* Create a Pathway */

2012-01-17T16:30:11Z

Create a Pathway

Aanjum: /* Define Processes */

2012-01-16T17:53:17Z

Define Processes

← Older revision		Revision as of 17:53, January 16, 2012
Line 17:		Line 17:
	''See more details for [[Process Editors]]''		''See more details for [[Process Editors]]''

	In GREET two major types of processes can be defined : Stationary Processes and ~~Stationary~~ Processes. The actual database contains most of the processes used in GREET 1.8d_0, so if the necessary processes for that pathway are already in the database, there is no need to create new ones.		In GREET two major types of processes can be defined : Stationary Processes and Transportation Processes. The actual database contains most of the processes used in GREET 1.8d_0, so if the necessary processes for that pathway are already in the database, there is no need to create new ones.

	If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.		If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.



	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===

Ddieffenthaler: /* Create a Pathway */

2012-01-13T21:36:01Z

Create a Pathway

← Older revision		Revision as of 21:36, January 13, 2012
Line 20:		Line 20:

	If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.		If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.



	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===
Line 34:		Line 36:

	Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.		Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.

			==Internal Links==
			* [[How_to\|How to]]

Ddieffenthaler: /* Define Processes */

2012-01-13T21:34:58Z

Define Processes

← Older revision		Revision as of 21:34, January 13, 2012
Line 16:		Line 16:
	===Define Processes===		===Define Processes===
	''See more details for [[Process Editors]]''		''See more details for [[Process Editors]]''

			In GREET two major types of processes can be defined : Stationary Processes and Stationary Processes. The actual database contains most of the processes used in GREET 1.8d_0, so if the necessary processes for that pathway are already in the database, there is no need to create new ones.

			If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.

	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===

Ddieffenthaler: /* Build the Pathway using the Pathway Editor */

2012-01-13T21:32:15Z

Build the Pathway using the Pathway Editor

← Older revision		Revision as of 21:32, January 13, 2012
Line 21:		Line 21:
	Editing a pathway have to be done from the Data Editor form, then click on the "Pathways" menu and "Add Pathway" this will open the pathway editor.		Editing a pathway have to be done from the Data Editor form, then click on the "Pathways" menu and "Add Pathway" this will open the pathway editor.

	As shown on the left the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes, which are located in the left column, will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.		As shown on the left the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes, which are located in the left column, will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.

	[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]		[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]

Ddieffenthaler: /* Build the Pathway using the Pathway Editor */

2012-01-13T21:32:06Z

Build the Pathway using the Pathway Editor

← Older revision		Revision as of 21:32, January 13, 2012
Line 19:		Line 19:
	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===
	[[File:pathway_editor.png\|300px\|thumb\|left\|Drag and dropping processes]]		[[File:pathway_editor.png\|300px\|thumb\|left\|Drag and dropping processes]]
	Editing a pathway have to be done from the Data Editor form, then click on the "Pathways" menu and "Add Pathway" this will open the pathway editor. As shown on the screenshot the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes available will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.		Editing a pathway have to be done from the Data Editor form, then click on the "Pathways" menu and "Add Pathway" this will open the pathway editor.

	~~Then to save~~ the ~~process, a name~~ is ~~required~~. The ~~Hidden option will hide or not this pathway from~~ the ~~GUI~~, ~~this option can~~ be ~~used for some legacy pathways that we still want~~ to ~~be in~~ the ~~database but not shown to not overwhelm~~ the ~~GUI. The ID is what will be used internally to refer to this~~ pathway, ~~therefore this number is automatically generated by~~ the ~~GUI. Notes~~ can be ~~used to give some indications about~~ the pathway and ~~are saved in the database~~.		As shown on the left the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes, which are located in the left column, will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.

	[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]		[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]

	On the right side of the pathway editor, the feeds selection tab is shown~~, this might be used~~ for processes ~~which need~~ a feed~~. When an issue~~ is ~~detected after a process has been dropped a message appears~~ at the ~~top~~ of ~~the~~ pathway ~~editor, in the~~ case ~~of the screenshot on the right, we dropped~~ a process which have ~~inputs from previous~~, but ~~in the current pathway, there is nothing before. So to solve~~ this ~~conflict we can either drop a process before, which have for output~~ Bituminous Coal ~~in this example~~, ~~or drop~~ a ~~"feed"~~ which ~~represent~~ a ~~material Source. In this case~~ the ~~material Source contains a single pathway to create bituminous coal, we are using this to feed out process~~.		On the right side of the pathway editor, the feeds selection tab is shown .The different feeds available are shown on the right side after the panel have been expanded. Then as for processes it's just a matter of drag and dropping. The feed is used at the beginning of a pathway to replace a material Mix. Let's think about that case : you have a process which have as an input Bituminous Coal, but this Bituminous Coal might come from different pathways. Instead of drawing those different pathways again and again, we are going to replace them with a Feed box, which is a Mix of the results from those pathways.

	~~The different feeds available are shown~~ on the right ~~side after~~ the ~~panel~~ have ~~been expanded~~. Then as for ~~processes it's just a matter of drag~~ and ~~dropping~~.		When an issue is detected after a process has been dropped a message appears at the top of the pathway editor, in the case of the screenshot on the right, we dropped a process which have inputs from previous, but in the current pathway, there is nothing before. So to solve this conflict we can either drop a process before, which have for output Bituminous Coal in this example, or drop a "feed" which represent a material Source. In this case the material Source contains a single pathway to create bituminous coal, we are using this to feed out process.

			Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.

Ddieffenthaler: /* Build the Pathway using the Pathway Editor */

2012-01-13T21:24:25Z

Build the Pathway using the Pathway Editor

← Older revision		Revision as of 21:24, January 13, 2012
Line 18:		Line 18:

	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===
			[[File:pathway_editor.png\|300px\|thumb\|left\|Drag and dropping processes]]
			Editing a pathway have to be done from the Data Editor form, then click on the "Pathways" menu and "Add Pathway" this will open the pathway editor. As shown on the screenshot the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes available will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.

			Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.

			[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]

			On the right side of the pathway editor, the feeds selection tab is shown, this might be used for processes which need a feed. When an issue is detected after a process has been dropped a message appears at the top of the pathway editor, in the case of the screenshot on the right, we dropped a process which have inputs from previous, but in the current pathway, there is nothing before. So to solve this conflict we can either drop a process before, which have for output Bituminous Coal in this example, or drop a "feed" which represent a material Source. In this case the material Source contains a single pathway to create bituminous coal, we are using this to feed out process.

			The different feeds available are shown on the right side after the panel have been expanded. Then as for processes it's just a matter of drag and dropping.

Ddieffenthaler: /* Create a Pathway */

2012-01-11T16:22:18Z

Create a Pathway

← Older revision		Revision as of 16:22, January 11, 2012
Line 9:		Line 9:
	===Define Resources===		===Define Resources===
	''See more details for [[Resources Editor]]''		''See more details for [[Resources Editor]]''

			In order to link all the processes together, resources and products for each of them needs to be entered in the database. Usually we define a name and some physical properties if they apply like heating values or carbon and sulfur ratios. Those resources will be used to define the Inputs of a process and their Products. A simple example could be a coal electric plant which uses '''Coal''' as an input and produces '''Electricity'''. '''Coal''' and '''Electricity''' needs to be defined in our resources database.

			Note : as the product of a process can be also used as a resource for the next process or a fuel for a vehicle. We are using the term resource for any materials or source of energy. Therefore in GREET.net '''Coal''', '''Electricity''', '''Sun''' or '''Ammonia''' will all be in the Resources Database.

	===Define Processes===		===Define Processes===
			''See more details for [[Process Editors]]''

	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===

Ddieffenthaler: /* Create a Pathway */

2012-01-11T16:14:04Z

Create a Pathway

← Older revision		Revision as of 16:14, January 11, 2012
Line 8:		Line 8:

	===Define Resources===		===Define Resources===
	{{details\|Resources Editor}}		''See more details for [[Resources Editor]]''

	===Define Processes===		===Define Processes===
	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===

← Older revision		Revision as of 16:30, January 17, 2012
Line 1:		Line 1:
	==Create a Pathway==		==Create a Pathway==

	In order to create a pathway in GREET.net it is necessary to know :		In order to create a pathway in GREET.net it is necessary to know:
	* What Processes are involved in the pathway, they can be either stationary or transportation processes		* What Processes are involved in the pathway, they can be either stationary or transportation processes
	* What Resources, Intermediate Materials or Energies involved in the pathway		* What Resources, Intermediate Materials, or Energies are involved in the pathway

	Once this is ~~know~~ we are going to check first that the database contains the necessary information for the resources and intermediate materials. If some are missing they will be added using the Resource Editor. In a second time the processes will be created. When the processes are all defined in the database the pathway can be ~~build~~ by assembling processes together.		Once this is known we are going to check first that the database contains the necessary information for the resources and intermediate materials. If some are missing they will be added using the Resource Editor. In a second time the processes will be created. When the processes are all defined in the database the pathway can be built by assembling processes together.

	===Define Resources===		===Define Resources===
Line 12:		Line 12:
	In order to link all the processes together, resources and products for each of them needs to be entered in the database. Usually we define a name and some physical properties if they apply like heating values or carbon and sulfur ratios. Those resources will be used to define the Inputs of a process and their Products. A simple example could be a coal electric plant which uses '''Coal''' as an input and produces '''Electricity'''. '''Coal''' and '''Electricity''' needs to be defined in our resources database.		In order to link all the processes together, resources and products for each of them needs to be entered in the database. Usually we define a name and some physical properties if they apply like heating values or carbon and sulfur ratios. Those resources will be used to define the Inputs of a process and their Products. A simple example could be a coal electric plant which uses '''Coal''' as an input and produces '''Electricity'''. '''Coal''' and '''Electricity''' needs to be defined in our resources database.

	Note : as the product of a process can be ~~also~~ used as a resource for the next process or a fuel for a vehicle. We are using the term resource for any materials or source of energy. Therefore in GREET.net '''Coal''', '''Electricity''', '''Sun''' or '''Ammonia''' will all be in the Resources Database.		Note: as the product of a process can also be used as a resource for the next process or a fuel for a vehicle. We are using the term resource for any materials or source of energy. Therefore in GREET.net '''Coal''', '''Electricity''', '''Sun''' or '''Ammonia''' will all be in the Resources Database.

	===Define Processes===		===Define Processes===
	''See more details for [[Process Editors]]''		''See more details for [[Process Editors]]''

	In GREET two major types of processes can be defined : Stationary Processes and Transportation Processes. The ~~actual~~ database contains most of the processes used in GREET 1.8d_0, so if the necessary processes for that pathway are already in the database, there is no need to create new ones.		In GREET two major types of processes can be defined: Stationary Processes and Transportation Processes. The database contains most of the processes used in GREET 1.8d_0, so if the necessary processes for that pathway are already in the database, there is no need to create new ones.

	If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.		If you do need to create new processes which are not already in the database, you will have to use the [[Process Editors]] and make your own. Once saved they will be available for pathway building.
Line 23:		Line 23:
	===Build the Pathway using the Pathway Editor===		===Build the Pathway using the Pathway Editor===
	[[File:pathway_editor.png\|300px\|thumb\|left\|Drag and dropping processes]]		[[File:pathway_editor.png\|300px\|thumb\|left\|Drag and dropping processes]]
	~~Editing~~ a pathway ~~have to~~ be ~~done~~ from the Data Editor form~~, then click~~ on the "Pathways" menu and "Add Pathway" this will open the pathway editor.		Adding a pathway can be accessed from the Data Editor form by clicking on the "Pathways" menu and then on "Add Pathway" this will open the pathway editor.

	As shown on the left the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes, which are located in the left column, will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.		As shown on the left the pathway editor is an empty sheet on which the user can drag and drop processes. The list of processes, which are located in the left column, will be updated automatically according to the current inputs/outputs of the pathway, and the places where a process can be drop are shown by green boxes on the pathway. Therefore building a pathway using existing processes is really easy, it's a matter of drag and dropping processes.
Line 29:		Line 29:
	[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]		[[File:feed_placement.png\|300px\|thumb\|right\|Drag and dropping a feed]]

	On the right side of the pathway editor, the feeds selection tab is shown .The different feeds available are shown on the right side after the panel ~~have~~ been expanded. Then as for processes it's just a matter of drag and dropping. The feed is used at the beginning of a pathway to replace a material Mix. Let's think about that case : you have a process which ~~have~~ as an input Bituminous Coal, but this Bituminous Coal might come from different pathways. Instead of drawing those different pathways again and again, we are going to replace them with a Feed box, which is a Mix of the results from those pathways.		On the right side of the pathway editor, the feeds selection tab is shown. The different feeds available are shown on the right side after the panel has been expanded. Then as for processes it's just a matter of drag and dropping. The feed is used at the beginning of a pathway to replace a material Mix. Let's think about that case: you have a process which has as an input Bituminous Coal, but this Bituminous Coal might come from different pathways. Instead of drawing those different pathways again and again, we are going to replace them with a Feed box, which is a Mix of the results from those pathways.

	When an issue is detected after a process has been dropped a message appears at the top of the pathway editor~~, in~~ the case of the screenshot on the right, we dropped a process which have inputs from previous, but in the current pathway, there is nothing before. So to solve this conflict we can either drop a process before, which have for output Bituminous Coal in this example, or drop a "feed" which represent a material Source. In this case the material Source contains a single pathway to create bituminous coal, we are using this to feed out process.		When an issue is detected after a process has been dropped a message appears at the top of the pathway editor. In the case of the screenshot on the right, we dropped a process which have inputs from previous, but in the current pathway there is nothing before that process. So to solve this conflict we can either drop a process before, which have for output Bituminous Coal in this example, or drop a "feed" which represent a material Source. In this case the material Source contains a single pathway to create bituminous coal, we are using this to feed out process.

	Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.		Then to save the process, a name is required. The Hidden option will hide or not this pathway from the GUI, this option can be used for some legacy pathways that we still want to be in the database but not shown to not overwhelm the GUI. The ID is what will be used internally to refer to this pathway, therefore this number is automatically generated by the GUI. Notes can be used to give some indications about the pathway and are saved in the database.