Re: [deal.II] Member description of MeshWorker::DoFInfo.matrix

> I am reading step-12 of the tutorial. The following lines are from local > integrator for interior face (dinfo is an alias to MeshWorker::DoFInfo). > > FullMatrix > > _v1_matrix = dinfo1.matrix(0, false).matrix; >

Re: [deal.II] The type of particle properties

Yidong, > Yes, I think *interpret* can work. Here I want to ask for a follow-up > question: Whether it's possible(how difficult) to write a child class of > Particle, whose property is not an array of double, but other self-defined > types (like Tensor etc.)? No -- the ParticleHandler

Re: [deal.II] The type of particle properties

Dear Wolfgang, Thanks for your prompt and clear answer! Yes, I think *interpret* can work. Here I want to ask for a follow-up question: Whether it's possible(how difficult) to write a child class of Particle, whose property is not an array of double, but other self-defined types (like Tensor

Re: [deal.II] The type of particle properties

> From the descriptions of > Particle(https://www.dealii.org/current/doxygen/deal.II/classParticles_1_1Particle.html) > > and > PropertyPool(https://www.dealii.org/current/doxygen/deal.II/classParticles_1_1PropertyPool.html), > > I know the properties of a particle should be ArrayView

Re: [deal.II] Implementation of boundary condtitions

Dear Muhammad, I think Ross implemented vector_value_list() this way so that he could use one function object to give correct values with multiple material IDs: see https://github.com/rosskynch/MIT_Forward/blob/master/src/forwardsolver.cc#L724 to see where he uses an object inheriting from

[deal.II] Re: On using project_boundary_values_div_conforming for (RT-DG) in parallel case

Hi Konrad, Thanks for your reminder. After upgrading to v9.1.1, everything goes well now. It seems an issue of the last version of dealii and has already been fixed: https://github.com/dealii/dealii/pull/7327 . Regards, Charlie On Wednesday, September 11, 2019 at 7:43:45 PM UTC+2, Konrad

Re: [deal.II] How to efficiently add / remove cells (maybe with hp::DoFHandler)

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

[deal.II] Implementation of boundary condtitions

Hello, I am trying to understand the MIT code written by Ross Kynch. I am facing a problem to understand the implementation of boundary conditions. As we know we impose boundary conditions to calcluate the unknown coefficients. I don't understand how is he implementing the code given below to

Re: [deal.II] Getting RHS values at nodes with DBC

As always there is a "deal.ii" way of doing the calculations. The FEValues::get_function_gradients() is actually what I needed. I got a little bit confused with the FEValues::get_normal_vectors(). This seems to return the normal direction of the face and doesn't give any further info about the