Skip to content
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

ENH: Analysis, bad array shapes after uff/unv import #16

Open
matmr opened this issue Mar 9, 2017 · 2 comments
Open

ENH: Analysis, bad array shapes after uff/unv import #16

matmr opened this issue Mar 9, 2017 · 2 comments
Assignees

Comments

@matmr
Copy link
Contributor

matmr commented Mar 9, 2017

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 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.

@matmr matmr added the bug label Mar 9, 2017
@matmr matmr changed the title BUG: Analysis, array shapes after uff/unv import BUG: Analysis, bad array shapes after uff/unv import Mar 9, 2017
@SilvanoPecoraro
Copy link

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.

@matmr
Copy link
Contributor Author

matmr commented Mar 10, 2017

Ok. Glad you managed to work around it 👍

Still, if multiple measurements can be present for one node, we have to handle that somehow.

I am leaving the issue open, changing from bug to enhancment

@matmr matmr added enhancement and removed bug labels Mar 10, 2017
@matmr matmr changed the title BUG: Analysis, bad array shapes after uff/unv import ENH: Analysis, bad array shapes after uff/unv import Mar 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants