User:Robbie Morrison/sandbox
From wiki.openmod-initiative.org
< User:Robbie Morrison(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| | + | |
| | + | Future suggestions: |
| | + | |
| | + | *should add: '''Modeled energy carriers (Other): Supercritical CO2''' (for CCS technologies) |
| | + | *''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 ''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) |
| | | | |
| | Some suggestions: | | Some suggestions: |
| Line 12: |
Line 18: |
| | | | |
| | *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). | | *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). |
| | + | |
| | + | AC/DC load flow: |
Revision as of 09:44, 8 December 2016
Future suggestions:
- should add: Modeled energy carriers (Other): Supercritical CO2 (for CCS technologies)
- 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 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)
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: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).
- 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:Status which accepts: planned, active, unmaintained, and discontinued (this would allow users to see which projects are alive or not).
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).
AC/DC load flow:
