- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi. I have a project that worked using vs 2013 and an earlier version
of PARDISO. I just upgraded to vc++ from vs2015 and the current version of mkl
(already to update 2, released a few days ago).
of PARDISO. I just upgraded to vc++ from vs2015 and the current version of mkl
(already to update 2, released a few days ago).
Now, PARDISO crashes - sometimes - using identical input data.
That is, using the same parms and input values, it will sometimes
complete w/o error, sometimes on the 2nd attempt, sometimes on
the 110th and so on. Given enough attempts, it allways crashes using
that data.
complete w/o error, sometimes on the 2nd attempt, sometimes on
the 110th and so on. Given enough attempts, it allways crashes using
that data.
i have extracted a small example program that shows the errror.
Basically, its a loop that reads the same data and calls pardiso. i have
tested this on various machines and the crash allways happens - not
allways after the same loopcount, but it does happen.
Basically, its a loop that reads the same data and calls pardiso. i have
tested this on various machines and the crash allways happens - not
allways after the same loopcount, but it does happen.
A VS 2015 project is here: https://diecloudstorage.blob.core.windows.net/pardisocrash/mkl_crash_vs2015_source.zip
The resulting binary is missing the
solver DLLs that i use, but those are in the precompiled binaries zip.
solver DLLs that i use, but those are in the precompiled binaries zip.
The precompiled binaries are here: https://diecloudstorage.blob.core.windows.net/pardisocrash/mkl_crash_windows_bin.zip
To test this, the program needs the path to the data files as
1st parameter. e.g.g: "c:>mkltest d:\temp"
1st parameter. e.g.g: "c:>mkltest d:\temp"
The test data is here: https://diecloudstorage.blob.core.windows.net/pardisocrash/mkl_crash_data.zip
Any ideas what might be causing this and what i can do about this?
WM_THX
-thomas woelfer
-thomas woelfer
Link Copied
- « Previous
-
- 1
- 2
- Next »
26 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the expectation time frame is end of August - beginner of September
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Gennady Fedorov (Intel) wrote:
the expectation time frame is end of August - beginner of September
Is there a workaround until the update is out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
there is no workaround with that issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. MKL 11.3.4 has been release a few weeks ago. Could you check how this update works on your side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has this issue been fixed in MKL 2017?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes. You may try the newest MKL 2017 update 1 ( released Nov 1st ).
Reply
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
- « Previous
-
- 1
- 2
- Next »