Closed joakimkjellsson closed 2 months ago
Hi @joakimkjellsson,
I think this error was also noticed in the issue #1204 and solved by the PR #1206. If you merge release
into your branch or cherry-pick the changes in from that PR.
Please, let me know if that solves the problem :)
Thanks for the quick reply @mandresm! I cherry picked this and now it seems to work. Not too "complex" of a solution ;-) /J
I'm closing this one now then :)
Good morning
I tried to launch a run today on glogin from the
geomar_dev
branch but was met with a long error (at the end of this message).I have been mostly using the
feature/blogin-rockylinux9
branch for the past month or so, trying to get some runs done on the new blogin and glogin nodes. When that was working, I merged withgeomar_dev
which has also been synced a bit withrelease
. The same runscripts which worked fine onfeature/blogin-rockylinux9
do no longer work ongeomar_dev
. I tested a few different runscripts for different versions of FOCI-OpenIFS and same result: works onfeature/blogin-rockylinux9
but notgeomar_dev
.The error message,
ruamel.yaml.representer.RepresenterError: cannot represent an object: (1+0j)
, does not make much sense to me, but it seems that the yaml parser encounters a complex number (1+0j) and can't represent it. This sounds like there is a1
somewhere which is accidentally set to1+0j
, but I have no idea where...Does anyone have any ideas?
Cheers Joakim