-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Tutorial with Python' issues running the reaction_diffusion.py example file #307
Comments
Hi Rick, nice to meet you! I think this may be related to some changes I made to the networking code in October, in combination with SDCC being slow somehow. (I'm not sure how that would happen, but I've heard similar reports recently from another user on SDCC. Heavy I/O from some other user's job could do it.). Are you running the latest release, or an in-development version? If the latter, could you try going to
(if it looks like that) into
and see if that helps? The shortened timeout is intended to help skip over inoperable networks more quickly on startup, but it occurs to me that that timeout remains set on the socket so that any delay of more than three seconds on the working network will then cause a timeout. And your last log messages are just about three seconds apart... Once we know the network works we can afford to wait a bit longer if the system has a hiccup, so the above code tries to reset the timeout to something more reasonable once we have a connection. |
Hi Lourens, Thanks for your quick message. While checking in SDCC modules what the version of MUSCLE3 was, I just noticed that I made a big mistake. It wasn't even there!! I cloned the MUSCLE3 repository in the SDCC environment and went from there, assuming that the MUSCLE3 module was loaded. I added it now (properly....) and the file runs perfectly. Excuses, there is no issue at all now. Thanks again! |
Hi Rick, No, you did in fact find an issue. From the paths in the backtrace above, you were running from the Git repository, probably the current The module on SDCC contains the latest released version, which is older and does not have the shortened timeout code yet. So by switching to it, you've now got the examples running, but the problem is still there on the develop branch. I'm planning to make a new release this month which would have had this problem in it if you hadn't reported it, and then it would have showed up again. So thanks for the report! I'll go fix this before the new version goes out. |
Hi Lourens, Good to know for my understanding. Glad I could help! |
Hi, I'm Rick, doing my graduation project at Ignition Computing.
I am completely new to MUSCLE3, so I am going through the tutorial on https://muscle3.readthedocs.io/en/latest/tutorial.html.
While trying to run the example file 'reaction_diffusion.py', being connected to the iter sdcc server, I noticed no figure was appearing.
Upon further inspection in the NoMachine Client VSC environment, it was found that an error occurred (still no figure was appearing):
it also gave the following error in the muscle3.macro.log file:
Maarten suggested to change Matplotlib's backend using the command:
export MPLBACKEND=TkAgg
When now running the python file, it shows the figure in a separate window for a brief moment, before the Timeout error kicks in. Then the window disappears.
Trying the same in VSC, logging in with
ssh -X iter_login03
to the iter sdcc server, and changing the MPLBACKEND to TkAgg, it gives the following error while running the file:The muscle3.micro.log contains:
The muscle3.macro.log file contains:
The muscle3_manager.log file contains;
In local VSC, it does not even show the plot. (maybe it runs so fast, that the window has no time to open, before the timeout occurs)
I don't know what the problem is, but I was asked to report this issue. Regards!
The text was updated successfully, but these errors were encountered: