It is possible to configure configure so that maintainer mode needs to be
enabled explicitly (by passing --enable-maintainer-mode):
AM_MAINTAINER_MODE([disable])
-- Boyce
> On Feb 26, 2016, at 2:29 PM, Derek Gaston wrote:
>
> That did it Cody - thanks!
>
> I will, of course, use this to poin
On Mar 17, 2014, at 1:51 PM, John Peterson wrote:
>
>
>
> On Mon, Mar 17, 2014 at 11:11 AM, Boyce Griffith
> wrote:
> I was wondering if I could get some information about how an installed build
> of libMesh expects to interact with the bundled libraries --- and
I was wondering if I could get some information about how an installed build of
libMesh expects to interact with the bundled libraries --- and specifically
with NetCDF. Is -lmesh_METHOD meant also to provide all of the archives for
the contrib libraries, or are there some special cases?
The re
On 6/3/13 12:28 PM, Roy Stogner wrote:
>
> On Mon, 3 Jun 2013, Lorenzo Alessio Botti wrote:
>
>> it seems that the issue was due to a missing header file in Hilbert.hpp
>>
>> After adding
>> #include "Hilbert/Algorithm.hpp"
>> everything went fine.
>> I think the compiler was right since Algorith
On 12/10/12 2:00 PM, Roy Stogner wrote:
> I'm currently looking at the parallel-correctness problems Ataollah
> Mesgarnejad and Vikram Garg are having, and it appears that the simple
> workaround for both of them involves sticking the right
> ghosted_vector.localize(ghosted_vector) call in the ri
On 10/25/12 9:30 PM, Kirk, Benjamin (JSC-EG311) wrote:
>
> On Oct 25, 2012, at 7:53 PM, Boyce Griffith wrote:
>
>> On 10/25/12 6:49 PM, Roy Stogner wrote:
>>> On second thought, this idea gets less stupid if your "buddy" isn't a
>>> human being.
On 10/25/12 6:49 PM, Roy Stogner wrote:
> On second thought, this idea gets less stupid if your "buddy" isn't a
> human being. We could always do what a lot of other projects do and
> auto-upload a "nightly" snapshot. The last thing BuildBot could do
> after a revision passes all tests is "make
On 10/25/12 3:52 PM, Boyce Griffith wrote:
>
>
> On 10/25/12 3:43 PM, Lorenzo Botti wrote:
>> http://epubs.siam.org/doi/abs/10.1137/110830125
>> I guess you already know this work...
>
> Yep. Is there actually any code available for Blaze yet?
Turns
On 10/25/12 3:43 PM, Lorenzo Botti wrote:
> http://epubs.siam.org/doi/abs/10.1137/110830125
> I guess you already know this work...
Yep. Is there actually any code available for Blaze yet?
Blitz++ is really an array class library. Although you can do dense
linear algebra with it, that's not
On 10/25/12 2:34 PM, Roy Stogner wrote:
>
>
> On Thu, 25 Oct 2012, Boyce Griffith wrote:
>
>> Is it even possible to have the shim class use operator[] for
>> multidimensional indexing ([i][j])? I don't know how you setup an
>> equivalent to "operator
On 10/25/12 1:58 PM, Roy Stogner wrote:
>
> On Thu, 25 Oct 2012, Roy Stogner wrote:
>
>> The first thing to do would be creating a shim class API
>
> Actually, should the first thing be something like:
>
> template
> typedef std::vector LibMesh1Array;
>
> template
> typedef std::vector > LibMes
On 10/25/12 2:21 PM, Roy Stogner wrote:
>
> On Thu, 25 Oct 2012, Boyce Griffith wrote:
>
>> Libraries like Eigen and Blitz++ use operator() for accessors rather
>> than operator[]. How horrible would it be to go ahead and change to
>> operator() when making t
On 9/20/12 11:53 AM, Cody Permann wrote:
> GNU GCC: This is probably our best option. The question is, do we build
> it from source, download binaries, or get it through Fink/Mac Ports?
> There are various advantages/disadvantages to each of these. Paul,
> you've been using GNU GCC (as opposed
On 5/10/12 7:05 PM, Roy Stogner wrote:
>
> On Thu, 10 May 2012, Boyce Griffith wrote:
>
>> Is it feasible to template over the return type in FEBase and then
>> have the derived classes pick either scalar or vector versions?
>
> Hmm... yes, actually. We'd need som
On 2/20/12 4:41 PM, Kirk, Benjamin (JSC-EG311) wrote:
> Plus, moving to a proper libtool installation will help in the future with
> shared libraries on multiple platforms (yeah, looking at you OSX).
Several years ago, I spent a lot of time trying to get
libtool+autoconf+automake to work on the
On 11/9/11 5:02 PM, Roy Stogner wrote:
>
> On Wed, 9 Nov 2011, Boyce Griffith wrote:
>
>> Not sure if this is really a bug that needs to be fixed
>
> It wasn't a correctness bug, but it was a potential efficiency bug.
> See if my new tweak to the svn head fixes it?
S
Not sure if this is really a bug that needs to be fixed, but with
periodic boundary conditions, I have been tripping this warning:
*** Warning, This code is deprecated, and likely to be removed in future
library versions! src/mesh/mesh_base.C, line 297, compiled Nov 9 2011
at 14:40:13 ***
I t
On 10/5/11 6:29 PM, Boyce Griffith wrote:
> I was wondering if FE::reinit() in fe_boundary.C for sides and edges
> should/could force reinitialization when qrule->shapes_need_reinit() is
> true, as is done in FE::reinit() in fe.C. I'm attaching a simple patch
> to this e
I was wondering if FE::reinit() in fe_boundary.C for sides and edges
should/could force reinitialization when qrule->shapes_need_reinit() is
true, as is done in FE::reinit() in fe.C. I'm attaching a simple patch
to this email that makes this change.
Thanks,
-- Boyce
Index: src/fe/fe_boundary
On 8/10/11 12:16 PM, Roy Stogner wrote:
>
> On Wed, 10 Aug 2011, John Peterson wrote:
>
>> A problem I see with this (other than adding a lot of code just to
>> silence the compiler) is that it won't be maintained by all (any?) of
>> the developers.
>>
>> I for one do not plan to add extra warnin
n Elem*
> for reinitialization... so you would have to do something like this no matter
> what.
>
> Let me know if that doesn't make sense.
>
> If you have a better way let me know.
>
> Derek
>
> On Jun 29, 2011, at 1:25 PM, Boyce Griffith wrote:
>
>> I am
I am trying to setup an adaptive quadrature rule that will use different
quadrature points/weights on different elements in the mesh. (In this
particular application, the number of quadrature points depends on the
size of the element.)
I am not sure how to get this to work, because QBase::ini
On 6/16/11 2:00 PM, Derek Gaston wrote:
>
> On Jun 16, 2011, at 11:46 AM, Roy Stogner wrote:
>
>> I'm just saying that, even if we do make the switch, you should
>> upgrade your compiler too. If it flubbed std::fill that badly then
>> there's probably lots of other stuff it's not optimizing as w
Here is a patch to make edge_reinit() behave like reinit(elem,side) in
terms of how it sets shapes_on_quadrature.
-- Boyce
On 5/3/11 11:53 AM, Boyce Griffith wrote:
What is going wrong with caching?
Looking at line 178 of fe_boundary.C:
// The shape functions correspond to the qrule
> I can confirm that this change fixes the segfault in ex0.
>>
>> Checking our other regression tests now...
>>
>> --
>> John
>>
>>
>> On Tue, May 3, 2011 at 9:25 AM, Boyce Griffith
>> wrote:
>>> G, looks like there was
G, looks like there was a bug in the patch (which I am surprised
didn't cause me any problems).
Index: src/fe/fe_boundary.C
===
--- src/fe/fe_boundary.C(revision 4447)
+++ src/fe/fe_boundary.C(working copy)
@@
On 4/18/11 7:00 PM, Roy Stogner wrote:
>
> On Mon, 18 Apr 2011, Boyce Griffith wrote:
>
>> I need FE::reinit() to work at arbitrary locations for the side
>> version of reinit(). Attached is a patch that adds this functionality
>> for both the side version of reinit
Hi, Folks --
I need FE::reinit() to work at arbitrary locations for the side version
of reinit(). Attached is a patch that adds this functionality for both
the side version of reinit() and for edge_reinit(). I wasn't completely
sure what to do for the InfFE case for the side case, so in the
On 3/14/11 2:51 PM, Boyce Griffith wrote:
>
>
> On 3/14/11 2:11 PM, John Peterson wrote:
>> On Mon, Mar 14, 2011 at 12:04 PM, Boyce
>> Griffith wrote:
>>> Crap, that is totally what is happening. I use my own build system,
>>> and I
>>> did n
On 3/14/11 2:11 PM, John Peterson wrote:
> On Mon, Mar 14, 2011 at 12:04 PM, Boyce Griffith
> wrote:
>> Crap, that is totally what is happening. I use my own build system, and I
>> did not realize that I needed to set -DDEBUG manually. Adding that flag
>> fixes
Crap, that is totally what is happening. I use my own build system, and
I did not realize that I needed to set -DDEBUG manually. Adding that
flag fixes everything.
-- Boyce
On 3/14/11 1:55 PM, Roy Stogner wrote:
> That mesh_base.h change should indeed break in crazy crazy ways if
> it's used
Crap, that is totally what is happening. I am not using the libMesh
build system; I am using my own, and I did not realize that I needed to
be including -DDEBUG.
-- Boyce
On 3/14/11 1:55 PM, Roy Stogner wrote:
> That mesh_base.h change should indeed break in crazy crazy ways if
> it's used to
To keep thing simple, I updated to 4247 and then updated only
mesh_base.h to 4248:
==
boyce-griffiths-mac-pro:libmesh-petsc-3.1 griffith$ svn diff -r4247
Index: include/mesh/mesh_base.h
==
Yes, GCC 4.4.4 from Fink, running on OS X 10.5.8.
On 3/14/11 1:46 PM, John Peterson wrote:
> Boyce,
>
> I've attached the diffs between 4247 and 4248 below.
>
> In the sources, could you try commenting out all the new calls to
> libmesh_assert_valid_parallel_ids();
>
> This should still crash, at
You folks don't have a valgrind build handy by any chance...?
-- Boyce
On 3/14/11 1:08 PM, John Peterson wrote:
> On Mon, Mar 14, 2011 at 11:03 AM, Roy Stogner
> wrote:
>>
>> On Mon, 14 Mar 2011, Boyce Griffith wrote:
>>
>>> OK, it looks like this was
#12 0x2b66 in main (argc=1, argv=0xbfffe0d8) at main.C:14
On 3/14/11 12:46 PM, Boyce Griffith wrote:
> OK, it looks like this was introduced in r4248.
>
> On 3/14/11 12:41 PM, Roy Stogner wrote:
>>
>> Thanks. This is looking like one hell of a bug - John tells me that
>>
ry it on a couple
> different computers.
> ---
> Roy
>
> On Mon, 14 Mar 2011, Boyce Griffith wrote:
>
>> In the meantime, I will try to find the rev at which this starts
>> happening.
>>
>> On 3/14/11 12:23 PM, Roy Stogner wrote:
>>>
>>>
In the meantime, I will try to find the rev at which this starts happening.
On 3/14/11 12:23 PM, Roy Stogner wrote:
>
> Hell, that simple I'll check it out ASAP.
>
> Thanks,
> ---
> Roy
>
> On Mon, 14 Mar 2011, Boyce Griffith wrote:
>
>> Here
On 3/14/11 8:15 AM, Boyce Griffith wrote:
>
>
> On 3/14/11 1:15 AM, Roy Stogner wrote:
>>
>> reproduce it; if not then the only way to pin it down is for you to
>> binary-search back through the svn log. :-P
>
> I'll see what I can come up with.
Here
On 3/14/11 1:15 AM, Roy Stogner wrote:
>
> On Mon, 14 Mar 2011, Boyce Griffith wrote:
>
>> The error is apparently still there in r4245.
>
> Hmmm... variant_filter_iterator.h didn't change at all between r4168
> (Jan 13) and r4246, and none of these changes have bee
d_cube
>> (mesh=@0xbfffd79c, nx=56, ny=2, nz=0, xmin=0, xmax=1.5707963267948966,
>> ymin=0, ymax=0.0625, zmin=0, zmax=0, type=libMeshEnums::QUAD4,
>> gauss_lobatto_grid=false) at src/mesh/mesh_generation.C:1438
>> #11 0x00d59d5e in libMesh::MeshTools::Generation::build_s
On 3/14/11 12:36 AM, Roy Stogner wrote:
>
> On Sun, 13 Mar 2011, Boyce Griffith wrote:
>
>> These look like namespace issues --- if I change libmesh_cast_ptr to
>> libMesh::cast_ptr, everything works fine.
>
> You mean libMesh::libmesh_cast_ptr, I assume?
67948966, ymin=0,
ymax=0.0625, type=libMeshEnums::QUAD4, gauss_lobatto_grid=false) at
src/mesh/mesh_generation.C:1501
#12 0x4a26 in main (argc=2, argv=0xbfffe004) at
../../../../../IBAMR/examples/IBFE/explicit/ex1/main.C:355
On 3/13/11 10:55 PM, Boyce Griffith wrote:
> Hi, Guys --
>
> I j
Hi, Guys --
I just updated to the latest svn HEAD, and I am now getting compiler
errors in my application code like:
/Users/griffith/sfw/libmesh/include/base/variant_filter_iterator.h:204:
error: ‘libmesh_cast_ptr’ was not declared in this scope
/Users/griffith/sfw/libmesh/include/base/variant
Hi, Folks --
There appears to be a missing #include in periodic_boundaries.h.
-- Boyce
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect
urprised if you're seeing
> it for 2D meshes (where IIRC we build quadtrees instead of octrees)
> and I'm surprised that I've never seen it for 1D meshes...
>
> Sounds like a straightforward solution, though; someone want to glance
> over and commit it?
> ---
> R
Hi, Folks --
We recently ran into a floating point exception coming from
location_maps.C. The problem is that when LIBMESH_DIM is 3 but the mesh
has DIM < 3, _lower_bound[i] == _upper_bound[i] for some dimensions.
Because LocationMap::key() computes, e.g.,
zscaled = (p(2) - _lower_bound[2
On 12/2/10 5:27 PM, Roy Stogner wrote:
> There are nearly ONE HUNDRED THOUSAND lines of changes. No way are we
> looking over every one of them. Does everyone want to trust that
> astyle doesn't break any C++, or that our regression and unit tests
> have enough coverage to catch any breakage?
Al
On 12/2/10 8:03 PM, Boyce Griffith wrote:
> Hi, Folks --
>
> I'm trying to add support for inhomogeneous DOF constraints to DofMap. I
> think I am almost there --- if I add the constraints after calling
> init(), everything appears to work. These constraints are quite simple
Hi, Folks --
I'm trying to add support for inhomogeneous DOF constraints to DofMap.
I think I am almost there --- if I add the constraints after calling
init(), everything appears to work. These constraints are quite simple
--- they are just inhomogeneous Dirichlet boundary conditions. I've
On 12/2/10 1:11 PM, Roy Stogner wrote:
>
> On Thu, 2 Dec 2010, Boyce Griffith wrote:
>
>> OK --- attached is a patch. Most of it is just re-indenting. (I wasn't
>> always careful about using tabs instead of spaces --- is there a
>> convention that you all prefer
On 12/2/10 10:17 AM, Roy Stogner wrote:
On Thu, 2 Dec 2010, Boyce Griffith wrote:
If you agree, I'm happy to send a patch.
Thanks! That would be great.
OK --- attached is a patch. Most of it is just re-indenting. (I wasn't
always careful about using tabs instead of spaces --
On 11/16/10 2:24 PM, Derek Gaston wrote:
> On Nov 16, 2010, at 10:27 AM, Boyce Griffith wrote:
>
>> Is adding qrule->need_reinit() the only change that you are making to QBase?
>> I am probably missing something, but it seems like allowing the quadrature
>> r
On 12/1/10 9:31 PM, Roy Stogner wrote:
>
> Did you really managed to get overlapping BC IDs working with a
> dozen-line patch? Egg on our faces... I don't think any of the
> primary developers use multiple IDs on the same boundary right now,
> but if we'd known it would be that simple to support t
Hi, Folks --
I noticed that adding multiple boundary IDs to the boundary_info object
caused an assertion to fail in xdr_io::write_serialized_bcs() at line
740 of xdr_io.C, which asserts that n_bcs == n_bcs_out.
Looking at the code that packs up the IDs, it appears that only the
first boundary
On 11/22/10 12:59 PM, Roy Stogner wrote:
>
> On Mon, 22 Nov 2010, Boyce Griffith wrote:
>
>> FWIW --- the g++ compiler option -Weffc++ can be helpful for tracking
>> down this kind of stuff --- it will emit warnings about classes that
>> violate some of the coding
On 11/22/10 12:33 PM, Roy Stogner wrote:
>
> On Mon, 22 Nov 2010, John Peterson wrote:
>
>> So... I'm wondering if we should do something similar (disable op= and
>> copy ctor unless needed and explicitly provided, possibly with a
>> macro) in all of our library classes?
>
> So a bunch of potenti
On 11/15/10 3:40 PM, Derek Gaston wrote:
> On Nov 15, 2010, at 3:38 PM, John Peterson wrote:
>
>> Are we married to the "has_constant_positions()" name? Maybe
>> something like qrule->need_reinit() in the vein of
>> FE::shapes_need_reinit(). Just thinking there might potentially be
>> other rea
On 6/21/10 1:49 PM, John Peterson wrote:
> On Mon, Jun 21, 2010 at 11:35 AM, Roy Stogner
> wrote:
>> I'd been kind of hoping that we'd be able to get away with the same in
>> library code (in our .C files, albeit not our .h files), but I guess
>> if even PETSc might have new encroaching identif
On 6/2/10 6:03 PM, Roy Stogner wrote:
>
> On Wed, 2 Jun 2010, Boyce Griffith wrote:
>
>> On 6/2/10 3:52 PM, Boyce Griffith wrote:
>>
>> Alternatively, I wonder if the interface might be clearer if assembly
>> and ghost-filling were separate member functions, a
I'd love to see VisIt become the libMesh viewer of choice! However,
right now, it seems like most of the output formats supported by libMesh
do not play well with VisIt. I spent the better part of an afternoon
several months back trying to get VisIt to read the VTK files generated
by libMesh
>> Can't you just call clear() in ~MyPreconditioner()?
>
> Sure, I can. Actually, that's what I'm doing now. But for that,
> still the method Preconditioner::clear() does not have to exist, does
> it?
I haven't used the Preconditioner class in libMesh, but this kind of
init()/clear() functio
to start at 1 for numbering... But its just that: a hack. It won't be
> commited. What I have on my list to do is to turn ids of 0 to MAX_ID
> when output... That way the examples will work. If I get a minute I'll
> try to do that today.
>
> Sorry about the trouble.
&g
Hi, Folks --
I am trying to get libMesh to output to an Exodus II file. I am using a
recent pull of the SVN version of libMesh so that I can use libMesh with
PETSc 3.0.0.
(By the way, I don't really care whether it is Exodus II or not --- I am
just trying to output data in a format which can
64 matches
Mail list logo
