Some function names in GPLAB may conflict with the names of other MATLAB functions. This is not exactly a bug, neither am I providing a solution. Another bug that no one noticed! People, I'm counting on you to spot these things!! :-) The function plotpareto.m always assumed that better fitness was higher fitness, which was not even the case with the demo function. The new checkvarsparams.m function provides a workaround for this problem, to be properly solved in a future release.Ĭontrary to what the user's manual says, when the parameter 'fixedlevel' was 1 and the parameter 'realmaxlevel' was empty, 'realmaxlevel' was not being filled automatically! The new checkvarsparams.m function also fixes this, along with the new checkvarsstate.m function. Thanks to Leonardo Vanneschi and Antonella Farinaccio for spotting this. With a particular set of parameters, the individuals sampled more often did not have their test fitness correctly measured. There was a problem when using a test set. Thank you to Zheng Yin for providing a corrected version. The function evaluate_tree.m, which is a workaround for the "nesting 32" MATLAB error, used to fail when there were 10 or more columns in the input data. The new normalize.m function corrects this. The normalization of vectors had some problems when there were negative values present. Thank you to Martin Schobert for warning me about this. There was conflicting information about which type of license applies to GPLAB, so here is an updated license.txt file. Here is a brief description of each bug, followed by a zip file containing all the fixes: More than two years after Version 3 came out, and all you have to offer is a few bug fixes? Well. Here you can find the files that were released before version 4: Home features download older versions new versions acknowledgements GPLAB - A Genetic Programming Toolbox for MATLAB
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |