-
Notifications
You must be signed in to change notification settings - Fork 16
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
Onedimensional - occassional errors in calculation - Windows build #5
Comments
t1.zip |
Hi, Thank you for reporting the issue. I pushed a fix in the dev branch. Could you try it and let me know if it fixes the issue for you too? |
Hi Florian,
|
That's strange. Are you sure you compiled the |
No, i'm stupid, i looked at the history too quick and thought dev has been merged to master already. |
Great, I close the issue and will merge the |
Hi, here is a problematic test case that i don't understand.
The problem is that calculation is not consistent. Sometimes a correct solution is found, and sometimes the results are wrong - some random bin is introduced that wasn't there in the inputs, or nonsensical results are printed.
This happens on Windows build from recent master branch. I didnt test on Linux.
my command line used for testing (always the same, im running this repeatedly):
The results are different on every run. In the attached case it seems totally wrong, like some data corruption:
sometimes it gets the result right:
And sometimes result seems right, but it packs an item exceeding bin size to the last bin:
If the results are wrong, the command output shows (sometimes) that some extra bin type has been introduced, that's not present in the input bins file (like the bin no#5 in the first example above), or the 'Final statistics' section is missing entirely. Sometimes the results are wrong but there's no extra bin type, just the wrong bin size is used like above.
correct run output:
BTW with
--vbpp-algorithm sequential-value-correction
option the problem doesn't seem to appear.[
bins_ea6574d4ab0d40dfa23bc04e5b686dd9.csv
items_ea6574d4ab0d40dfa23bc04e5b686dd9.csv
solution_ea6574d4ab0d40dfa23bc04e5b686dd9.csv
](url)
The text was updated successfully, but these errors were encountered: