- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

This happens irrespective of whether the matrix is the same or not. the second call to dss_reorder fails. Any ideas?

Link Copied

4 Replies

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

*"The structure of the matrix changes and hence the solver has to be deleted and reconstructed at every iteration" - what do you mean by "the solver has to be deleted"? Please show thow order of invoking dss routines and be much better if you give us the test case.*

*--Gennady*

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

At each time step do,

error = dss_create(handle,MKL_DSS_DEFAULTS)

error = dss_define_structure(handle,MKL_DSS_NON_SYMMETRIC,ia,n,n,ja,nnz)

dss_reorder(handle,MKL_DSS_AUTO_ORDER,perm)

!! then for a number of iterations I do.

error = dss_solve_real(handle,MKL_DSS_DEFAULTS,b,1,x)

!! After the code has converged

error = dss_delete(handle,MKL_DSS_DEFAULTS)

At the first time step this works fine. at the second time step . I am able to create the solver and define its structure. but when the call is made to dss_reorder, I get

Memory overwrite in lda-m gap: loc( -65536, 21322608) = 0.0000000 , Invalid message level

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

Hi,

Where do you call dss_factor?

Regards,

Konstantin

Topic Options

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page