Skip to content

Add benchmark tests for csv features#542

Merged
smartie2076 merged 25 commits intodevfrom
patch/tests_for_features
Oct 1, 2020
Merged

Add benchmark tests for csv features#542
smartie2076 merged 25 commits intodevfrom
patch/tests_for_features

Conversation

@smartie2076
Copy link
Copy Markdown
Collaborator

@smartie2076 smartie2076 commented Aug 31, 2020

Not addressed checkpoints are summarized in #541. For solving #541, please also look at what was done in this PR.

Changes proposed in this pull request:

  • Fix using a timeseries for instead of a scalar parameter value.
  • Add benchmark test test_benchmark_feature_parameters_as_timeseries: Applied to efficiency and energy_price.
  • Add input data for future benchmark test test_benchmark_feature_output_flows_as_list (applied to an energyConsumption asset)
  • Add input data for future benchmark test test_benchmark_feature_input_flows_as_list (applied to an energyConsumption asset)

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

  • Use in-line comments to explain your code
  • Write docstrings to your code
  • For new functionalities: Explain in readthedocs
  • Write test(s) for your new patch of code
  • Update the CHANGELOG.md
  • Apply black (black . --exclude docs/)

@smartie2076 smartie2076 added the enhancement New feature or request label Aug 31, 2020
@smartie2076 smartie2076 self-assigned this Aug 31, 2020
Base automatically changed from Benchmark_heat to dev September 1, 2020 11:43
@Bachibouzouk
Copy link
Copy Markdown
Collaborator

@smartie2076, the files that were in src are now in src/mvs_eland, luckily there are not too many changes to perform (in the test files the imports have changed from from src.<module> to from mvs_eland.<module>

@smartie2076
Copy link
Copy Markdown
Collaborator Author

@ursulaelmir I have not written the tests for this jet, but two input flows for an energyConversion object may be simulated with these inputs:

Feature_input_flows_as_list.zip

As said, I did not test the results! I just want to update you on this. If you need any intervention from me regarding this, you should drop the issue until after you handed in your thesis.

@smartie2076 smartie2076 marked this pull request as ready for review September 10, 2020 15:09
@smartie2076
Copy link
Copy Markdown
Collaborator Author

@Bachibouzouk you could also review this one, but only if you do not go by commits :'D

Copy link
Copy Markdown
Collaborator

@Bachibouzouk Bachibouzouk left a comment

Choose a reason for hiding this comment

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

The docstrings can be added in a subsequent PR. I would just remove the code which is commented out if it is not going to be considered here.

@Bachibouzouk
Copy link
Copy Markdown
Collaborator

@smartie2076 - can this be merged (once the conflict with changelog has been solved of course)

@smartie2076
Copy link
Copy Markdown
Collaborator Author

@smartie2076 - can this be merged (once the conflict with changelog has been solved of course)

I need to change the description of the PR, but that is all. It will not fix the issue it was supposed to fix, though ;)

@smartie2076
Copy link
Copy Markdown
Collaborator Author

@Bachibouzouk I think it is fine to merge, the commented out benchmark tests are intentional.

@smartie2076 smartie2076 merged commit 502a489 into dev Oct 1, 2020
@smartie2076 smartie2076 deleted the patch/tests_for_features branch October 1, 2020 12:36
@Bachibouzouk Bachibouzouk mentioned this pull request Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants