Known bugs

From SUMOwiki
Jump to navigationJump to search

While we always try to test each release as much as we can, inevitably some bugs will always slip through unnoticed. This page only shows the most important bugs that have surfaced after the release was made.

To stay up to date with the latest news and releases, we also recommend subscribing to our newsletter here. Traffic will be kept to a minimum and you can unsubscribe at any time.

If you happen to encounter something not listed here, please report it.


Version 5.0

Bug Consecutive runs on the same dataset are not independent (can cause dataset depleted exceptions)
Status Fixed in SVN.
Workaround Wait for next release.


Bug Duplicate samples and samples with NaN/Inf values are not filtered properly.
Status Fixed in SVN.
Workaround Wait for next release. Simulators that may return invalid values or duplicate samples should be avoided until then.


Bug You get the following error: "Failed to create object of type ANNGeneticInterface, error is "Undefined variable "logger" or class "logger.severe"
Status Fixed in SVN.
Workaround Simply remove the offending line or set complex handling to split or modulus (you are trying to model complex data with ANNs).

Version 4.2

Bug Loading the random state from file gives a directory does not exist error.
Status Fixed in SVN.
Workaround Upgrade to the next version.


Bug When starting the toolbox for the first time you get an error like "The class ContextConfig cannot be found, make sure java is running"
Status Fixed in SVN.
Workaround This is a bug in Matlab itself. Please contact us for instructions on how to fix this.


Bug When starting the toolbox for the first time you get an error like "The class be.ac.ua.coms.m3.config.Util has no field or method named genHash"
Status Fixed in SVN.
Workaround This is a bug in Matlab itself. Please contact us for instructions on how to fix this.


Bug When the TestSamples measure is used without a dataset the testset is not calculated correctly!!
Status Fixed in SVN.
Workaround Replace the line 'tmp(testSet,:) = [];' by 'tmp(testSet,:) = NaN;'


Bug The optimization framework may fail in specific circumstances
Status The framework is currently under redesign and a much improved, more robust, version will be released with 5.0
Workaround Upgrade to 5.0 when it becomes available.


Bug The BatchModelBuilder fails with an error
Status Fixed in SVN
Workaround Simply remove the offending line

Version 4.1

Bug The maximum number of samples is not respected in a correct way
Status Fixed in SVN.
Workaround Upgrade to 4.2 when it becomes available.


Bug The toolbox crashes when you pass samples on the command line
Status Fixed in SVN.
Workaround On the offending line replace "scale(..)" by "scaleColumns(...)".

Version 4.0

Bug The toolbox goes into a seemingly infinite loop if u are using the Matlab sample evaluator and there is an error in your matlab function.
Status Fixed in SVN
Workaround This is due to the poor Java -> Matlab interface and thus there is little we can do about it. It is best to make sure your function runs without error by running it manually.


Bug In some rare cases the toolbox goes into an infinite loop when using the grid sample selector.
Status Fixed in SVN.
Workaround This happens in some rare cases, and is due to the way the grid SE works. This will be fixed in the next release. In the meantime, if you run into the problem use a different sample selector or combine the grid SE with a different SE (e.g., the random SE) using the CombinedSampleSelector.


Bug If the first component inside the <Plan> tag is a component that is overridden in the <Run> tag, a NullPointerException occurs
Status Fixed in SVN.
Workaround This is a very obscure bug, simply make sure that the first component in your <Plan> tag is one that is NOT overridden in a <Run> tag. Use for example <ContextConfig>.


Bug When modeling the same output multiple times in parallel, some profilers may interfere with each other
Status Fixed in SVN.
Workaround Avoid modeling the same output multiple times in the same run. Try using different runs or turning off the profilers that give problems.