-
Notifications
You must be signed in to change notification settings - Fork 3
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
Reconstruction get stuck with minimal missing samples #29
Comments
I was already debugging similar. Best way was for me to
Can you add:
|
Just the current develop branch (commit bcf3098). dumpXML = 1 |
I just discovered that these are the nodes with missing samples at the end. Other nodes should have that data so all of them should be able to reconstruct those samples. WARNING : Simulator : Node 36 is missing 17 samples |
Same case, focusing on Node 36 and its row 30 neighbors: WARNING : Simulator : Node 36 is missing 17 samples It seems clear the neighbors should have sent all the data they have, but for some reason they are not doing so. |
When executed with the following parameters:
randomSeed = "DAS"
and
INFO : Simulator : Shape: {'run': 0, 'numberNodes': 256, 'blockSize': 32, 'failureRate': 10, 'netDegree': 8, 'class1ratio': 0.8, 'chi': 2, 'vpn1': 1, 'vpn2': 500, 'bwUplinkProd': 2200, 'bwUplink1': 110, 'bwUplink2': 2200, 'randomSeed': 'DAS-bs-32-nn-256-fr-10-c1r-0.8-chi-2-vpn1-1-vpn2-500-bwupprod-2200-bwup1-110-bwup2-2200-nd-8-r-0'} ... Block Available: 0 in 69 steps
the block does not become available.
The weird thing is that it gets block when missing only 140 samples, here are the last lines of the XML dump:
For a block with 1024 samples and a network of 256 nodes, I think it is virtually impossible to get stuck at this stage. If the 140 missing samples are distributed among multiple nodes, then any node with less than 16 missing samples should be able to reconstruct them. If all of the missing samples are in one single node then the other nodes holding the same rows/columns should have the entire data.
The text was updated successfully, but these errors were encountered: