-
Notifications
You must be signed in to change notification settings - Fork 529
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
b4b issue on mww3_test_03 with grdset_d2 #144
Labels
help wanted
Extra attention is needed
Comments
mickaelaccensi
changed the title
b4b issue on mww3_test_03 with grdset_d2
b4b issue on mww3_test_03 with grdset_d2
Jan 13, 2020
Moving comments from @ajhenrique from VLab issue 45652 on 10/5/18:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it is not b4b when you change the number of mpi procs
you could reproduce it by running this regtest with values of mpi tasks multiple of the number of cpu per node
(here I have 28 cpus per node), so I ran -n=$N with N = 28, 56, 84, 112
bin/run_test -c datarmor_intel_debug -m grdset_d2 -n $N -p $MPI_LAUNCH -s PR3_UQ_MPI -w work_d2 -N -o netcdf ../model mww3_test_03
the differences are on all the out_grd.*, out_pnt.*and netcdf output files
this is due to load balancing
otherwise it's always b4b if you run twice the same test
The text was updated successfully, but these errors were encountered: