<div dir="ltr">Thanks Rick,<div><br></div><div>I suspected the number of files was an issue, but it wasn't fixed with the usual 'setfileoption' I'm used to dealing with when opening lots of .nc files. I've added a call to delete after each time and will see if that fixes it. I'll report back if it doesn't.</div><div><br></div><div>I don't have access to the server logs, and don't anticipate our HPC center will be very helpful in obtaining some deeper checks into this. Since the simple second check seems to solve the issue, I won't bother anyone about it.</div><div><br></div><div>Cheers,</div><div>Jon</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 1, 2015 at 4:01 PM, Rick Brownrigg <span dir="ltr"><<a href="mailto:brownrig@ucar.edu" target="_blank">brownrig@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Jon,<br><br></div>with regard to the second issue, I'm wondering if its a matter of too many open files. Linux/Unix typically has a limit of around 1024 max open files per process. I wonder if the reassignment of "f_in" each time through your loop is not closing the previous file. You might try "delete(f_in)" at an appropriate spot in your code once the "current" file is no longer needed.<br><br></div>I don't know about the 1st issue -- I don't suppose you have access to the thredds server logs?<br><br></div>Hope that helps...<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Rick<br><br><div><div><div><br></div></div></div></font></span></div>
</blockquote></div><br></div>