Thanks for letting us know! This is indeed a communication issue w.r.t. the VTK output (the inter-block communication for the actual simulation is correct, luckily).
You can fix the Rayleigh Bernard example by adding a call to sLattice.communicate()
in getResults
for the VTK-writing timesteps.