BUG: objectRegistry: do not clear event number on dependent objects
This was causing same event number on both U and grad(U) which meant that if one of the processors had different event number the trigger of gradient caching would not be synchronised. Now instead the overflow is detected in the regIOobject::upToDate function and handled consistently (by assuming that the events of object will never differ by more than labelMax/2)
Please register or sign in to comment