Dear Professor Bangerth,
thank you very much for your reply and please excuse my late answer.
Unfortunately I didn't have the time the last couple of days to work on
this problem or further investigate it.
I have edited the pack_callback() function in solution_transfer.cc a little
bit myself
Mathias,
> thanks again for your reply, I will start answering your questions and
> give you more insight into what I try to do at the moment:
>
> That's exactly the question you have to answer first. What do you
> *want* to
> happen on these cells? If you know what you want to
Dear Professor Bangerth,
thanks again for your reply, I will start answering your questions and give
you more insight into what I try to do at the moment:
That's exactly the question you have to answer first. What do you *want* to
> happen on these cells? If you know what you want to happen,
> Oh yes, I actually did not assume my current way of doing things to work.
> After the static case was running, it was just a one liner (calling
> set_fe_indices() again in each timestep) which was a really naive way of
> doing
> things.
> The problem at the moment is, that I just change the
Dear Professor Bangerth,
thanks for your reply, I hope I can answer your questions:
I can see that this doesn't look right. But do you understand *why*
> things go wrong? I can't tell from the pictures, but I've often found
> that when trying to solve a problem for which I know that there is a
Mathias,
> I want to simulate how a solid moves in a fluid with a fixed mesh using
> Cut-FEM. I implemented this using the hp-framework and set all the DoFs
> where just the solid is to FE_Nothing. You can see this in (attached)
> two pictures: overlay_0 shows a solid circle lying in a
