Okay. Here's where I'm at right now.
I believe we encountered KeyboardInterrupt errors before when the script was being killed either by out-of-memory or memory-corruption issues. This would only be possible in the HOP code, which corresponds to what you are seeing in terms of the commenting out of RunHOP. Unfortunately, it's not easy for me to reproduce memory corruption here on such a large dataset. I am attempting to do so with the L7 RD0035 dataset. I will be doing this by running your script on four processors on one of our machines; unfortunately, all our multiproc machines also have lots of RAM. So I'm not sure I'll be able to get identical results, but I am trying.
Are you running with vanilla trunk, and which revision? I'm on vanilla trunk r1297.
On Thu, May 7, 2009 at 10:43 AM, Stephen Skory email@example.com wrote:
I ran the script on Kraken. It ran with 128 threads and 8gb per thread. It gets stuck in HOP someplace (no error messages) with 64 threads/8gb on Kraken on one thread. That thread has the largest amount of particles, so it's likely that it is running out of memory.
How big is DD0082?
It is 150GB.
_______________________________________________________ firstname.lastname@example.org o__ Stephen Skory http://physics.ucsd.edu/%7Esskory/ _.>/ _Graduate Student ________________________________(_)_(_)_______________ _______________________________________________ Yt-dev mailing list Ytemail@example.com http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org