Monday, September 29, 2008
Changes for converters
I have committed lots of changes for (all) converters; also, the issue with splitted funcs (for nlps2nlp and lsp2nlp) has been fixed.
PSwarm v 1.2: bugfixes for Linux
Saturday, September 27, 2008
new converter: nlsp2nlp
I have committed nlsp2nlp converter, see NLSP page for details. It tries to minimize
You can try updated nlsp_1.py or nlsp_constrained.py from /examples.
However, a requirement should be satisfied: non-linear functions shouldn't be splitted.
This minor issue is intended to be fixed in future (BTW, splitting can't yield benefits for nlsp2nlp converter with any NLP solver).
||F(x)||2and, of course, it is capable of handling constrained problems.
You can try updated nlsp_1.py or nlsp_constrained.py from /examples.
However, a requirement should be satisfied: non-linear functions shouldn't be splitted.
This minor issue is intended to be fixed in future (BTW, splitting can't yield benefits for nlsp2nlp converter with any NLP solver).
Tuesday, September 23, 2008
Some more openopt install issues
Latest NumPy (taken from subversion repository) forced some OO users to inform me about some more openopt's install issues.
First of all, sometimes openopt's "python setup.py install" starts to search and download numpy 1.1.x from internet, while recent numpy from svn is already installed.
At second (it's especially inconvenient to me), modifying any single line in openopt's sources and then running "python setup.py install" now recompiles all openopt's files. Even if there were no changes at all, anyway all OO files are recompiled. Taking into account that I run this dozens times per day it's very annoying, and my increases danger for my HDD. Of course I could use OO without "python setup.py install" but this is inconvenient because of some reasons (I had already tried).
So, please take into account: these issues are not up to me, they are up to numpy.distutils developers. I hope they will fixed it ASAP.
First of all, sometimes openopt's "python setup.py install" starts to search and download numpy 1.1.x from internet, while recent numpy from svn is already installed.
At second (it's especially inconvenient to me), modifying any single line in openopt's sources and then running "python setup.py install" now recompiles all openopt's files. Even if there were no changes at all, anyway all OO files are recompiled. Taking into account that I run this dozens times per day it's very annoying, and my increases danger for my HDD. Of course I could use OO without "python setup.py install" but this is inconvenient because of some reasons (I had already tried).
So, please take into account: these issues are not up to me, they are up to numpy.distutils developers. I hope they will fixed it ASAP.
Monday, September 22, 2008
Install issues with latest numpy
Recently some changes have been committed to numpy, and previous openopt versions can't work with those ones.
So I have committed some changes to openopt, and AFAIK now openopt runs with all known to me numpy versions >= 1.1.0 correctly.
Hence, install/update OpenOpt from latest tarball or subversion repository is recommended.
So I have committed some changes to openopt, and AFAIK now openopt runs with all known to me numpy versions >= 1.1.0 correctly.
Hence, install/update OpenOpt from latest tarball or subversion repository is recommended.
Saturday, September 20, 2008
Friday, September 19, 2008
new converter: lp2nlp
Subscribe to:
Posts (Atom)