On 10/3/19 2:06 AM, huyanzhuo wrote:
> |
> |
>
> it works well when i use *ONE PROCESS*, it only need 14~15 iterations to get
> a
> satisified result.
> but when i use the
> |
> mpirun -np 2
> |
> i get errors as follows
> |
>
> Exception on
On 10/11/19 6:17 PM, manuJayadharan wrote:
>
> *Question: *If I start by assuming that I have values of the
> flux(approximated
> using RT_k elements for each fixed time step) at different points on the red
> interface from my earlier computations in terms of dof_handler for Omega_1
> and
> s
On 10/15/19 1:55 AM, Mauro Murer wrote:
> s in the system matrices.
> All went well until I tried to implement a mesh refinement.
> In particular, when I assemble the gradient operator after the refinement of
> the mesh (increasing the dof of the problem), this error occurs when
> "distribute_loc
> > Yes. Though it seems confusing to me that you call these variables
> > locally_*_cells, because they really are index sets for degrees of freedom,
> > not cells.
>
> OK, I misunderstood it. I thought the numbering of the dof is same as that of
> the cell since the degrees of freedom is 1
On 10/20/19 5:42 PM, Zhidong Brian Zhang wrote:
> Thank you very much for your prompt reply, Konrad!
>
> My confusion is the output of cell->id(), for example,
> 0_3:000
> 0_3:200
> 0_3:003
> 0_3:006
> 0_3:406
> 0_3:606
> 0_3:206
> 0_3:007
> 0_3:407
> 0_3:607
> 0_3:207.
These strings are simply a
Hi, Dr. Bangerth,
Thank you very much for prompt reply!
> Yes. Though it seems confusing to me that you call these variables
> locally_*_cells, because they really are index sets for degrees of
freedom,
> not cells.
OK, I misunderstood it. I thought the numbering of the dof is same as that
Thank you very much for your prompt reply, Konrad!
My confusion is the output of cell->id(), for example,
0_3:000
0_3:200
0_3:003
0_3:006
0_3:406
0_3:606
0_3:206
0_3:007
0_3:407
0_3:607
0_3:207.
What type I need to use as the key in std::map? And is the map
parallel-distributed? Because my model
On 10/19/19 3:01 PM, Zhidong Brian Zhang wrote:
>
> And I initialize the cell-based vector (the pesudo density in topology
> optimization) as follows,
>
> opt->locally_owned_cells= opt->dof_handler_dg.locally_owned_dofs();
> DoFTools::extract_locally_relevant_dofs(opt->dof_handler_dg,
>
On 10/20/19 9:54 AM, Konrad Simon wrote:
>
> Is there a way to evaluate a given shape function on a given cell like a
> normal Function or TensorFunction? I need to do many computations on a coarse
> cell that itself is meshed.
You are looking for the FEFieldFunction class.
> I have an implem
Hi deal.ii community,
I have a little implementation problem to bug you with...
Is there a way to evaluate a given shape function on a given cell like a
normal Function or TensorFunction? I need to do many computations on a
coarse cell that itself is meshed.
I have an implementation but it is
Hi Zhidong,
I don't know what exactly you want to do but I found it quite useful that
the CellId class has an order relation. That makes it usable in a std::map.
Use the CellId (you can retrieve it through cell-->id() if cell is a cell
accessor like the one you use to loop over all your cells)
11 matches
Mail list logo
