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
We got this issue kindly referred to us by Mr. Silvano.
As soon as I launch [OpenModal], I have a visual c++ error R6034. Then if I press ok, openmodal GUI opens. I import my uff file, the geometry is loaded correctly the measurements also, but in the analysis tab nothing appears and I can't run an analysis.
I join the log file to this email so you can see yourself the errors appearing in the command window.
The error: File "openModal\gui\widgets\analysis.py", line 1413, in update_model File "openModal\utils.py", line 89, in get_frf_from_mdd ValueError: could not broadcast input array from shape (16386) into shape (32772)
From what I see, there seems to be something going on in the analysis module, which could or could not be connected to issue #15. @sbtlaarzc could you take a look at it?
Further, it might be a bug but it might also be an 'unexpectedly' formatted .uff file, which unfortunately we can not have a look at. It would be good to know, where this uff came from (what software generated it).
Do we have any generic .uff files at hand in a repository somewhere so the users can test? If not, we should also think about that.
The text was updated successfully, but these errors were encountered:
Hello everybody! I managed to fix the issue by removing measurements that were recorded on the same node number. By only keeping one measurement per node, the analysis tab loads the FRFs correctly :)
I don't know if it's a bug, but the workaround seems to "fix" it.
We got this issue kindly referred to us by Mr. Silvano.
The log file: 1488458116_log.txt
The error:
File "openModal\gui\widgets\analysis.py", line 1413, in update_model File "openModal\utils.py", line 89, in get_frf_from_mdd ValueError: could not broadcast input array from shape (16386) into shape (32772)
From what I see, there seems to be something going on in the analysis module, which could or could not be connected to issue #15. @sbtlaarzc could you take a look at it?
Further, it might be a bug but it might also be an 'unexpectedly' formatted .uff file, which unfortunately we can not have a look at. It would be good to know, where this uff came from (what software generated it).
Do we have any generic .uff files at hand in a repository somewhere so the users can test? If not, we should also think about that.
The text was updated successfully, but these errors were encountered: