-
Notifications
You must be signed in to change notification settings - Fork 0
threaded ocean core timestamp issues #1289
Comments
@Larofeticus and @philipwjones
The added print statement shows that, when running with two threads:
With one thread it has the correct time. Is it clear that timeStamp should be on the shared list? |
BTW, currently there is also a write statement within that omp parallel loop:
If I run with two threads in debug mode, the second thread also has trouble writing to the std err unit=0 file. This is the output:
If I move the print statement outside the omp loop, the problem goes away. But we may want to print within threaded sections elsewhere. |
I tested MPAS-O standalone on LANL grizzly using |
@mark-petersen - just to help diagnose, can you try putting these print/write statements within a critical region, i.e.: |
Probably related, on a threaded run on grizzly with intel, with
|
I’m tested threaded MPAS-O stand-alone on edison. The second thread has a blank instead of a proper timestamp variable.
The text was updated successfully, but these errors were encountered: