update your rss feeds if you want to get the posts furthermore.
New location:
http://forum.openopt.org/viewforum.php?id=19
Monday, December 15, 2008
OpenOpt (and my) Future
My interim in icyb.kiev.ua optimization dept is up to be finished.
Today I have spoken with my chiefs from about my further career.
They have informed me: because of financial crisis the situation is undefined.
Still I have some chances. Moreover, there are some chances I will be permitted to spent some work time for further openopt development.
However, it is provided some conditions to be satisfied.
Some days ago I had been forced to move my code out of scikits framework, my chiefs want me to host it inside Ukraine under our control (mb you know I had been refused to obtain veto rule for openopt code changes within scikits framework; I understand scipy community - they can't take taht something is hosted inside their server and is out of control, but I understand my chiefs position as well).
I have contacted uafoss.org (FOSS Ukraine dept), and they gladly allowed me to host it here.
Full transportation (svn repository, doc, wiki etc) will be finished within several days. But numerical optimization forum already works, you are welcome: http://forum.openopt.org. I had noticed openopt.com and openopt.net are already taken by someone, so it's definitely correct time to go.
Thanks to Michailo Danilenko and Volodimir M. Lisivka from linux.org.ua (LOU) community.
Special thanks to Wadim V. Mashkov and Michael Shigorin from linux.kiev.ua community.
Today I have spoken with my chiefs from about my further career.
They have informed me: because of financial crisis the situation is undefined.
Still I have some chances. Moreover, there are some chances I will be permitted to spent some work time for further openopt development.
However, it is provided some conditions to be satisfied.
Some days ago I had been forced to move my code out of scikits framework, my chiefs want me to host it inside Ukraine under our control (mb you know I had been refused to obtain veto rule for openopt code changes within scikits framework; I understand scipy community - they can't take taht something is hosted inside their server and is out of control, but I understand my chiefs position as well).
I have contacted uafoss.org (FOSS Ukraine dept), and they gladly allowed me to host it here.
Full transportation (svn repository, doc, wiki etc) will be finished within several days. But numerical optimization forum already works, you are welcome: http://forum.openopt.org. I had noticed openopt.com and openopt.net are already taken by someone, so it's definitely correct time to go.
Thanks to Michailo Danilenko and Volodimir M. Lisivka from linux.org.ua (LOU) community.
Special thanks to Wadim V. Mashkov and Michael Shigorin from linux.kiev.ua community.
OpenOpt release 0.21
Hi all,
I'm glad to inform you about new OpenOpt release: v 0.21.
Changes since previous release 0.19 (June 15, 2008):
Backward incompatibility:
Welcome to http://forum.openopt.org - new forum about numerical optimization and related free and open source software.
For assist with new host and forum
Thanks to Michailo Danilenko and Volodimir M. Lisivka from linux.org.ua (aka LOU) community.
Special thanks to Wadim V. Mashkov and Michael Shigorin from linux.kiev.ua community.
Regards, Dmitrey.
I'm glad to inform you about new OpenOpt release: v 0.21.
Changes since previous release 0.19 (June 15, 2008):
- major changes for NLP / NSP solver ralg
- new converter: qp2nlp
- new converter: lp2nlp
- new converter: nllsp2nlp
- new converter: nlsp2nlp
- new converter: minimax to NLP
- Introducing OpenOpt GUI
- PSwarm 1.3 has been connected instead of v 1.1. It has much more parameters to modify and ability to use user-supplied callback function.
- Lots of changes related to oofun: add oovar and oolin, now fixed oovars can be correctly handled
- enhanced iterfcn connection for scipy fmin_cobyla
- some doc updates for result structure
- new openopt API func: oosolver
- some code cleanup and bugfixes
- some other minor changes
Backward incompatibility:
- instead of "from scikits.openopt" now you should use "from openopt import ..."
- LSP has been renamed to NLLSP
- oofun with ordinary variables (x) support had been ceased (it's hard to keep maintaining), use oovars instead.
Welcome to http://forum.openopt.org - new forum about numerical optimization and related free and open source software.
For assist with new host and forum
Thanks to Michailo Danilenko and Volodimir M. Lisivka from linux.org.ua (aka LOU) community.
Special thanks to Wadim V. Mashkov and Michael Shigorin from linux.kiev.ua community.
Regards, Dmitrey.
Some changes for oofun
Some changes for oofun:
- oolin now can handle matrices: oolin(C) creates oofun that returns numpy.dot(C, inp_array); oolin(C, d) yields oofun that returns numpy.dot(C, x) + d. See updated oolin example.
- add fixed variables handling for oovars. Now you can declare v.fixed = True or just v = oovar(..., fixed = True). So all oofuns that recursively depend on fixed oovars only will be calculated only once, and derivatives will be all-zero (hence no calculations will be required for those parts of code that depend on fixed oofuns only). In future it will be good to have inner fixed coords for oovars, like this: v.fixed = [0, 1, 15] (i.e. positions of fixed coords inside the oovar). See the fixed oovars example.
Saturday, December 6, 2008
some changes
I have committed some changes to OO Kernel, most important is a fix reducing time for connecting oovars to prob instance (the recursive function throw all oofuncs took too much time previously).
Thursday, November 27, 2008
Ironclad v0.7 released (NumPy on IronPython)
Tuesday, November 25, 2008
CorePy: Assembly Programming in Python
I've got to know about BSD-licensed v 1.0 release of CorePy - "a Python package for developing assembly-level applications on x86, Cell BE and PowerPC processors".
I guess it would be useful for those objective or non-linear functions that are required to be evaluated sufficiently faster than pure Python-coded.
Of course, using C, C++, Fortran code via Cython, f2py, ctypes, SWIG, Pyrex etc could yield some speedup as well.
I guess it would be useful for those objective or non-linear functions that are required to be evaluated sufficiently faster than pure Python-coded.
Of course, using C, C++, Fortran code via Cython, f2py, ctypes, SWIG, Pyrex etc could yield some speedup as well.
Subscribe to:
Posts (Atom)