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

On Wed, Dec 12, 2012 at 11:04 AM, Roy Stogner wrote: > Nick Malaya set up something similar over here with the TACC systems - > longhorn.tacc builds and tests our manufactured solution library MASA > with the Portland Group compilers, and reports the results back to our > "master" server where it

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 10:04 PM, Kirk, Benjamin (JSC-EG311) wrote: > On Dec 12, 2012, at 6:35 PM, Jens Lohne Eftang wrote: > >>> and repeat your experiment, replying with the results again for the first >>> three nodes, also with the >>> node->debug_buffer() as before? >>> >>> I'd expect system 0, vars 0,

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Dec 12, 2012, at 6:35 PM, Jens Lohne Eftang wrote: >> >> and repeat your experiment, replying with the results again for the first >> three nodes, also with the >> node->debug_buffer() as before? >> >> I'd expect system 0, vars 0,1,2 to have ids 0, 96, and 192, respectively, >> from this b

Re: [Libmesh-users] XDR read bug with C1 elements

On Wed, 12 Dec 2012, Ataollah Mesgarnejad wrote: > On Dec 12, 2012, at 3:41 PM, Roy Stogner wrote: > >> Yes - that would only have worked if you'd already manually >> initialized every system and variable to match the solution file and >> then init()ed it. > I did this but still had the problem

Re: [Libmesh-users] XDR read bug with C1 elements

On Dec 12, 2012, at 3:41 PM, Roy Stogner wrote: > > On Tue, 11 Dec 2012, Ataollah Mesgarnejad wrote: > >> If I remove READ_HEADER read will try to load a vector from another >> system to this system and fails because the number of DOFs are >> different. > > Yes - that would only have worked i

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 06:17 PM, Kirk, Benjamin (JSC-EG311) wrote: > On Dec 12, 2012, at 4:11 PM, Jens Lohne Eftang wrote: > >> With revision 6524 it's still broken. Yep, I'm pulling from svn. > With r6524, will you please uncomment the section > >// std::cout << "base_idx, var, vg, vig, ncg, comp=

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

One more thing - you may want to put node->debug_buffer(); libmesh_error(); So you can force an abort to track down the output - uncommenting those lines will create a lot of noise on the console! -Ben On Dec 12, 2012, at 5:17 PM, "Kirk, Benjamin (JSC-EG311)" wrote: > On Dec 12, 2012, a

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Dec 12, 2012, at 4:11 PM, Jens Lohne Eftang wrote: > With revision 6524 it's still broken. Yep, I'm pulling from svn. With r6524, will you please uncomment the section // std::cout << "base_idx, var, vg, vig, ncg, comp=" //<< base_idx << " " //

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 05:09 PM, Kirk, Benjamin (JSC-EG311) wrote: > On Dec 12, 2012, at 3:52 PM, "Jens Lohne Eftang" wrote: > >> On 12/12/2012 04:31 PM, Kirk, Benjamin (JSC-EG311) wrote: >>> Sorry, the debug_buffer() is a new feature - from when I thought it was my >>> patch. ;-) >>> >>> Have you run thi

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Dec 12, 2012, at 3:52 PM, "Jens Lohne Eftang" wrote: > On 12/12/2012 04:31 PM, Kirk, Benjamin (JSC-EG311) wrote: >> Sorry, the debug_buffer() is a new feature - from when I thought it was my >> patch. ;-) >> >> Have you run this on debug mode? > Hmm, I must have messed something up when I ro

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 04:31 PM, Kirk, Benjamin (JSC-EG311) wrote: > Sorry, the debug_buffer() is a new feature - from when I thought it was my > patch. ;-) > > Have you run this on debug mode? Hmm, I must have messed something up when I rolled back to 6524 earlier. Now I did get debug_buffer() to work an

Re: [Libmesh-users] XDR read bug with C1 elements

On Tue, 11 Dec 2012, Ataollah Mesgarnejad wrote: > If I remove READ_HEADER read will try to load a vector from another > system to this system and fails because the number of DOFs are > different. Yes - that would only have worked if you'd already manually initialized every system and variable t

