Giter Club home page Giter Club logo

openenergyplatform / oeplatform Goto Github PK

View Code? Open in Web Editor NEW
61.0 12.0 19.0 149.11 MB

Repository for the code of the Open Energy Platform (OEP) website. The OEP provides an interface to the Open Energy Family

Home Page: http://openenergyplatform.org/

License: GNU Affero General Public License v3.0

Python 44.17% CSS 1.88% HTML 20.40% JavaScript 24.33% Shell 0.08% Mako 0.02% Dockerfile 0.04% SCSS 9.06% Less 0.01%
oep django rest-api energy database open-energy-family open-data

oeplatform's Introduction

Workflow Status-Badge & Link
Automated tests Automated tests
Docs Documentation Status

OpenEnergyPlatform

Open Energy Family - Open Energy Platform (OEP)

Repository for the code of the Open Energy Platform (OEP) website https://openenergy-platform.org/. This repository does not contain data, for data access please consult this page

License / Copyright

This repository is licensed under GNU Affero General Public License v3.0 (AGPL-3.0)

Installation & Setup

Follow the detailed installation guide.

Development & Code contribution

Please read carefully the CONTRIBUTING.md file before you start contributing!

For further information visit our development & contribution guide

oeplatform's People

Contributors

4lm avatar adelmemariani avatar bachibouzouk avatar bmlancien avatar christian-rli avatar chrwm avatar darynarli avatar dependabot[bot] avatar ebroda avatar edithak avatar gnn avatar han-f avatar henhuy avatar jh-rli avatar johannwagner avatar kirannbhavaraju avatar klarareder avatar l-emele avatar ludee avatar mfinkendei avatar mglauer avatar mjazimm avatar pajot avatar quentinpeyras avatar smutyala18 avatar stap-m avatar steull avatar thsstll avatar tom-heimbrodt avatar wingechr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

oeplatform's Issues

[Factsheets] MF openness, source code available

open source = yes -> source code available = yes:

  • GitHub checkbox appears
  • Rename "link to source code" as "Access to source code", Info text: "Where is the source code available (e.g. link, email address)?"; type: not link, but text field.

UML diagram validators

We are looking for a tool that validates UML diagrams regarding correctness and conformance. This tool should be able to handle the XMI data format w.r.t. to recent standards.

Linked to #60

Translation from python code to UML

There should be a tool that translates existing python code to UML diagramms (especially class diagrams). The main issue is that python is not type secure but python 3.5 introduced type hints. These might be used to enhance the performance. Also, I do not know any tool that produces a valid xmi document according to recent standards. XMI is the standard exchange format for UML, though.

[Factsheets] SF - general information - tools

There are two fields labelled as "tools". The second one seems to be meant as a "other" field and should only appear, when "other" is selected in the drop down menu of the first field. The options of the first field are still dummy data and seem to be supposed to include automatically the list of all models for which a fact sheet is available.

Do we want to allow the selection of more than one tool? See also Issue #55 .

larger text fields

Please, provide larger text fields, especially, when we expect larger texts (for instance "Primary Purpose" and "Primary Outputs", "User behaviour and demand side management", "Comment on geographic (spatial) resolution", "Short description of mathematical model class"). It is not very user-friendly, when the user cannot see her/his text completely at one glance.

[Factsheets] Fact sheets: References

Citation reference and References to reports produced using the model

  • larger text fields
  • plus button for more than one reference, opening an additional text field
  • Citation DOI fields next to each field

Citation reference info text
"Publication(s) to be referenced when citing the model; e.g. Doe, John (2014), An electricity market model for Europe, Journal of Modelling Sciences, Vol 10, Issue 80."

Larger text fields also for all other points.

Larger scale usage

  • MF: rename to "Model usage"; info text: Who uses the model?
  • FF: rename to "Framework" usage; info text: Who uses the framework?

validation
options: peer-reviewed, outcomes cross checked with other models or data, other + text

[Factsheets] submitting parts of the fact sheets

I would expect a message like "changes / fact sheet successfully saved", after clicking on submit.

Instead of being brought to the next tab, you find yourself on the first tab "general information" after submitting a part.

When does the model fact sheet appear in the list of model fact sheets. I am quite sure that it did not appear directly after submitting the first parts of the model fact sheets.

After submitting the Mathematical properties, the server error 500 occurred. The fact sheet I was working on occurred in the list of model fact sheets (but I cannot open it "server error"). When I tried to reproduce the server error by clicking on the submit button in the Mathematical properties tab, I got back to the General Information tab of the fact sheet creating page telling me "Basic factsheet [ TWO WORDS] with this Name [SHOULD BE LOWERCASE] already exists." In my opinion that messages should tell me more. Are my latest changes lost? How do I go on (e.g. editing the existing fact sheet)?

