Use solph instead of oemof in the documentation #952
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The aim of this PR is to consistently refer to
solph
instead ofoemof
in the documentation. I seem to remember from the 2022.11 meeting, thatoemof
should no longer be used synonymously withsolph
. However, in the documentation sometimesoemof
is used while actually referring just to thesolph
package. A prominent example is the title of the documentation (filedocs/index.rst
), where it reads "Welcome to oemof's documentation!".As oemof is a framework containing multiple packages by now, I think it would be better to be precise on which part of oemof is meant.
Questions