Re: [Libmesh-devel] Data format documentation

2007-11-26 Thread Martin Lüthi
Hi Roy Stogner writes: > Do you have any specific files or URLs you think we should add? This > is definitely a good idea, but I bet nobody's going to get around to > it until the next time we're stuck hunting up documentation ourselves. > If you've been through that wringer yourself recently

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread John Peterson
OK, It appears that the libmesh SVN repository has become corrupted in an early version, and I have no idea how this could have happened, or how to fix it. I have a request in to the sourceforge support system, but there's no telling how long it might take them to fix the problem, or if they can f

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread Roy Stogner
On Mon, 26 Nov 2007, John Peterson wrote: > Interesting. At 492K, this appears to be the largest of the tecio.a > libraries that we have checked into the repository. At first I thought sf.net > might just be under heavy load, but it's surprising that it dies on the same > file > for both of us.

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread John Peterson
If you try to check out from non-secure http, you get a slightly different error message : svn: REPORT request failed on '/svnroot/libmesh/!svn/vcc/default' svn: REPORT of '/svnroot/libmesh/!svn/vcc/default': 200 OK (http://libmesh.svn.sourceforge.net) It looks like others using sourceforge htt

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread John Peterson
Interesting. At 492K, this appears to be the largest of the tecio.a libraries that we have checked into the repository. At first I thought sf.net might just be under heavy load, but it's surprising that it dies on the same file for both of us. The file itself has been in the repo since 2004. -

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread Roy Stogner
On Mon, 26 Nov 2007, John Peterson wrote: > Still not gone for me. If you try a fresh checkout, see if it dies right > after downloading the ia64 tecplot binary. It dies right before downloading that binary, after creating the directory it goes in: ... Alibmesh/contrib/tecplot/lib/ia64-unkn

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread John Peterson
Roy Stogner writes: > On Mon, 26 Nov 2007, John Peterson wrote: > > > Upon trying to check out a fresh copy libmesh, I get: > > > > svn co https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh > > > > svn: REPORT request failed on '/svnroot/libmesh/!svn/vcc/default' > > svn: RE

Re: [Libmesh-devel] SVN repo

2007-11-26 Thread Roy Stogner
On Mon, 26 Nov 2007, John Peterson wrote: > Upon trying to check out a fresh copy libmesh, I get: > > svn co https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh > > svn: REPORT request failed on '/svnroot/libmesh/!svn/vcc/default' > svn: REPORT of '/svnroot/libmesh/!svn/vcc/default':

Re: [Libmesh-devel] ParallelMesh & 0.6.9/0.7.0

2007-11-26 Thread Roy Stogner
On Mon, 26 Nov 2007, Benjamin Kirk wrote: > So I hear you two should be hammering the library now -- both the > Serial and Parallel Meshes... Right? That's the plan. I'm swamped with other work, but I'm getting some big runs started in the lab tonight and I should be submitting jobs on Lonestar

[Libmesh-devel] SVN repo

2007-11-26 Thread John Peterson
Upon trying to check out a fresh copy libmesh, I get: svn co https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh svn: REPORT request failed on '/svnroot/libmesh/!svn/vcc/default' svn: REPORT of '/svnroot/libmesh/!svn/vcc/default': Could not read chunk delimiter: Secure connection t

[Libmesh-devel] ParallelMesh & 0.6.9/0.7.0

2007-11-26 Thread Benjamin Kirk
So I hear you two should be hammering the library now -- both the Serial and Parallel Meshes... Right? I'm redoing the EquationSystems IO to be able to read/write restart files in parallel on a distributed memory mesh without serializing it. This should allow for a parallel simulation to dump re

Re: [Libmesh-devel] Data format documentation

2007-11-26 Thread Roy Stogner
On Sat, 24 Nov 2007, Martin Lüthi wrote: Libmesh supports a wide variety of data formats. For some formats the documentation is easily accessible, but for some (e.g. UNV) one has to hunt down some description of the file format. I think that it should be mandatory to put the file definitions in

Re: [Libmesh-devel] Possible n^2 algorithm in mesh.write() ?

2007-11-26 Thread John Peterson
I do remember it. I thought we had checked it in and so I figured that couldn't *still* be the problem. Oh well. -J Derek Gaston writes: > Hehe... > > John... do you remember that you and I already did this once back when > I was working on my thesis? I was seeing the same problem of writi

Re: [Libmesh-devel] Possible n^2 algorithm in mesh.write() ?

2007-11-26 Thread Derek Gaston
Hehe... John... do you remember that you and I already did this once back when I was working on my thesis? I was seeing the same problem of writing from every node... and we dug down there and put a bunch of those statements in. I guess it never actually got checked in though and I'm not eve

Re: [Libmesh-devel] Data format documentation

2007-11-26 Thread Derek Gaston
Hmmm... not a bad idea. I'll put the Exodus documentation over into the doc tree soon. Derek On Nov 24, 2007 4:32 AM, Martin Lüthi <[EMAIL PROTECTED]> wrote: > Hi > > Libmesh supports a wide variety of data formats. For some formats the > documentation is easily accessible, but for some (e.g. UN

Re: [Libmesh-devel] Possible n^2 algorithm in mesh.write() ?

2007-11-26 Thread John Peterson
OK, so it's not an n^2 algorithm, but XdrIO::write() currently gets called on all CPUs, and so all of them try to write to the same file at the same time. Turns out this is a lot more noticeable on 128 CPUs than it is on 4... The fix should be to wrap the call to write in if (processor_id==0) as