- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to Stefan for letting us know that this is not a serious issue.
We will fix it in a future release.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Stefan,
Thank you for posting the issue.
We can reproduce it on our side. If you set iparm[20]=0 or 1, the disappeared message will reappear.
May I ask what is the typical value of max_iterref_steps in your application? Also could you tell us how important is this issue to your project? Does this issue hinder your work?
Best regards,
Ruqiu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iparm[7] (max_iterref_steps) is currently set to 1 by default. Having iparm[20]=3 and iparm[7]=2 (the default) or iparm[7]=10 does not work. But setting iparm[20]=3 and iparm[7]=0 seems to work.
Since we have workarounds (iparm[20]=0 or 1, iparm[7]=0, or using an older MKL), this issue is not a serious blocker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to Stefan for letting us know that this is not a serious issue.
We will fix it in a future release.

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