MF Coverage

There are a few points to improve the coverage section of the model fact sheet:

  • the headlines grouping the options of "Modelled energy carriers (primary energy carriers)", "Modelled technologies: components for generation or conversion", "Modelled technologies: components for storage"
  • the options of "Modelled technologies: components for transfer, infrastructure or grid" were specified unclear: electricity (transmission; distribution); heat (transmission; distribution); gas (transmission; distribution); Please, include the headings.
  • Network coverage / representation (electrical grid): option "net transfer capacities" is missing
  • "Changes in efficiency" text field is totally missing
  • Market models was meant to be a check box, when yes: two options: fundamental model; stochastic model
  • missing info text for "Geographical coverage": "What regions are covered? Please, list the regions covered by the model. Leave blank, if the model and data are not limited to a specific region.
    Example input: USA, Canada, Mexico"
  • Time resolution was accidentally called "Network coverage / representation (electrical grid)"
  • "Additional dimensions (sector)": Please, delete "(sector)" from the heading. the text fields have unnecessary / unclear labels. Please, delete / replace them.

Example Database

Developers that clone our repository do not clone the underlying django database (as intended). These local copies can not fill pages with text and can not be designed as intended. We should provide example data for our pages.

MF; Mathematical properties

There are different approaches to handle empty "other texts". Can there be found a consistent way?

  • Model class is in the final data sheet divided in three parts (optimisation, simulation, other with a check mark). Please, add the headings "optimisation", "simulation" in the form.
  • In the list of the "Mathematical objective" appears "mathematical objective other text". That is not very beautiful.
  • In "Approach to uncertainty" appears "Other".

[Factsheets] MF model integration

Integration with other models and Integration of other models:

Please, make a check box and a larger text field, appearing when check box is activated.

Data input should support foreign keys

The current input scheme assumes that each a table draws the data directly from the table. The following is currently not possible:

id name
1 Marc
id job employee
2 knitting Marc

Suppose the following input data: "Marc is knitting."

This "Marc" could not be linked to the id 1 with the current interface.
Solution:
Add a 'link to prim. key where name = "Marc"' option to the mapping page of data-edit

Scenario Fact Sheet, several bugs

Form:

  • In the form the section "results" is accidentally named "references".
  • In the form in section Assumptions the "Potential energy saving" is implemented twice. Please, use plural in the first: "Potential energy savingS". The second one should be labelled with "emission reductions".
  • I cannot find the question " Name of the scenario" in the form. Please, consider that in connection to #59.

Sheet:

  • "Name of the study" should not be part of Assumptions. The same is true for "Name of the Scenario", but under consideration of #59.
  • The number of labels in the Assumption section include accidentally the word "kind".

fact sheets only accept links with http://

On the fact sheet creating page only links with http:// in the beginning are accepted. That might annoy the users. Please, change that or warn users in the info text.

Split scenario Factsheets

Currently, the section "Basic Information" contains informations regarding the study that contains the scenario. Studies can contain several scenarios.

Hence, we should remove the fields in basic information and put them into a seperate fact sheet.
On the form's "General Information" tab users can select from existing studies or select to enter a new one. If they do so, after submitting the form they are redirected to a new form for the new study.

The actual fact sheet should look like it does now, but fetch the "General Information" from the new study table.

@EvaWie: Are there other fields that should be part of the study?

MF; Mathematical properties; objective other text

Ticking the "other option" in a former saved fact sheet, Mathematical objective other text says "false".

The fact sheet cannot be saved or the following error occurs even when the "other option" is not tick anymore.
"Mathematical objective other text: This field is required."

Annoyed by the info text question mark

Clicking on the blue info text question mark does not show you the expected information, but brings you to the top of the page. I personally dislike that.

[Factsheets] FF Design and Interfaces; Supported model types

  • The point "Supported model types" was accidentally named "Mathematical model".
  • The selection should be options and not a drop-down menu.
  • Should this selection be in general information?
  • In the ready fact sheets appears suddenly "Support / Community / Forum" instead.

Fix percentage fields

There are several issues with "potential energy savings" etc in the scenario fact sheets :

  • Input fields should hide if "not estimated" is selected
  • If values other than "not estimated" are selected, both integer fields become necessary

Fact sheets logo upload

  • The logo upload does not work. Please, specify in the info text, what kind of pictures can be uploaded.

