Errors in MUSE_OS-develop\docs\tutorial-code

[Diego Moya]

Dear Sara,

I have been studying the examples in MUSE_OS-develop\docs\tutorial-code

Just 7-example works with any issues.

The others have the following errors:

·       1-introduction

muse.errors.GrowthOfCapacityTooConstrained: Error during the investment process. The capacity was not allowed to grow sufficiently in order to match the demand. Consider increating the MaxCapacityAddition and/or the MaxCapacityGrowth in the technodata.

I already modified MaxCapacityAddition and/or the MaxCapacityGrowth and the error persists.

Same as above in

·       2-add-agent\1-multiple-objective

·       2-add-agent\2-single-objective

·       3-add-region

·       4-modify-timing-data\1-modify-timeslices

·       4-modify-timing-data\2-modify-time-framework

 

·       In 5-add-service-demand\1-exogenous-demand

There is no tolm in this example

 

·       In 5-add-service-demand\2-correlation-demand simple

Using settings.toml: KeyError: 'scale'

Using settings_residential_regressed.toml: AssertionError: Regions file does not exist (D:\Path\MUSE_OS-develop\docs\tutorial-code\5-add-service-demand\2-correlation-demand simple\input\Regions.csv)

I have then included a Regions file and change GlobalCommodities by MUSEGlobalCommodities

KeyError: 'scale'

 

·       In 6-add-correlation-demand

KeyError: 'scale'

 

·       In 8-trade\final_trade

File "C:\Users\anaconda3\envs\muse\lib\site-packages\muse\interactions.py", line 126, in compute_interactions raise NoInteractionsFound muse.errors.NoInteractionsFound: A network with no interactions has been found. This might be the case if there are no retrofit agents and yet a 'new_to_retro' network has been defined for a particular sector. Asses the existance of both new and retrofit agents for all sectors and remove the new_to_retro interacton network if it is not needed

 

I would like to know is these errors have been addressed before just in case or if there is any help to address them as they are key to understand the capabilities of the OS.

 

Best regards,

Diego 

[sgiarols]

Dear Diego

thanks for your message. 

Just to say that the OS works on on the above-mentioned cases and the problems only refer to a mismatch with the sample cases present in the documentation.

In fact, the errors you receive is due to an outdated version of the tutorial in the documentation. We warn the uses that a mismatch with the documentation can happen because the tutorials which you mention, are illustrative examples on how to improve the model, but the cases constantly updated with the model updates are in data/example. 

At the next model release, due soon, the documentation will be also update these tutorials you mentioned. 

On our side, we regret that the tutorials give you the error and we are acting on updating the documentation. However, the standard procedure to build the model is to start from the data/example (the default one) and applying the instructions as explained also in the documentation and in the tutorial as for what needs to be incrementally changed to increase the model in complexity. This is the way we normally suggest to work with MUSE and we also consider that, although regretful, mismatches in updating the documentation, can be useful to have a better understanding of the model.

This should help you on what to do for sequentially building the model.

Best