Re: [Libmesh-users] Recommend an open-source software to generate complex FE mesh

2013-01-03 Thread walter kou
Hi all, But when I try to run gmsh: ./gmsh, I get error on missing libraries. And after using command: ldd gmsh, I find missing libraries: libgmp.so.3 => not found libgfortran.so.3 => not found My computer: fedora 17 x86_64; and actually if I type: locate libgfortran.so.3, I find I have l

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
On Thu, Jan 3, 2013 at 2:24 PM, Roy Stogner wrote: > I didn't know that; thanks. I agree completely. I'm still not even > entirely certain whether it's a good idea to use an interactive rebase > to squash the occasional "commit N" and "commit N+1 fixing the bug > just introduced by commit N" tog

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
Damon, Thanks for the email... always good to see what others are doing! What I'm advocating is _never_ using "git pull" and never having "merge commits". If no one ever uses straight "git pull" things are much better (even for public branches, but that can still give you issues). Instead, ever

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
On Thu, Jan 3, 2013 at 2:20 PM, Roy Stogner wrote: > > But note that periodically rebasing a shared branch should probably be > > frowned upon, since that involves rewriting history (and push -f), and > > may affect others... > > This is half of my trepidation. Before using git, in my imagination

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Roy Stogner
On Thu, 3 Jan 2013, Derek Gaston wrote: Oh - I also don't like "--no-ff" for merging.  It essentially "squashes" a bunch of commits into one... which I think is a bad idea. I didn't know that; thanks. I agree completely. I'm still not even entirely certain whether it's a good idea to use an

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Roy Stogner
On Thu, 3 Jan 2013, John Peterson wrote: > It's an alternative to doing periodic merges (as e.g. Ben did with his > recent meshfree interpolation branch). Yup. And even with things like "git log --no-merges", the result of those seems to be slightly annoying. When experimenting with "master ad

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
Oh - I also don't like "--no-ff" for merging. It essentially "squashes" a bunch of commits into one... which I think is a bad idea. Git is all about working with tons of patches... and being able to swap them in and out of branches. If you squash them together you lose a _ton_ of flexibility. T

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
On Thu, Jan 3, 2013 at 1:58 PM, John Peterson wrote: > I looked at this diagram for a while, and I like it, other than I > probably wouldn't make such a big distinction between the yellow and > green dots... > > Feature (pink) branches periodically merge into develop, every once in > a while deve

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread John Peterson
On Thu, Jan 3, 2013 at 1:04 PM, Roy Stogner wrote: > > (Cc:ing the PECOS local git expert) > > On Wed, 12 Dec 2012, Derek Gaston wrote: > >> Let's just move to Git and work in master for a little while and let >> everyone catch their breath... > > Although I am still very much mired in the "catchi

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Derek Gaston
On Thu, Jan 3, 2013 at 1:04 PM, Roy Stogner wrote: > (I'm still not certain under what-if-any conditions "rebase" is a good > idea, for example) "rebase" is what you want to use to "update" your branch and "stack" your patches on top of whatever other work happened in another branch. This is es

Re: [Libmesh-users] [Libmesh-devel] libMesh now on GitHub!

2013-01-03 Thread Roy Stogner
(Cc:ing the PECOS local git expert) On Wed, 12 Dec 2012, Derek Gaston wrote: > Let's just move to Git and work in master for a little while and let > everyone catch their breath... Although I am still very much mired in the "catching my breath" stage (I'm still not certain under what-if-any con

[Libmesh-users] Upcoming backwards-incompatible API change to FEMSystem::mass_residual()

2013-01-03 Thread Roy Stogner
To do a decent stabilized problem with nonlinearities on the time derivative term, our mass_residual() functions ought to have access to the current element solution u(t) at the simulation-time being evaluated, a fixed element solution u_f which is constant from t_n to t_{n+1}, and some measure o

Re: [Libmesh-users] Recommend an open-source software to generate complex FE mesh

2013-01-03 Thread John Peterson
On Thu, Jan 3, 2013 at 8:48 AM, walter kou wrote: > Hi Derek, > Thanks for your reply. The FE mesh in my current application, though it is > 3D, will not be "really complex" as shown in the website of Cubit. While I > find Gmsh from Libemsh-wiki website looks good. Could Gmsh prepare FE mesh > for

Re: [Libmesh-users] Recommend an open-source software to generate complex FE mesh

2013-01-03 Thread walter kou
Hi Derek, Thanks for your reply. The FE mesh in my current application, though it is 3D, will not be "really complex" as shown in the website of Cubit. While I find Gmsh from Libemsh-wiki website looks good. Could Gmsh prepare FE mesh for libmesh? If so, what kind of files will Gmsh generate for li