Revenue Management Optimisation Library

* A small addition, namely BidPriceVector_T&, has been made to the rmol/RMOL_Service.hpp interface. (0 comments)

The new release, namely the version 0.17.0, brings, along the classical platform-independent tar-balls (g-zipped and Bzip2-ed), RPM packages. Those RPM packages have been generated on a Linux Fedora 10 distribution, but may work on most of the ... [More] RPM-based distributions (e.g., Red Hat, Mandriva, Novell Suse). Moreover, the source RPM file (rmol.*.src.rpm) should allow to build the RPM packages tailored to your specific distribution, if needed. (0 comments) [Less]

The new release, namely the version 0.17.0, brings, along the classical platform-independent tar-balls (g-zipped and Bzip2-ed), RPM packages. Those RPM packages have been generated on a Linux Fedora 10 distribution, but may work on most of the ... [More] RPM-based distributions (e.g., Red Hat, Mandriva, Novell Suse). Moreover, the source RPM file (rmol.*.src.rpm) should allow to build the RPM packages tailored to your specific distribution, if needed. (0 comments) [Less]

jRMOM is the Java version of the RMOL library. Why Java? For an even wider spread of RMOL of course! (0 comments)

jRMOM is the Java version of the RMOL library. Why Java? For an even wider spread of RMOL of course! (0 comments)

As the RPM package has been built on a Fedora Core 6 with an AMD64, I do not know whether other platforms and/or processors are supported as well.From the source tarball and the spec file, however, it is possible to build a RPM on a Suse platform (I have tested it successfully on a Suse 9.2 with AMD64). (0 comments)

As the RPM package has been built on a Fedora Core 6 with an AMD64, I do not know whether other platforms and/or processors are supported as well.From the source tarball and the spec file, however, it is possible to build a RPM on a Suse platform (I have tested it successfully on a Suse 9.2 with AMD64). (0 comments)

The building system now follows the GNU standards (GNITS, etc.). Hence, the classical "./configure', 'make' and 'make install' sequence now works.Note that the test has to be compiled with the check target: 'make check' (there's not even the need to install the library for that purpose). (0 comments)

The building system now follows the GNU standards (GNITS, etc.). Hence, the classical "./configure', 'make' and 'make install' sequence now works.Note that the test has to be compiled with the check target: 'make check' (there's not even the need to install the library for that purpose). (0 comments)

That first working version optimally calculates the protections for the buckets/classes, corresponding to the prices/yields and demand distribution parameters (mean and standard deviation) given as input (as of today, still hard-coded in the "main" source code file, i.e., optimise.cpp). (0 comments)