Hi Dr. Bangerth,
Thanks a lot for your fast response!
That's good to know! The Cell_Data_to_Point_Data filter in ParaView
averages the adjacent cell values and assign them to the nodes, which
produces a smooth and continuous nodal solution field. I was planning on
implementing the averaging
On 7/27/20 2:47 PM, Jimmy Ho wrote:
data_out.add_data_vector( cellData , "Name" , data_out.type_cell_data );
to force deal.ii to recognize that "cellData" should be interpreted as a
cell-based data. When I read the vtu files generated by this program via
ParaView, I found that although
Hi All,
I am trying to compute the average of integration point variables and store
them as cell variables, and subsequently write them as cell arrays in the
visualization. I used:
data_out.add_data_vector( cellData , "Name" , data_out.type_cell_data );
to force deal.ii to recognize that
Dear David,
Thank you! It solved the problem.
Best wishes,
Yuesu
On Mon, Jul 27, 2020 at 8:48 AM David Wells wrote:
> Hi Yuesu,
>
> Essentially, yes. If you look at the code for partition_triangulation you
> will find
>
> // check for an easy return
> if (n_partitions == 1)
> {
> for
Hello everyone!
This is deal.II newsletter #127.
It automatically reports recently merged features and discussions about the
deal.II finite element library.
## Below you find a list of recently proposed or merged features:
#10755: Fix compiling with CUDA 11 (proposed by masterleinad)
Hi Yuesu,
Essentially, yes. If you look at the code for partition_triangulation you
will find
// check for an easy return
if (n_partitions == 1)
{
for (const auto : triangulation.active_cell_iterators())
cell->set_subdomain_id(0);
return;
}
Hence step-17 only tries to use
