You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @robbievanleeuwen, this is a bit of a weird one that I have encountered a few times and boiled it down the following:-
Describe the bug
Running the code below results in various consistent errors occurring from crashing the kernel and returning a triangle-related error. However, it completes every now and then (often only the first time you run it from VSCode in a jupyter notebook after booting up, but the next time you run it the same errors)!
Very weird, beyond my skills to really diagnose the cause.
This behaviour seems to occur when utilising a doubly symmetric section (section and reinforcement), and with a theta of 45 degrees only.
One thing I have noted is if say you go to 45+180 or 45+90 degrees rotation for the same section effectively being analysed, it always works. So it is something specifically about 45-degree neutral axes rotation that's causing the effect as far as I can tell.
Can you confirm you see the same behaviour? Any ideas?
Desktop (please complete the following information):
OS: WIndows 10
Same behaviour on current version 2.1.3, and the latest master
Python 3.10.8 (errors seem to be independent of this, checked on python 3.8 as well and same behaviour, possibly seeing kernel crash more often than the triangle error on 3.8 though).
The text was updated successfully, but these errors were encountered:
Hi @robbievanleeuwen, this is a bit of a weird one that I have encountered a few times and boiled it down the following:-
Describe the bug
Running the code below results in various consistent errors occurring from crashing the kernel and returning a triangle-related error. However, it completes every now and then (often only the first time you run it from VSCode in a jupyter notebook after booting up, but the next time you run it the same errors)!
Very weird, beyond my skills to really diagnose the cause.
This behaviour seems to occur when utilising a doubly symmetric section (section and reinforcement), and with a
theta
of 45 degrees only.One thing I have noted is if say you go to 45+180 or 45+90 degrees rotation for the same section effectively being analysed, it always works. So it is something specifically about 45-degree neutral axes rotation that's causing the effect as far as I can tell.
Can you confirm you see the same behaviour? Any ideas?
Error variation 1
Error variation 2
To Reproduce
Run this code
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: