|
|
| Line 1: |
Line 1: |
| | | | |
| − | 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. | + | 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. |
| | | | |
| − | Some further questions and suggestions for inprovment: | + | Some further questions and suggestions for improvment: |
| | | | |
| | *should add: '''Modeled energy carriers (Other): Supercritical CO2''' (for CCS technologies) | | *should add: '''Modeled energy carriers (Other): Supercritical CO2''' (for CCS technologies) |
| − | *under '''Transfer (Heat)''': does heat transmission (that is, long-distance transport) make any sense? | + | *under '''Transfer (Heat)''': does heat ''transmission'' (that is, long-distance transport) make any sense? |
| − | *the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very confusingly termed DC load flow (see end of message for details) | + | *the '''Network coverage''' fields '''AC load flow''' and '''DC load flow''' are ambiguous: the basic AC load flow model is very confusingly termed DC load flow (see end of message for details) — so the associated help message should make this crystal clear |
| − | *the ''Not planned to open up further in the future'' indicator is a bit meaningless when a really permissive license like the MIT license has already been checked (some addition logic is perhaps required to suppress this flag)
| + | *the various '''Property:*''' pages should explain the meaning of the field at the very top of the page |
| − | | + | |
| − | Some suggestions:
| + | |
| − | | + | |
| − | *the various '''Property:*''' pages should explain the meaning of the field. Particularly obscure (for me anyway) is '''Property:Is suited for many scenarios'''. Does that mean that new scenarios can be defined by difference to a reference scenario? | + | |
| | *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), ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point). | | *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), ''input/output'', ''econometric'', and ''integrated assessment'' (for completeness, more than anything else, at this point). |
| | *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. | | *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. |
| − | *the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (not that I know of any projects using subversion), ''download'' (anonymous download that is), ''on application'' (meaning requires registration), and ''by invitation'' (meaning that applicants will be screened and approved). | + | *the '''Property:Model source public''' could be renamed '''Property:Distribution''' and contain the values: ''git repository'', ''svn repository'' (not that I know of any projects using subversion), ''anonymous download'', ''registration'', and ''by invitation'' (meaning that applicants will be screened and approved). |
| − | *a new '''Property:First''' release date to record the year or full date of first public release (this would provide interesting historical information) | + | *a new '''Property:First release date''' to record the year or full date of first public release (this would provide interesting historical information) |
| | + | *a new '''Property:Final release date''' to record the abandonment of a project |
| | *a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive or not). | | *a new '''Property:Status''' which accepts: ''planned'', ''active'', ''unmaintained'', and ''discontinued'' (this would allow users to see which projects are alive or not). |
| | | | |
| | In addition: | | In addition: |
| | | | |
| − | *maybe the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (say CC BY 4.0). | + | *perhaps the license information should be split into '''Property:Code license''' and '''Property:Data license''' to distinguish between the codebase (say GPLv3) and datasets (say CC BY 4.0). |
| | | | |
| − | AC/DC load flow naming issue: | + | The AC/DC load flow naming issue: |
| | | | |
| | Andersson (2008) on page 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 often referred to as DC load flow. | | Andersson (2008) on page 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 often referred to as DC load flow. |
| | | | |
| | 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] <span style="font-size:85%">(PDF)</span>. Zürich, Switzerland: ETH. Retrieved <span class="nowrap">2016-12-08</span>. | | 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] <span style="font-size:85%">(PDF)</span>. Zürich, Switzerland: ETH. Retrieved <span class="nowrap">2016-12-08</span>. |
Andersson (2008) on page 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 often referred to as DC load flow.
