Unclear problem following capacity planning tutorial

[DariusAttebrant]

Hello. I am currently attempting to follow the following tutorial https://spine-tools.github.io/SpineOpt.jl/latest/tutorial/capacity_planning/
I can however not get the model to work even though I have, to the greatest possible extent, verified that my model is identical to that of the example. I believe that the problem could stem from some error on my part when introducing several temporal blocks. When I try to run the model it fails in the execution of Run SpineOpt. The error looks as below

I believe that I have the latest version of all programs, as attached below. One thing I am unsure of in this aspect is whether there is a required version of python, of which I currently have 3.9.13. It should be enough according to the installation specifications though.

I am also somewhat unsure about which Julia version Spine is using. In the folder pointed to under files>settings>tools a Julia with version 1.11.4 is located. However, if the "install Julia" button is pressed it claims to only have 1.10.0 and begins installing 1.11.4. It never changes in the sense that I can repeat this process and it will still claim not to be up to date. An image of this is shown below. The Julia interface is the one under C:\Users\warthog\AppData\Local\julias\bin\julia.cmd

Thanks in advance!

Attach your model as a JSON file (encouraged)

broken_caoacity_planning_tutorial.json

What versions are you using?

SpineOpt: 0.10.1
SpineInterface: 0.15.2
SpineToolbox: 0.9.5
Julia: 1.11.4 or 1.10.0 see above

[tarskul]

Thanks for the extensive information. That made it easier for me to look at. The julia version is a bit weird but otherwise the installation seems fine to me.

You guessed it right that the issue was with the introduction of the temporal blocks. You made two mistakes:

• In the time series of the demand, you entered data at T01 instead of T00 (probably because it automatically jumps when you enter data)
• In the operational block of 2035 you start at 2036-01-02T00:00:00 instead of 2036-01-01T00:00:00

[DariusAttebrant]

Thank you! Not sure how I could miss those when double checking. Upon further inspection I had made the same error in the other time series for available units as well. The model now works as intended.

Once again, many thanks for your support!