Re: [Libmesh-users] Fwd: EquationsSystems with two systems; node iteration

On 12/12/2012 04:37 PM, Andrs, David wrote: > On Wed, Dec 12, 2012 at 2:25 PM, Jens Lohne Eftang > wrote: > > On 12/12/2012 04:19 PM, Andrs, David wrote: > > On Wed, Dec 12, 2012 at 1:52 PM, Jens Lohne Eftang > mailto:jleft...@gmail.com>>wrote: > > >

Re: [Libmesh-users] Fwd: EquationsSystems with two systems; node iteration

On Wed, Dec 12, 2012 at 2:25 PM, Jens Lohne Eftang wrote: > On 12/12/2012 04:19 PM, Andrs, David wrote: > > On Wed, Dec 12, 2012 at 1:52 PM, Jens Lohne Eftang >wrote: > > > >> Hi all, > >> > >> I have an EquationSystems which holds two systems: > >> > >> EquationSystems es(mesh); > >> es.read(fil

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

Sorry, the debug_buffer() is a new feature - from when I thought it was my patch. ;-) Have you run this on debug mode? Reading the system from disk initialized the equation systems, and then you add another system? Conceptually this should work, but... That's what the asserts are there for!

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 04:11 PM, Kirk, Benjamin (JSC-EG311) wrote: > On Dec 12, 2012, at 3:07 PM, Roy Stogner wrote: > >> On Wed, 12 Dec 2012, Jens Lohne Eftang wrote: >> >>> The system that is read from file has three variables. Now, when I >>> iterate of the nodes of mesh, and do >>> >>> index_0 = node->

Re: [Libmesh-users] Fwd: EquationsSystems with two systems; node iteration

On 12/12/2012 04:19 PM, Andrs, David wrote: > On Wed, Dec 12, 2012 at 1:52 PM, Jens Lohne Eftang wrote: > >> Hi all, >> >> I have an EquationSystems which holds two systems: >> >> EquationSystems es(mesh); >> es.read(filename), >> READ, >> EquationSystems::READ_HEA

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On 12/12/2012 04:07 PM, Roy Stogner wrote: > On Wed, 12 Dec 2012, Jens Lohne Eftang wrote: > >> The system that is read from file has three variables. Now, when I >> iterate of the nodes of mesh, and do >> >> index_0 = node->dof_number(0, i, 0); >> index_1 = node->dof_number(0,0,0); >> >> I alwas g

[Libmesh-users] Fwd: EquationsSystems with two systems; node iteration

On Wed, Dec 12, 2012 at 1:52 PM, Jens Lohne Eftang wrote: > Hi all, > > I have an EquationSystems which holds two systems: > > EquationSystems es(mesh); > es.read(filename), > READ, > EquationSystems::READ_HEADER | > EquationSystems::READ_DATA | >

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Wed, Dec 12, 2012 at 2:07 PM, Roy Stogner wrote: > > On Wed, 12 Dec 2012, Jens Lohne Eftang wrote: > >> The system that is read from file has three variables. Now, when I >> iterate of the nodes of mesh, and do >> >> index_0 = node->dof_number(0, i, 0); >> index_1 = node->dof_number(0,0,0); >>

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Dec 12, 2012, at 3:07 PM, Roy Stogner wrote: > On Wed, 12 Dec 2012, Jens Lohne Eftang wrote: > >> The system that is read from file has three variables. Now, when I >> iterate of the nodes of mesh, and do >> >> index_0 = node->dof_number(0, i, 0); >> index_1 = node->dof_number(0,0,0); >> >

Re: [Libmesh-users] EquationsSystems with two systems; node iteration

On Wed, 12 Dec 2012, Jens Lohne Eftang wrote: > The system that is read from file has three variables. Now, when I > iterate of the nodes of mesh, and do > > index_0 = node->dof_number(0, i, 0); > index_1 = node->dof_number(0,0,0); > > I alwas get index_0==index_1 also when i = 1,2. I assume you

