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

Handling of sparse matrices #17

Open
josephcslater opened this issue Mar 6, 2018 · 1 comment
Open

Handling of sparse matrices #17

josephcslater opened this issue Mar 6, 2018 · 1 comment

Comments

@josephcslater
Copy link
Member

As of this date, the module does not handle (is not aware) of sparse matrices. It would be prudent for all system matrices from FEA to be considered sparse. This necessitates the conversion to sparse format. The following notes were made in a notebook earlier. The first experience was in using mode_expansion_from_model.


It appears that the issue below in the vibrationtesting module is that sparse matrices are not handled. Slicing, multiplying, and inverting will all have to be done separately for sparse matrices. See the sparse matrices manual .

In the short term, converting them to full matrices will be good enough. In the long term, there will need to be parallel paths, one for sparse matrices, one for non-sparse. The appropriate format using scipy sparse matrices appears to be lil_matrix. On fix might be to rewrite, and automatically convert all matrices to this format before the math, then convert to the originating format afterwards to make the user happy.


@ghost
Copy link

ghost commented Jan 31, 2019

I am working on fixing this issue, please follow the link to see the progress: https://github.com/sainag2473/vibrationtesting/commits/vt.sainag2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant