You'll need to tell us more about what you're doing. I just tested Daniel's scripts, running the one at http://pastebin.com/p5rARUJf with `mpirun -np 2` and then running the one at http://pastebin.com/P883d0q4 in serial and it works fine.
On Mar 22, 2013, at 5:12 PM, Adrian Jacobo wrote: > Hi Daniel, > > Thanks for your help. I've just had time to try the code you sent, and I > still have the same problem. The script is able to read the data in the > string (gmshString) without problems, but when it tries to create the > variable u using the data saved in the file it consumes all the available > memory in the system and crashes. > > Cheers, > Adrian. >> >> On Mon, Mar 18, 2013 at 1:22 PM, Adrian Jacobo >> <[email protected]> wrote: >> Hi, >> >> I'm having problems when saving results of a calculation on a Gmsh grid >> when running in parallel. >> >> Hi Adrian, >> >> Pickling Gmsh meshes is profoundly broken in parallel. It just doesn't work. >> At this point, Gmsh mesh objects should raise an exception when pickled in >> parallel until/if FiPy can ever handle this properly. >> >> One way to get around the issue, is to pickle the simpler array and string >> objects and then use them to reconstruct the mesh and variable. This is >> hardly a persistent method for data storage, but pickling in general with >> complicated objects seems to be fraught with problems. In my own experience, >> I tend to use lower level objects for pickling when possible. I fixed your >> code to do this, see http://pastebin.com/p5rARUJf and >> http://pastebin.com/P883d0q4. >> >> Cheers >> > > <ATT00001.c> _______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