[Libmesh-users] EquationsSystems with two systems; node iteration

Hi all, I have an EquationSystems which holds two systems: EquationSystems es(mesh); es.read(filename), READ, EquationSystems::READ_HEADER | EquationSystems::READ_DATA | EquationSystems::READ_ADDITIONAL_DATA); System & sys = es.add_

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

Sorry I'm late to the party, been in bed with the flu all day. On Dec 12, 2012, at 11:27 AM, Derek Gaston wrote: > Also, I have some libMesh changes that I'm going to be making today, so I was > thinking about my Git workflow a little bit. I think even _I_ am going to > clone the libMesh Git r

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

On Dec 12, 2012, at 12:04 PM, Roy Stogner wrote: >> >> Also, I have some libMesh changes that I'm going to be making today, >> so I was thinking about my Git workflow a little bit. I think even >> _I_ am going to clone the libMesh Git repo on GitHub over into my >> own workspace and work on my

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

On Wed, 12 Dec 2012, Roy Stogner wrote: > Ben and I (at least) haven't been getting the automatic emails that > libMesh pull requests are supposed to generate; you might want to ping > -devel at the same time until we get that sorted out. Never mind; looks like John figured out the problem. ---

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

On Wed, 12 Dec 2012, Derek Gaston wrote: Sounds good.  Is there any way we could run a build bot "slave" (I don't know the BuildBot parlance) here at INL that would report our test status back to your Build Bot server?  If so, we could definitely set that up. Nick Malaya set up something simi

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

On Wed, Dec 12, 2012 at 9:32 AM, Kirk, Benjamin (JSC-EG311) wrote: > On Dec 12, 2012, at 9:28 AM, John Peterson > wrote: > >> The development branch can be periodically merged into stable, perhaps >> automatically by buildbot whenever tests pass. >> >> So core developers would primarily work wit

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

On Wed, Dec 12, 2012 at 10:17 AM, Roy Stogner wrote: > The PECOS CI server actually is publicly accessible. It's so hammered > right now that I'd rather not subject its interface to even more usage > until we get some new hardware going, but email me privately if you > want the URL to peek at occ

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

On Dec 12, 2012, at 11:17 AM, Roy Stogner wrote: > On Wed, 12 Dec 2012, Derek Gaston wrote: > >> I am not against this model... (it is VERY close to how we do things >> with MOOSE... and our "stable merge" is automated by Bitten) >> however, can we have a small "cooling off" period for a moment

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

On Wed, 12 Dec 2012, Derek Gaston wrote: > I am not against this model... (it is VERY close to how we do things > with MOOSE... and our "stable merge" is automated by Bitten) > however, can we have a small "cooling off" period for a moment while > everyone gets up to date with using the new buil

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

I am not against this model... (it is VERY close to how we do things with MOOSE... and our "stable merge" is automated by Bitten) however, can we have a small "cooling off" period for a moment while everyone gets up to date with using the new build system and pulling from Git? MOOSE still doesn't

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

On Wed, 12 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote: > (1) treating 'master' as the place for stable code, along the lines of Roy's > suggestion, > (2) creating 'devel' where the core developers live. My concern here is that then the core developers don't get the main benefit of the "devel"->

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

On Dec 12, 2012, at 9:28 AM, John Peterson wrote: > The development branch can be periodically merged into stable, perhaps > automatically by buildbot whenever tests pass. > > So core developers would primarily work with the development branch, > and users who lie somewhere between "core develo

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

On Tue, Dec 11, 2012 at 9:53 PM, Roy Stogner wrote: > > On Tue, 11 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> >> http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Integration-Manager-Workflow > > > Who volunteers to be integration manager? If it's not the most > prolific deve

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

On Dec 11, 2012, at 10:53 PM, "Roy Stogner" wrote: > A) given another patch designed specifically to fix the failed tests, > B) reverted to any other newer-than-Master revision that hasn't been > tested (in cases where multiple patches were added too fast for > buildbot to test) > C) reverted com