Rolling Horizon Error

[hannesfelipe]

Dear SpineOpt-Team,

I recently installed SpineToolbox and SpineOpt. I am still getting into the environment, and I am happy to see all the options Spine provides. However, I’ve got a problem and don’t know how to solve it.

I did all the steps from this tutorial: https://www.youtube.com/watch?v=brf6rlzNDR0. Everything worked as described until the last element. Applying the roll_forward parameter leads to an error message.

ERROR: LoadError: MethodError: no method matching roll!(::SpineInterface.TimeSlice, ::Dates.CompoundPeriod; update::Bool)

Closest candidates are:
roll!(::SpineInterface.TimeSlice, ::Union{Dates.CompoundPeriod, Dates.Period}; refresh) got unsupported keyword argument "update"

I assume that there has something changed in the Spine-structure since then? Or is it Julia specific. The tutorial uses Julia 1.8.5. I use Julia 1.9.2. I use spinetoolbox 0.6.18.

Best regards and thanks for your support!

[Tasqu]

@hannesfelipe As far as I can tell, you seem to have a version conflict between SpineOpt and SpineInterface.

ERROR: LoadError: MethodError: no method matching roll!(::SpineInterface.TimeSlice, ::Dates.CompoundPeriod; update::Bool)

Closest candidates are:
roll!(::SpineInterface.TimeSlice, ::Union{Dates.CompoundPeriod, Dates.Period}; refresh) got unsupported keyword argument "update"

is caused by SpineOpt trying to call the roll! function using the update keyword, which was replaced by the refresh keyword by this commit on the 30th of June. Based on the given closest candidate using the refresh keyword, your SpineInterface seems to be up to date with SpineOpt lagging behind.

Updating your SpineOpt should hopefully fix this issue. Alternatively, you can try downgrading your SpineInterface to a version before this commit, but I wouldn't recommend that.

[hannesfelipe]

@Tasqu thank you for the respone.

I already thought about this. My SpineOpt is version 0.06.13. Totally forgot to mention that. At least, I tried to install the current version of all packages.

I assume that is the current version. Seems like I have to try the downgrading or do you have any other idea?

[Tasqu]

I'm guessing you've installed SpineOpt and SpineInterface according to the README instructions? E.g.

using Pkg
pkg"registry add General https://github.com/spine-tools/SpineJuliaRegistry"
pkg"add SpineOpt"

This can occasionally result in version conflicts between the two packages if we fail to properly update the SpineJuliaRegistry, which I'm guessing is the case here. I'll have to investigate.

In the meantime, you can try installing SpineOpt directly from the source (instructions in the README), which will guarantee that you're using the latest development version of SpineOpt, which shouldn't have this issue with SpineInterface.

using Pkg
pkg"dev <path-to-your-local-SpineInterface-repository>"
pkg"dev <path-to-your-local-SpineOpt-repository>"

Note that you will have to download or clone the repositories on your machine for the above to work.

[Tasqu]

@hannesfelipe Sorry for the delay, I ran into another more serious issue with SpineInterface while figuring out this one. As I suspected, the issue was that the SpineOpt version 0.6.13 in the registry wasn't compatible with the SpineInterface version 0.11.3 in the registry. However, this should now be solved with versions 0.6.14 and 0.11.5 updated to the registry.

TLDR: pkg> add SpineOpt and pkg> add SpineInterface should now install compatible versions of SpineOpt and SpineInterface, avoiding this bug.

[hannesfelipe]

@Tasqu thank you very much for your support. I updated SpineOpt and SpineInterface today. Seems like everything is working now.