-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug in PoolLast's is_empty method #1
Comments
Thank you for detecting that. Fortunately, I think it is not relevant, because, as I remember, the experiments were carried out with a pool non empty. Anyway, I will check, and give you a more complete information (and a fix) later. |
Thank you for your response! I need SHADE-ILS for my own research, and because of that I have downloaded I have noticed that a lot of it is not being used (got rid of ~3/4 of it at the moment), Would you mind if I shared refurbished code with you so you could update |
Ok.
Yes, sometimes it happens. I write several options that finally did not work, and some code is actually not used at all. However, when I publish the paper, I prefer to submit the source code used for the experimental section, so sometimes that code was not removed.
I do not mind, however, in order to maintain localled the original source code, I prefer to have for now in another branch. |
Thank you for your response! I am waiting for your insights on the bug :) |
In class PoolLast from shadeils.py we can find (line 73):
Given the fact that the result of dictionary class's method
values()
returns some type of a collection,no matter the contents of the dictionary, the comparison
values() == 0
will always yieldFalse
.As a result,
if not pool_global.is_empty():
statement found in line 292 will always be executed .I assume that the behaviour is unintended, but does it have an impact on the performance, overall logic of the method?
The text was updated successfully, but these errors were encountered: