On Mon, 13 Mar 2017, John Peterson wrote:
On Mon, Mar 13, 2017 at 11:06 AM, Barna Becsek wrote:
I was able to overcome the problem with a little help from a
friend.
Basically what I did is replace “this->qrule->get_weights()”
with “const_cast(this->qrule)->get_weights(
On Mon, Mar 13, 2017 at 11:06 AM, Barna Becsek
wrote:
> Dear Roy,
>
> I was able to overcome the problem with a little help from a friend.
> Basically what I did is replace “this->qrule->get_weights()” with
> “const_cast(this->qrule)->get_weights()” and everything
> worked fine!
> I, however, sti
Dear Roy,
I was able to overcome the problem with a little help from a friend.
Basically what I did is replace “this->qrule->get_weights()” with
“const_cast(this->qrule)->get_weights()” and everything worked
fine!
I, however, still don’t understand why this would be necessary. In theory qrule
a
Dear Roy,
I was finally able to install in a location where I can both read from compute
nodes and edit the files. In the attachment is what I found.
Basically, it seems like get_weights() returns an incorrect address.
–Barna
> On 7 Mar 2017, at 11:19, Barna Becsek wrote:
>
>>
>> On 3 Mar
> On 3 Mar 2017, at 22:30, Roy Stogner wrote:
>
>
> On Fri, 3 Mar 2017, Barna Becsek wrote:
>
>>> On 3 Mar 2017, at 17:47, Roy Stogner wrote:
>>>
>>> On Fri, 3 Mar 2017, Barna Becsek wrote:
>>>
> On 3 Mar 2017, at 17:28, Roy Stogner wrote:
>
> What is &qw and how does it compa
On Wed, 1 Mar 2017, Barna Becsek wrote:
I found the place the assertion is tripped. In the attachment you
can see the stack and location of the casting. Haven’t dug into why
this happens yet…
Well, at least we know the cast is a red herring now! That's not a
64-bit invalid_something_or_other
Dear Roy,
I found the place the assertion is tripped. In the attachment you can see the
stack and location of the casting. Haven’t dug into why this happens yet…
–Barna
> On 1 Mar 2017, at 14:50, Barna Becsek wrote:
>
> Alright, thank you for giving it a look. As far as I can see from libm
Alright, thank you for giving it a look. As far as I can see from libmesh’s
config.log the CXXFLAGS_DBG do include the option -O0.
For the others I cannot really do much at the moment because I am in a somewhat
unfortunate situation, where:
I have a filesystem on the cluster that I can compile s
On Tue, 28 Feb 2017, Barna Becsek wrote:
> I actually attached the stack to the previous email but I am not
> sure whether I can actually send attachments to this mailing list.
Depends on attachment size, but I simply overlooked it. I use a text
email reader 90% of the time and my eyes glaze ov
Thank you very much!
I actually attached the stack to the previous email but I am not sure whether I
can actually send attachments to this mailing list.
So this is the output:
Assertion `oldvar == static_cast(static_cast(oldvar))' failed.
oldvar = [4]
/apps/daint/UES/6.0.UP02/sandbox-ws/moose
On Tue, 28 Feb 2017, Barna Becsek wrote:
> To remedy this I called prepare_for_use once additionally before
> gather_neigboring_elements (to make sure that the mesh is set up as
> a distributed one) and then once after.
>
> This actually made me overcome the original problem, i.e. the above
> loo
Thank you so much for your help. I still have some issues/questions:
I have verified that the problem is exactly what you said by checking how far
the loop over i (till mesh.max_elem_id()) goes before that process (rank 0)
gets ahead of the other processes.
It exactly only goes as far as the loc
On Mon, 27 Feb 2017, Barna Becsek wrote:
> I hope this does not come too late.
That depends entirely on your deadlines, I fear. ;-)
> But I finally got the debugger to work with some help of support on
> the Supercomputer that we are using. This is the complete stack:
>
> To recap the problem:
Dear Roy,
I hope this does not come too late. But I finally got the debugger to work with
some help of support on the Supercomputer that we are using. This is the
complete stack:
To recap the problem:
We were reading in a mesh that was created outside of libmesh (rectilinear) and
wanted to use
On Fri, 13 Jan 2017, Barna Becsek wrote:
> Hmm, you are right but I cannot find a process that would correspond to the
> children of any of these.
Is this a cluster, by any chance? Where slurm is running on the login
node but the actual applications are running on separate compute
nodes?
If I
Hmm, you are right but I cannot find a process that would correspond to the
children of any of these. These are all the processes for my username:
ps -elf | grep becsekba
4 S root 12129 17897 0 80 0 - 24867 SyS_po 14:35 ?00:00:00
sshd: becsekba [priv]
4 S becsekba 12131 1
On Fri, 13 Jan 2017, Barna Becsek wrote:
> I think these also belong to the execution:
I think you've posted backtraces for every process *except* the
important ones. :-D
Shouldn't there be child processes of those srun processes? The
children would be the ones running *your* code; that's whe
I think these also belong to the execution:
0 S becsekba 54421 52395 0 80 0 - 4438 wait 12:39 pts/92 00:00:00
/bin/bash /apps/daint/UES/xalt/0.7.6/bin/srun -n 8 whale-dbg -i
IMP/RunImpact2D.i
(gdb) bt
#0 0x2b641c273cec in waitpid () from /lib64/libc.so.6
#1 0x004297aa in
Ok, this is the backtrace of the running processes. There are two processes
running:
0 S becsekba 54451 54421 0 80 0 - 76108 futex_ 12:39 pts/92 00:00:00
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
1 S becsekba 54477 54451 0 80 0 - 24908 pipe_w 12:39 pts/92 00
On Thu, 12 Jan 2017, Barna Becsek wrote:
> What I meant was the program will not exit gather_neighboring_elements. I
> think the processes are still running.
Right. But you can e.g. attach gdb to a running process to get a
stack trace. If there's an infinite loop then we can at least find
out
What I meant was the program will not exit gather_neighboring_elements. I think
the processes are still running.
> On Jan 12, 2017, at 4:26 PM, Roy Stogner wrote:
>
>
>> On Thu, 12 Jan 2017, Barna Becsek wrote:
>>
>> thank you very much for these thorough elaborations. Judging by
>> these I
On Thu, 12 Jan 2017, Barna Becsek wrote:
thank you very much for these thorough elaborations. Judging by
these I think we are doing the setup correctly.
However, it seems our code gets stuck somewhere in the
get_neighboring_elements() method in debug mode. It halts and does
not seem to advan
Dear Roy, dear Cody,
thank you very much for these thorough elaborations. Judging by these I think
we are doing the setup correctly.
However, it seems our code gets stuck somewhere in the
get_neighboring_elements() method in debug mode. It halts and does not seem to
advance even with very coars
On Tue, 10 Jan 2017, Barna Becsek wrote:
What we DON’T HAVE:
- A clear understanding of how ghost elements in LibMesh work.
If you need complicated ghosting (multiple layers of ghost elements,
ghost elements defined by contact problems, ghosted DoFs on distant
elements, etc) then the best wri
Dear Users,
We are writing a multiphysics tool where we need to replicate a FD mesh in a FE
way. We have been almost able to translate one into the other but are facing
some minor difficulties (hopefully).
I would greatly appreciate if someone could help us find the missing steps for
having a c
25 matches
Mail list logo
