We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There's a complaint in Operations Research StackExchange that CONOPT-for-AMPL does not recognize requests for very large amounts of memory:
https://or.stackexchange.com/questions/12979/assigning-memory-to-conopt-in-ampl-for-solving-a-large-model
According to the user, the "CONOPT space" message says:
workmeg=100000
workmeg=100000000
workmeg=10000000000
The text was updated successfully, but these errors were encountered:
The user might try our conopt4 which should have library-managed memory allocation (it is ASL-managed in conopt 3.17)
conopt4
Sorry, something went wrong.
mapgccv
No branches or pull requests
There's a complaint in Operations Research StackExchange that CONOPT-for-AMPL does not recognize requests for very large amounts of memory:
https://or.stackexchange.com/questions/12979/assigning-memory-to-conopt-in-ampl-for-solving-a-large-model
According to the user, the "CONOPT space" message says:
workmeg=100000
gives 0.76 Mbytesworkmeg=100000000
gives 762.94 Mbytesworkmeg=10000000000
gives 8191.00 MbytesThe text was updated successfully, but these errors were encountered: