<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Wesley,<div class=""><br class=""></div><div class="">I tried doing that but to no avail. My guess is something is going on with my installation/internals of GrADS. I come from more of a programming/computer science background, so when I saw that my code had no race conditions but still broke when running in parallel, I immediately thought it must have been something I wasn’t familiar with GrADS (as GrADS from my point of view is not intuitive at all). I appreciate your advice.</div><div class=""><br class=""></div><div class="">Thank you,</div><div class=""><br class=""></div><div class="">Josh<br class=""><blockquote type="cite" class=""><pre class="" style="white-space: pre-wrap; font-variant-ligatures: normal; orphans: 2; widows: 2;">Josh,
Problems in running jobs in parallel usually are caused by a file that is
being "shared" when it shouldn't be.
g2grb.gs uses temporary files but there names are based on the output
file which is different in the parallel runs.
wgrib2 doesn't make temporary files and doesn't lock files. So I don't
know what is causing your problem. My suggestion is turn each of the
parallel jobs in its own directory.
Wesley
</pre></blockquote><div class=""><pre class="" style="white-space: pre-wrap; font-variant-ligatures: normal; orphans: 2; widows: 2;"><br class=""></pre></div></div></body></html>