Hi Andra, judging from the output, it seems that all 3 supersteps are executed in the second case as well, but getSuperstepNumber() is returning the wrong superstep number. I confirmed that this is also the case in VertexCentricConnectedComponentsITCase and SpargelConnectedComponentsITCase, i.e. the superstep number is wrong, but the results produced are correct. I'll try to find out what's wrong.
-V. On 4 March 2015 at 16:31, Andra Lungu <lungu.an...@gmail.com> wrote: > Hello, > > I have implemented a Bulk Synchronous Version of Triangle Count. The code > can be found here: > https://github.com/andralungu/gelly-partitioning/tree/triangles > > In this algorithm, the messages sent differ as the superstep differs. In > order to distinguish between superstep numbers, I used the > getSuperstepNumber() function. > > In order to test the overall implementation, I have extended > MultipleProgramsTestBase... nothing unusual until here. The problem is that > in CLUSTER mode, the test passes and the result is the one expected because > the superstep number changes, as can be seen below: > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Messenger]Step 2 > [Messenger]Step 2 > [Messenger]Step 2 > [Messenger]Step 2 > [Messenger]Step 2 > [Messenger]Step 2 > [Update]Step 2 > [Update]Step 2 > [Update]Step 2 > [Update]Step 2 > [Update]Step 2 > [Messenger]Step 3 > [Messenger]Step 3 > [Messenger]Step 3 > [Messenger]Step 3 > [Messenger]Step 3 > [Update]Step 3 > [Update]Step 3 > [Update]Step 3 > > For COLLECTION, the superstep number remains 1, and the result is obviously > not the one I expected. > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Messenger]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > [Update]Step 1 > > Does anyone have an idea what could have triggered this behaviour? > > Thanks in advance! > Andra >
