Closed moritzshore closed 8 months ago
@michstrauch not sure if tagging works here but i'll try it out
Hi Mo,
I am in a rush, but for now: Wait before you dive into Linux forking. It won't work without a SWAT executable compiled for Linux.
Is there any chance in the climate workflow to restrict the number of threads to be you used? I did not yet run it myself ...
Cheers
Ok thanks, no rush micha! I'll stick with the windows stuff for now and see what I can do.
Sidenote: in our print.prt
basin_wb
is actually on line 11 not 10. Not sure if this is just a quirk in our setup, a quick in your setup, or just a typo. nevertheless, letting you know just in case.
Best!
ps. @NataljaC is the linux version of Rev_61_0_64rel
already available somewhere?
We have successfully compiled the Linux exe, but we need to wait for all the collaborators to approve the changed that are made in the code. ETA ~ week.
Hope this is okay with you.
Natalja
Ok thanks, no rush micha! I'll stick with the windows stuff for now and see what I can do.
Sidenote: in our
print.prt
basin_wb
is actually on line 11 not 10. Not sure if this is just a quirk in our setup, a quick in your setup, or just a typo. nevertheless, letting you know just in case.Best!
ps. @NataljaC is the linux version of
Rev_61_0_64rel
already available somewhere?
Thank Moritz, print thing was my error. Now updated.
Having a lot of problems with our virtural machine crashing due to unrestricted use of memory by the multi-core stuff.
From what I've read, this works much better on Linux with
fork()
'ing. Any experiences with this workflow on linux before I dive in?Or experiences with memory restriction on windows?
I'll try to figure it out on my own for now, but if anyone has advice, i'm all ears!
@michstrauch ?