Look for timeseries key in the dict_asset if the file is not present

[Bachibouzouk]

Fix #354

Changes proposed in this pull request:

• [x] If the TIMESERIES key is in the dict_values and the file under FILENAME cannot be found, the timeseries is loaded from TIMESERIES instead of throwing an error

Do the same for C0.treat_multiple_flows --> issue #882

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

• [ ] Use in-line comments to explain your code
• [ ] Write docstrings to your code (example docstring)
• [ ] For new functionalities: Explain in readthedocs
• [ ] Write test(s) for your new patch of code (pytests, assertion debug messages)
• [ ] Update the CHANGELOG.md
• [ ] Apply black (black . --exclude docs/)
• [ ] Check if benchmark tests pass locally (EXECUTE_TESTS_ON=master pytest)

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

[smartie2076]

Does this adress known bug #354? Is this just about the timeseries of eg. specific generation or demand being red from the json file instead of the file, or does this also work for efficiencies?

I will have to do the review later, as the deliverable has higher prio right now.

[Bachibouzouk]

Does this adress known bug #354? Is this just about the timeseries of eg. specific generation or demand being red from the json file instead of the file, or does this also work for efficiencies?

Thanks, I could not find the issue anymore last Friday and I was pretty sure there was one!

It only works with csv files being loaded, this could apply for efficiencies if they are loaded from the filename provided under the FILE_NAME in the input json (I only wanted to get rid of the FileNotFoundError when data was already available under the TIMESERIES key in the input json