https://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&feed=atom&action=historyTalk:Open Models - Revision history2024-03-28T10:17:10ZRevision history for this page on the wikiMediaWiki 1.19.7https://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7643&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T19:47:46Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 19:47, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 11:</td>
<td colspan="2" class="diff-lineno">Line 11:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">::Okay, here is the answer. The form help (now) says: "Is the model able to be used for large-scale scenario analysis with hundreds or thousands of different parameter sets being investigated?" <span class="userid-350 comment-signature" timestamp="20161208194746">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 20:47 (CET)</span></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/><br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/><br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/><br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/><br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/><br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/><br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/><br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/><br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/><br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/><br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/><br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/><br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/><br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/><br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/><br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/><br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/><br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/><br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7634&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:55:09Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:55, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<ins class="diffchange diffchange-inline"><br/></ins><br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<ins class="diffchange diffchange-inline"><br/></ins><br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<ins class="diffchange diffchange-inline"><br/></ins><br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<ins class="diffchange diffchange-inline"><br/></ins><br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<ins class="diffchange diffchange-inline"><br/></ins><br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<ins class="diffchange diffchange-inline"><br/></ins><br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<ins class="diffchange diffchange-inline"><br/></ins><br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<ins class="diffchange diffchange-inline"><br/></ins><br/>* a new '''Property:Final release date''' to record the abandonment of a project<ins class="diffchange diffchange-inline"><br/></ins><br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7632&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:54:12Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:54, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/><br/>Some further questions and suggestions for improvement:<br/><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/><br/>In addition:<br/><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/><br/>The AC/DC load flow naming issue:<br/><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<ins class="diffchange diffchange-inline"><br/></ins><br/>'''References'''<br/><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7629&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:53:46Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:53, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<ins class="diffchange diffchange-inline"><br/></ins><br/>Some further questions and suggestions for improvement:<ins class="diffchange diffchange-inline"><br/></ins><br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<ins class="diffchange diffchange-inline"><br/></ins><br/>In addition:<ins class="diffchange diffchange-inline"><br/></ins><br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<ins class="diffchange diffchange-inline"><br/></ins><br/>The AC/DC load flow naming issue:<ins class="diffchange diffchange-inline"><br/></ins><br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<ins class="diffchange diffchange-inline"><br/></ins><br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7628&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:53:00Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:53, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] <del class="diffchange diffchange-inline">&lt;span style="font-size:85%"&gt;</del>(PDF)<del class="diffchange diffchange-inline">&lt;/span&gt;</del>. Zürich, Switzerland: ETH. Retrieved <del class="diffchange diffchange-inline">&lt;span class="nowrap"&gt;</del>2016-12-08<del class="diffchange diffchange-inline">&lt;/span&gt;</del>.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>* should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>* under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>* the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>* the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>* the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>* the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>* the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>* a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>* a new '''Property:Final release date''' to record the abandonment of a project<br/>* a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>* perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7625&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:52:16Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:52, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the Planned to open up in the future flag so that this flag is greyed out when Open Source licensed is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>should add: Modeled commodities (Other): Supercritical CO2 (for CCS technologies)<br/>under Transfer (Heat): does heat transmission (that is, long-distance heat transport) make any sense?<br/>the Network coverage fields AC load flow and DC load flow are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>the various Property:* pages should explain the meaning of their field at the very top of the page<br/>the Property:Math modeltype should also accept the following values: accounting, hybrid, and game theory. And possibly energy-economy or economic equilibrium or general equilibrium (for top-down models, of which there are none so far), and also input/output, econometric, and integrated assessment (for completeness, more than anything else, at this point)<br/>the Property:License need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The Property:License page can then contain a list of expansions<br/>the Property:Model source public could be renamed Property:Distribution and contain the values: git repository, svn repository (though subversion is not common), anonymous download, registration, and by invitation (meaning that new project members will be screened and approved)<br/>a new Property:First release date to record the year or full date of first public release (this would also provide interesting historical information)<br/>a new Property:Final release date to record the abandonment of a project<br/>a new Property:Status which accepts: planned, active, unmaintained, and discontinued (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>perhaps the license information should be split into Property:Code license and Property:Data license to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is analogous to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>References<br/>Andersson, Göran (2008). Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the <ins class="diffchange diffchange-inline">'''</ins>Planned to open up in the future<ins class="diffchange diffchange-inline">''' </ins>flag so that this flag is greyed out when <ins class="diffchange diffchange-inline">'''</ins>Open Source licensed<ins class="diffchange diffchange-inline">''' </ins>is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/><ins class="diffchange diffchange-inline">* </ins>should add: <ins class="diffchange diffchange-inline">'''</ins>Modeled commodities (Other): Supercritical CO2<ins class="diffchange diffchange-inline">''' </ins>(for CCS technologies)<br/><ins class="diffchange diffchange-inline">* </ins>under <ins class="diffchange diffchange-inline">'''</ins>Transfer (Heat)<ins class="diffchange diffchange-inline">'''</ins>: does heat <ins class="diffchange diffchange-inline">''</ins>transmission<ins class="diffchange diffchange-inline">'' </ins>(that is, long-distance heat transport) make any sense?<br/><ins class="diffchange diffchange-inline">* </ins>the <ins class="diffchange diffchange-inline">'''</ins>Network coverage<ins class="diffchange diffchange-inline">''' </ins>fields <ins class="diffchange diffchange-inline">'''</ins>AC load flow<ins class="diffchange diffchange-inline">''' </ins>and <ins class="diffchange diffchange-inline">'''</ins>DC load flow<ins class="diffchange diffchange-inline">''' </ins>are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/><ins class="diffchange diffchange-inline">* </ins>the various <ins class="diffchange diffchange-inline">'''</ins>Property:*<ins class="diffchange diffchange-inline">''' </ins>pages should explain the meaning of their field at the very top of the page<br/><ins class="diffchange diffchange-inline">* </ins>the <ins class="diffchange diffchange-inline">'''</ins>Property:Math modeltype<ins class="diffchange diffchange-inline">''' </ins>should also accept the following values: <ins class="diffchange diffchange-inline">''</ins>accounting<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>hybrid<ins class="diffchange diffchange-inline">''</ins>, and <ins class="diffchange diffchange-inline">''</ins>game theory<ins class="diffchange diffchange-inline">''</ins>. And possibly <ins class="diffchange diffchange-inline">''</ins>energy-economy<ins class="diffchange diffchange-inline">'' </ins>or <ins class="diffchange diffchange-inline">''</ins>economic equilibrium<ins class="diffchange diffchange-inline">'' </ins>or <ins class="diffchange diffchange-inline">''</ins>general equilibrium<ins class="diffchange diffchange-inline">'' </ins>(for top-down models, of which there are none so far), and also <ins class="diffchange diffchange-inline">''</ins>input/output<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>econometric<ins class="diffchange diffchange-inline">''</ins>, and <ins class="diffchange diffchange-inline">''</ins>integrated assessment<ins class="diffchange diffchange-inline">'' </ins>(for completeness, more than anything else, at this point)<br/><ins class="diffchange diffchange-inline">* </ins>the <ins class="diffchange diffchange-inline">'''</ins>Property:License<ins class="diffchange diffchange-inline">''' </ins>need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The <ins class="diffchange diffchange-inline">'''</ins>Property:License<ins class="diffchange diffchange-inline">''' </ins>page can then contain a list of expansions<br/><ins class="diffchange diffchange-inline">* </ins>the <ins class="diffchange diffchange-inline">'''</ins>Property:Model source public<ins class="diffchange diffchange-inline">''' </ins>could be renamed <ins class="diffchange diffchange-inline">'''</ins>Property:Distribution<ins class="diffchange diffchange-inline">''' </ins>and contain the values: <ins class="diffchange diffchange-inline">''</ins>git repository<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>svn repository<ins class="diffchange diffchange-inline">'' </ins>(though subversion is not common), <ins class="diffchange diffchange-inline">''</ins>anonymous download<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>registration<ins class="diffchange diffchange-inline">''</ins>, and <ins class="diffchange diffchange-inline">''</ins>by invitation<ins class="diffchange diffchange-inline">'' </ins>(meaning that new project members will be screened and approved)<br/><ins class="diffchange diffchange-inline">* </ins>a new <ins class="diffchange diffchange-inline">'''</ins>Property:First release date<ins class="diffchange diffchange-inline">''' </ins>to record the year or full date of first public release (this would also provide interesting historical information)<br/><ins class="diffchange diffchange-inline">* </ins>a new <ins class="diffchange diffchange-inline">'''</ins>Property:Final release date<ins class="diffchange diffchange-inline">''' </ins>to record the abandonment of a project<br/><ins class="diffchange diffchange-inline">* </ins>a new <ins class="diffchange diffchange-inline">'''</ins>Property:Status<ins class="diffchange diffchange-inline">''' </ins>which accepts: <ins class="diffchange diffchange-inline">''</ins>planned<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>active<ins class="diffchange diffchange-inline">''</ins>, <ins class="diffchange diffchange-inline">''</ins>unmaintained<ins class="diffchange diffchange-inline">''</ins>, and <ins class="diffchange diffchange-inline">''</ins>discontinued<ins class="diffchange diffchange-inline">'' </ins>(this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/><ins class="diffchange diffchange-inline">* </ins>perhaps the license information should be split into <ins class="diffchange diffchange-inline">'''</ins>Property:Code license<ins class="diffchange diffchange-inline">''' </ins>and <ins class="diffchange diffchange-inline">'''</ins>Property:Data license<ins class="diffchange diffchange-inline">''' </ins>to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is <ins class="diffchange diffchange-inline">''</ins>analogous<ins class="diffchange diffchange-inline">'' </ins>to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><ins class="diffchange diffchange-inline">'''</ins>References<ins class="diffchange diffchange-inline">'''</ins><br/>Andersson, Göran (2008). <ins class="diffchange diffchange-inline">[http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf </ins>Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability<ins class="diffchange diffchange-inline">] &lt;span style="font-size:85%"&gt;</ins>(PDF)<ins class="diffchange diffchange-inline">&lt;/span&gt;</ins>. Zürich, Switzerland: ETH. Retrieved <ins class="diffchange diffchange-inline">&lt;span class="nowrap"&gt;</ins>2016-12-08<ins class="diffchange diffchange-inline">&lt;/span&gt;</ins>.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7623&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:51:01Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:51, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 12:</td>
<td colspan="2" class="diff-lineno">Line 12:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Suggestions==</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline"><br/></del>After offline discussions with Ingmar, I am going to edit the logic behind the <del class="diffchange diffchange-inline">'''</del>Planned to open up in the future<del class="diffchange diffchange-inline">''' </del>flag so that this flag is greyed out when <del class="diffchange diffchange-inline">'''</del>Open Source licensed<del class="diffchange diffchange-inline">''' </del>is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/><del class="diffchange diffchange-inline">*</del>should add: <del class="diffchange diffchange-inline">'''</del>Modeled commodities (Other): Supercritical CO2<del class="diffchange diffchange-inline">''' </del>(for CCS technologies)<br/><del class="diffchange diffchange-inline">*</del>under <del class="diffchange diffchange-inline">'''</del>Transfer (Heat)<del class="diffchange diffchange-inline">'''</del>: does heat <del class="diffchange diffchange-inline">''</del>transmission<del class="diffchange diffchange-inline">'' </del>(that is, long-distance heat transport) make any sense?<br/><del class="diffchange diffchange-inline">*</del>the <del class="diffchange diffchange-inline">'''</del>Network coverage<del class="diffchange diffchange-inline">''' </del>fields <del class="diffchange diffchange-inline">'''</del>AC load flow<del class="diffchange diffchange-inline">''' </del>and <del class="diffchange diffchange-inline">'''</del>DC load flow<del class="diffchange diffchange-inline">''' </del>are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/><del class="diffchange diffchange-inline">*</del>the various <del class="diffchange diffchange-inline">'''</del>Property:*<del class="diffchange diffchange-inline">''' </del>pages should explain the meaning of their field at the very top of the page<br/><del class="diffchange diffchange-inline">*</del>the <del class="diffchange diffchange-inline">'''</del>Property:Math modeltype<del class="diffchange diffchange-inline">''' </del>should also accept the following values: <del class="diffchange diffchange-inline">''</del>accounting<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>hybrid<del class="diffchange diffchange-inline">''</del>, and <del class="diffchange diffchange-inline">''</del>game theory<del class="diffchange diffchange-inline">''</del>. And possibly <del class="diffchange diffchange-inline">''</del>energy-economy<del class="diffchange diffchange-inline">'' </del>or <del class="diffchange diffchange-inline">''</del>economic equilibrium<del class="diffchange diffchange-inline">'' </del>or <del class="diffchange diffchange-inline">''</del>general equilibrium<del class="diffchange diffchange-inline">'' </del>(for top-down models, of which there are none so far), and also <del class="diffchange diffchange-inline">''</del>input/output<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>econometric<del class="diffchange diffchange-inline">''</del>, and <del class="diffchange diffchange-inline">''</del>integrated assessment<del class="diffchange diffchange-inline">'' </del>(for completeness, more than anything else, at this point)<br/><del class="diffchange diffchange-inline">*</del>the <del class="diffchange diffchange-inline">'''</del>Property:License<del class="diffchange diffchange-inline">''' </del>need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The <del class="diffchange diffchange-inline">'''</del>Property:License<del class="diffchange diffchange-inline">''' </del>page can then contain a list of expansions<br/><del class="diffchange diffchange-inline">*</del>the <del class="diffchange diffchange-inline">'''</del>Property:Model source public<del class="diffchange diffchange-inline">''' </del>could be renamed <del class="diffchange diffchange-inline">'''</del>Property:Distribution<del class="diffchange diffchange-inline">''' </del>and contain the values: <del class="diffchange diffchange-inline">''</del>git repository<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>svn repository<del class="diffchange diffchange-inline">'' </del>(though subversion is not common), <del class="diffchange diffchange-inline">''</del>anonymous download<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>registration<del class="diffchange diffchange-inline">''</del>, and <del class="diffchange diffchange-inline">''</del>by invitation<del class="diffchange diffchange-inline">'' </del>(meaning that new project members will be screened and approved)<br/><del class="diffchange diffchange-inline">*</del>a new <del class="diffchange diffchange-inline">'''</del>Property:First release date<del class="diffchange diffchange-inline">''' </del>to record the year or full date of first public release (this would also provide interesting historical information)<br/><del class="diffchange diffchange-inline">*</del>a new <del class="diffchange diffchange-inline">'''</del>Property:Final release date<del class="diffchange diffchange-inline">''' </del>to record the abandonment of a project<br/><del class="diffchange diffchange-inline">*</del>a new <del class="diffchange diffchange-inline">'''</del>Property:Status<del class="diffchange diffchange-inline">''' </del>which accepts: <del class="diffchange diffchange-inline">''</del>planned<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>active<del class="diffchange diffchange-inline">''</del>, <del class="diffchange diffchange-inline">''</del>unmaintained<del class="diffchange diffchange-inline">''</del>, and <del class="diffchange diffchange-inline">''</del>discontinued<del class="diffchange diffchange-inline">'' </del>(this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/><del class="diffchange diffchange-inline">*</del>perhaps the license information should be split into <del class="diffchange diffchange-inline">'''</del>Property:Code license<del class="diffchange diffchange-inline">''' </del>and <del class="diffchange diffchange-inline">'''</del>Property:Data license<del class="diffchange diffchange-inline">''' </del>to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is <del class="diffchange diffchange-inline">''</del>analogous<del class="diffchange diffchange-inline">'' </del>to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/><del class="diffchange diffchange-inline">'''</del>References<del class="diffchange diffchange-inline">'''</del><br/>Andersson, Göran (2008). <del class="diffchange diffchange-inline">[http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf </del>Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability<del class="diffchange diffchange-inline">] &lt;span style="font-size:85%"&gt;</del>(PDF)<del class="diffchange diffchange-inline">&lt;/span&gt;</del>. Zürich, Switzerland: ETH. Retrieved <del class="diffchange diffchange-inline">&lt;span class="nowrap"&gt;</del>2016-12-08<del class="diffchange diffchange-inline">&lt;/span&gt;</del>. <span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>After offline discussions with Ingmar, I am going to edit the logic behind the Planned to open up in the future flag so that this flag is greyed out when Open Source licensed is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>should add: Modeled commodities (Other): Supercritical CO2 (for CCS technologies)<br/>under Transfer (Heat): does heat transmission (that is, long-distance heat transport) make any sense?<br/>the Network coverage fields AC load flow and DC load flow are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>the various Property:* pages should explain the meaning of their field at the very top of the page<br/>the Property:Math modeltype should also accept the following values: accounting, hybrid, and game theory. And possibly energy-economy or economic equilibrium or general equilibrium (for top-down models, of which there are none so far), and also input/output, econometric, and integrated assessment (for completeness, more than anything else, at this point)<br/>the Property:License need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The Property:License page can then contain a list of expansions<br/>the Property:Model source public could be renamed Property:Distribution and contain the values: git repository, svn repository (though subversion is not common), anonymous download, registration, and by invitation (meaning that new project members will be screened and approved)<br/>a new Property:First release date to record the year or full date of first public release (this would also provide interesting historical information)<br/>a new Property:Final release date to record the abandonment of a project<br/>a new Property:Status which accepts: planned, active, unmaintained, and discontinued (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>perhaps the license information should be split into Property:Code license and Property:Data license to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is analogous to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>References<br/>Andersson, Göran (2008). Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability (PDF). Zürich, Switzerland: ETH. Retrieved 2016-12-08.<span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7620&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T12:50:04Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:50, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 11:</td>
<td colspan="2" class="diff-lineno">Line 11:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning that new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">==Suggestions==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"><br/>After offline discussions with Ingmar, I am going to edit the logic behind the '''Planned to open up in the future''' flag so that this flag is greyed out when '''Open Source licensed''' is set to true. Otherwise the flag is rather meaningless when a permissive license like the MIT license has already been checked.<br/>Some further questions and suggestions for improvement:<br/>*should add: '''Modeled commodities (Other): Supercritical CO2''' (for CCS technologies)<br/>*under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance heat transport) make any sense?<br/>*the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very often (and confusingly) termed DC load flow (see end of message for details) — so the associated help message should make the distinction crystal clear<br/>*the various '''Property:*''' pages should explain the meaning of their field at the very top of the page<br/>*the '''Property:Math modeltype''' should also accept the following values: ''accounting'', ''hybrid'', and ''game theory''. And possibly ''energy-economy'' or ''economic equilibrium'' or ''general equilibrium'' (for top-down models, of which there are none so far), and also ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point)<br/>*the '''Property:License''' need only record the abbreviated form of the license where it is well known, for example: GPLv2 and not GNU General Public License version 2.0. The '''Property:License''' page can then contain a list of expansions<br/>*the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (though subversion is not common), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that new project members will be screened and approved)<br/>*a new '''Property:First release date''' to record the year or full date of first public release (this would also provide interesting historical information)<br/>*a new '''Property:Final release date''' to record the abandonment of a project<br/>*a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive and which have been abandoned)<br/>In addition:<br/>*perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (often CC BY 4.0)<br/>The AC/DC load flow naming issue:<br/>Andersson (2008) on page&nbsp;59 explains that the active power flow equation for fixed-frequency AC power is ''analogous'' to Ohms law applied to a resistor carrying DC current. Hence this form of AC power analysis is regularly referred to as DC load flow analysis.<br/>'''References'''<br/>Andersson, Göran (2008). [http://www.eeh.ee.ethz.ch/uploads/tx_ethstudies/modelling_hs08_script_02.pdf Modelling and analysis of electric power systems: power flow analysis fault analysis power systems dynamics and stability] &lt;span style="font-size:85%"&gt;(PDF)&lt;/span&gt;. Zürich, Switzerland: ETH. Retrieved &lt;span class="nowrap"&gt;2016-12-08&lt;/span&gt;. <span class="userid-350 comment-signature" timestamp="20161208125004">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 13:50 (CET)</span></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7602&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T11:57:15Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 11:57, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 10:</td>
<td colspan="2" class="diff-lineno">Line 10:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Field "Is suited for many scenarios" in Section "Overview of models by purpose, scope and modelling type"==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Field "Is suited for many scenarios" in Section "Overview of models by purpose, scope and modelling type"==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning <del class="diffchange diffchange-inline">the </del>new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up. <span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>:I read that as suited in terms of data preparation, meaning <ins class="diffchange diffchange-inline">that </ins>new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up.<span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrisonhttps://wiki.openmod-initiative.org/index.php?title=Talk:Open_Models&diff=7599&oldid=prevRobbie Morrison: <nice-discussions-summary>2016-12-08T11:56:33Z<p><nice-discussions-summary></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 11:56, 8 December 2016</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 10:</td>
<td colspan="2" class="diff-lineno">Line 10:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Field "Is suited for many scenarios" in Section "Overview of models by purpose, scope and modelling type"==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>==Field "Is suited for many scenarios" in Section "Overview of models by purpose, scope and modelling type"==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>I am just wondering what is meant by this field.<br/>Suited in terms of runtime?<br/>Best<br/>Cord<br/> <span class="userid-47 comment-signature" timestamp="20161006064509">[[User:Cord Kaldemeyer|Cord Kaldemeyer]]  6 October 2016, 08:45 (CEST)</span></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">:I read that as suited in terms of data preparation, meaning the new scenarios could be created from a reference scenaro by ''difference''. This needs to be cleared up. <span class="userid-350 comment-signature" timestamp="20161208115633">[[User:Robbie Morrison|Robbie Morrison]]  8 December 2016, 12:56 (CET)</span></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span class="NiceDiscussions END"></span></div></div></td></tr>
</table>Robbie Morrison