- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I just tried lpsolve in IML on SAS University Edition. It fails with "ERROR: out of memory", apparently regardless of the number of variables.
I've tried increasing the sizes on IML to no avail.
I wonder if changing the memsize option would work. I don't see how to do that under VirtualBox though. In fact, some comments indicate that SAS has actually locked us out 'because UE is only for smallish programs'. It's not clear to me that lpsolve would run on my config regardless of problem size.
Is there a way to change memsize on UE/VirtualBox setup? Is that really what is needed?
Thanks,
Duane
Release: 3.5 (Basic Edition)
Supported browsers:
- Microsoft Internet Explorer 9, 10, 11
- Mozilla Firefox 21+
- Google Chrome 27+
- Apple Safari 6.0+ (on Apple OS X)
Build date: Feb 3, 2016 10:49:31 PM
SAS Mid-tier release: Jan 13, 2016 7:00:00 PM
Java Version: 1.7.0_76
SAS release: 9.04.01M3P06242015
SAS platform: Linux LIN X64 2.6.32-573.26.1.el6.x86_64
Site name: UNIVERSITY EDITION 2.3 9.4M3
Site number: xxxxxxxx
Copyright © 2012-2016, SAS Institute Inc., Cary, NC, USA.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
This problem has nothing to do with the size of the problem. It was a bug in SAS University Edition for SAS 9.4m3. The issue has been fixed in SAS 9.4m4, so the problem will be fixed when you upgrade your copy of SAS UE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
You can't change any of these settings in SAS UE. As you observed, it is a learning tool. If you want to do heavy load testing of the SAS system, obtain a test installation from your SAS representative.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I don't recall seeing the 'learning tool' stance and associated limitations when I was installing it last year. The stress seemed to be on us not using it commercially. Maybe I missed it. I thought it was just missing some features.
So is lpsolve completely unavailable on UE due to this error? Or have I made a stupid mistake?
I have to say that I'm pretty put off if SAS would purposely hobble UE in this fashion.
If I can find it back, I recall finding instructions for loading UE on another virtualization environment and getting around this problem (if this is really my problem). But if SAS is acting in bad faith, then that sort of thing isn't a good strategy long term. Sounds like R's lp solution is a hassle, but at least they're not putting land mines in it on purpose.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
SAS UE is a for-free example installation of a usually very expensive software system. It is not "hobbled", but it is limited capacity-wise.
The intention behind UE is to provide SAS beginners a learning environment that lets them prepare for SAS certifications with data provided for the courses; with those, you'll never run into problems.
Your best option is to reduce the scope of your example data so you can get an example solution.
If you want to solve real-world problems, get a true SAS installation that is scaled to your requirements.
In the end it's all a matter of TANSTAAFL. And if the "learning stance" is not clear from this: http://www.sas.com/en_us/software/university-edition.html, then how else should SAS convey it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Looks like I'm nowhere near the limit. Still, the page you reference does not mention limiting problem size. Though to be fair, university and learning are mentioned. I was surprised to find out about the memory limit. I expect others will be as well. And it does seem tacky to me.
Non-commercial use seemed to be the target.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
This problem has nothing to do with the size of the problem. It was a bug in SAS University Edition for SAS 9.4m3. The issue has been fixed in SAS 9.4m4, so the problem will be fixed when you upgrade your copy of SAS UE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. That seems credible. I'll try upgrading. I thought I was up to date since UE checks at launch and reports that it is up to date.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Upgrading to 9.4M4 worked.