Skip to content

Proofread RTD Getting started and landing page#871

Merged
Bachibouzouk merged 14 commits intodevfrom
fix/proof-RTD-intro
Apr 29, 2021
Merged

Proofread RTD Getting started and landing page#871
Bachibouzouk merged 14 commits intodevfrom
fix/proof-RTD-intro

Conversation

@Bachibouzouk
Copy link
Copy Markdown
Collaborator

@Bachibouzouk Bachibouzouk commented Apr 27, 2021

Changes proposed in this pull request:

  • proofread the index and the getting started part of RTD

The following steps were realized, as well (if applies):

  • For new functionalities: Explain in readthedocs
  • Update the CHANGELOG.md

For more information on how to contribute check the CONTRIBUTING.md.

@smartie2076
Copy link
Copy Markdown
Collaborator

Ah, did you not plan to create one changelog entry, in which we can list the RTD PR step by step?

@Bachibouzouk
Copy link
Copy Markdown
Collaborator Author

Ah, did you not plan to create one changelog entry, in which we can list the RTD PR step by step?

Yes but I am not done with the .rst file/this PR yet, I still have to go through the chapter Defining an energy system

@smartie2076
Copy link
Copy Markdown
Collaborator

Ah, did you not plan to create one changelog entry, in which we can list the RTD PR step by step?

Yes but I am not done with the .rst file/this PR yet, I still have to go through the chapter Defining an energy system

Ah, okay, I didnt see that it was a draft. Let me know when I should do the next review!

Copy link
Copy Markdown
Collaborator

@smartie2076 smartie2076 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! There are two issues where we need to check if a advertized function really works/does not work.

I am not sure how we want to deal with this - maybe if you find an issue remove the connected line, paste it into the existing issue with a line number, so that it can be changed when the issue is being solved.
If no issue exists (and a smoke test shows it does not work, or if the test should be implemented as a pytest), an issue can be created. We then use the wording that is more careful, and place the text of the advertized feature into the new issue.

@@ -0,0 +1,6 @@
.. _benchmarks_examples:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the plan to have more examples here, or to expand the examples?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can either have a section with multiple small examples here or just this one example detailed, then link to the input files of the other examples. I think the former is preferable, because we will never have time to draft a nice step by step description of all benchmark tests

| └── mvs_config.json


The name and location of the :code:`input_folder` is up to the user. The underlying structure and file names within this folder should not be altered.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exept for the file storage_01.csv which can have a freely defined name referenced in energyStorages.csv.

Time series: time_series folder
###############################
Some parameters value in the CSV/Json files are filenames. Those filenames correspond to files which must be present in the folder :code:`time_series` in your input folder, formatted as CSV.
As an example, if one asset listed in :ref:`energy production <production>` has :code:`generation_pv.csv` as value for the :ref:`file_name <filename-label>`. The file :code:`generation_pv.csv` containing a value of the pv generation for each timestep of the simulation should be present in the :code:`time_series` folder.
Copy link
Copy Markdown
Collaborator

@smartie2076 smartie2076 Apr 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As an example, if one asset listed in :ref:`energy production <production>` has :code:`generation_pv.csv` as value for the :ref:`file_name <filename-label>`. The file :code:`generation_pv.csv` containing a value of the pv generation for each timestep of the simulation should be present in the :code:`time_series` folder.
As an example, if one asset listed in :ref:`energy production <production>` has :code:`generation_pv.csv` as value for the :ref:`file_name <filename-label>`. The file :code:`generation_pv.csv` (containing a value of the pv generation for each timestep of the simulation) should be present in the :code:`time_series` folder.

Old:

As an example, if one asset listed in :ref:`energy production <production>` has :code:`generation_pv.csv` as value for the :ref:`file_name <filename-label>`. This file :code:`generation_pv.csv` contains the specific pv generation for each timestep of the simulation and should be present in the :code:`time_series` folder.

Copy link
Copy Markdown
Collaborator Author

@Bachibouzouk Bachibouzouk Apr 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You suggestion changes the main verb of the sentence which is "the file should be present", I will therefore not add it

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then how about brackets?

@Bachibouzouk
Copy link
Copy Markdown
Collaborator Author

I wanted to ask you to have a look at the "Building a model from assets and energy flows" section @smartie2076 as I am not sure it is up to date or if it doesn't require a good restructuring, as I am not sure the text would be helpful to anyone in its current form. Who was the target audience you wrote it for? Shouldn't we have a section titled "Energy system network"?

@Bachibouzouk Bachibouzouk merged commit 0c414a0 into dev Apr 29, 2021
@Bachibouzouk Bachibouzouk deleted the fix/proof-RTD-intro branch April 29, 2021 06:48
@smartie2076
Copy link
Copy Markdown
Collaborator

I wanted to ask you to have a look at the "Building a model from assets and energy flows" section @smartie2076 as I am not sure it is up to date or if it doesn't require a good restructuring, as I am not sure the text would be helpful to anyone in its current form. Who was the target audience you wrote it for? Shouldn't we have a section titled "Energy system network"?

Sure, I will have a look. I did write it for the end users, ie. project location owners initially...
I will think about adding that section title at that point

@smartie2076 smartie2076 mentioned this pull request May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants