Dear libMesh devs,
the roots of the finite element method lie in structural analysis and
the need to solve elasticity problems. Thin shells with a stretching and
a bending rigidity are an extremely important special case. The bending
term requires C1 finite elements which have been hard to cons
Others may also be interested in this, but I have a keen interest. I'd be
happy to look at the patch, but, even better, would be for you to open a
pull request on GitHub (https://github.com/libMesh/libmesh) so that, if we
decide to integrate the patch, we have a commit history of your development
s
Agreed!
And if you're not comfortable generating the pull request I could help - if
you send along the patch I can try and break it up into number of smaller
changes on a new branch, and we can start discussion.
-Ben
On Feb 21, 2014, at 10:20 AM, Paul T. Bauman wrote:
> Others may also be in
I'd definitely be enthusiastic about getting support for shells in
libMesh as well.
David
On 02/21/2014 11:20 AM, Paul T. Bauman wrote:
Others may also be interested in this, but I have a keen interest. I'd
be happy to look at the patch, but, even better, would be for you to
open a pull requ
Another vote for shells - this would be super handy...
Derek
On Fri, Feb 21, 2014 at 9:55 AM, David Knezevic
wrote:
> I'd definitely be enthusiastic about getting support for shells in
> libMesh as well.
>
> David
>
>
>
> On 02/21/2014 11:20 AM, Paul T. Bauman wrote:
>
> Others may also be int
All,
I got pissed off at all other continuous integration capabilities so I
wrote my own. It's currently hosted at moosebuild.com (you can go there,
but please don't sign in yet because everything isn't finalized and I don't
want you to lose anything you do on there - not too mention that all of
I'll also make it run a "make check" - I forgot to mention that part. We
can expand from there later...
On Friday, February 21, 2014, Derek Gaston wrote:
> All,
>
> I got pissed off at all other continuous integration capabilities so I
> wrote my own. It's currently hosted at moosebuild.com (y
I've got no issues - as for the clients, does the server communicate out or
wait to be polled? I ask because I've got some client resources, but they are
behind a firewall and can't just listen on a random port... They could
periodically poll out though.
Looks interesting!
I take it you've
Clients poll (simply http requests on port 80). That was important to us
for the same reason (and one of the reasons I don't like some of the other
CI systems).
Not just buildbot. Here's a list of systems we tried/looked at and their
issues:
- BuildBot
- client in constant connection with ser
Whoops - sent too early
- Jenkins
- Ugly
- Java (I could probably stop there)
- Crappy client (requires fairly specific versions of Java files and has
flaky connection issues)
- Bad interface for custom build scripts
- Really made for testing Java web-apps
- Did I mention it's ugly and
10 matches
Mail list logo