[Factsheets] Several changes

  • Model / Framework / scenario fact sheet; general information: Rename "Institution(s)" as "Partner(s)"; info text: "Which organisations develop(ed) the model / framework / scenario?"
  • Model; model integration; "Input/output data file format": Please, separate Input and Output into two drop-down menus. Veto? They should not be mandatory.
  • (Move the "Primary Outputs" to the integration section, right before the "Output data file format".)
    Sorry, we changed our mind. Please, do not move it.
  • Model fact sheet: documentation quality stays a mandatory field, because it is a drop-down menu. The option "not available" needs to be added. Can the field be next to link to documentation.
  • "Additional software" will no longer be a mandatory field. Please, remember to delete the "*".
  • option to say when approximately it may become open source under the item 'planned to open up in the future' in the openness section (please, make a text field) Sorry, we changed our mind: Please, put it into mathematical properties.
  • There needs be added a check box: "Multi-regional model" in the coverage section . Info text: "Allows the model multi-regional modelling?"
  • Geographic (spatial) resolution info text: "What is the typical geographic resolution, the model works with?"

[Factsheets] fact sheets: several display errors

At different points in the sections "Coverage" and "Mathematical properties" the submitted fact sheet show "True" or an array of the word "True" instead of a check mark or a list of the selected options.

The label "framework yes text" should not appear in the fact sheet. If there is a text it should stand for itself (or give it a more beautiful name like name of the underlying framework). If there is no text, this line should not be part of the fact sheet.

The points "planned to open up in the future" and "costs" appear in the ready fact sheet of open source models, but can not be filled out in the form.

The "license other text" should not appear in the final fact sheet or it should be renamed. When choosing a licence from the list after choosing the "other option" and entering a name in the other field first, in the form the "other option" and the entered name disappear, but in the final fact sheet the name or the standard text "not jet decided" is displayed nevertheless and the selection is ignored (model and framework fact sheet).

As above the label "external optimizer yes text" should not appear.

Do we prefer a check box with yes-text for "Additional software"? Preventing people to write none / no etc. The field should not be mandatory (please, change that also in the framework fact sheet).

[Factsheets] Watch changes (on fact sheets)

Add watch function, so that the watcher of a certain fact sheets gets a notification mail, when the fact sheet has been changed. This function is meant to make the authors of a fact sheet / the developers of models or frameworks or scenarios aware of changes in "their" fact sheet.

Model fact sheet; Coverage

  • the headlines grouping the options of "Modelled energy carriers (primary energy carriers)", "Modelled technologies: components for generation or conversion", "Modelled technologies: components for storage" are missing
  • the options of "Modelled technologies: components for transfer, infrastructure or grid" were specified unclear: electricity (transmission; distribution); heat (transmission; distribution); gas (transmission; distribution): Please delete the words "Transfer electricity / gas /heat";
    The headings should not have a check box.

Implement Data Input

We need a form for input of new data on our platform. This form should adapt to the edited table and submit data to the "untested" database.

User Management

We need a user management for our platform. For starters each user
should be able to login and manage a profile that consists of his
name, mail-address (per default hidden) and his affiliation. Maybe we
will extend this profiles later.

Django seems to come with a package for user management:
django.contrib.auth.forms

[Factsheets] SF - general information - Technologies included

Some things went wrong here. The headings are missing and heat appears three times in the list.

The list was meant to look like this:
renewables (PV, wind, hydro, biomass, biogas, solar thermal, others); conventional generation (gas, coal, oil, liquid fuels, nuclear); CHP; networks (electricity, gas, heat); storages (battery, kinetic, CAES, PHS, chemical)

help text behave funny

Fields are class attributes of the corresponding model. Changes on one instance will be done on all. Find another way to change help texts on instances Energyframework.

[Factsheets] Fact sheets Documentation text fields

The text fields for the link to the documentations should not be mandatory - taking the case, where the documentation is not online available, into account. Please, make in the info text clear, that a link is expected.

The quality rating was meant to be located next to link and not underneath.

Too many mandatory fields

There are too many mandatory fields. That hinders users, who have to continue later, to save fact sheets, that are only partly filled out in parts.
Questions with options (and drop down menus?) should no longer be mandatory. Please, provide a default selection.

Fact Sheets: check boxes

Design / Layout: Please, make sure that the user easily sees, which check box belongs to which text.

open source licence to choose

Please, extent the list of open source licences:
for instance: MIT Licence, Apache Licence, GNU GPL Licence

The "other" text field should disappear when a licence for the list is chosen.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.