[deal.II] Approximate Derivative Tensor functionality

Hey there! For cell-wise error estimation calculations, I want to use the 'approximate_gradient', 'approximate_derivative_tensor' and similar functionality available in 'DerivativeApproximation' namespace (here ).

[deal.II] Re: Approximate Derivative Tensor functionality

default = 0 (and I have only 1 scalar field). The syntax error shall be coming from the tensors cell_grad and cell_hessian. On Wednesday, 15 February 2017 16:42:55 UTC+5:30, Sumedh Yadav wrote: > > Hey there! > For cell-wise error estimation calculations, I want to use the > 'app

[deal.II] Re: Approximate Derivative Tensor functionality

ell matrices as - Tensor<2,2, float> cell_hessian; -Tensor<1,2, float> cell_grad; On Wednesday, 15 February 2017 16:42:55 UTC+5:30, Sumedh Yadav wrote: > > Hey there! > For cell-wise error estimation calculations, I want to use t

[deal.II] Re: Approximate Derivative Tensor functionality

,1,2> as template arguments. But supplying 1 in place of 2 doesn't work! On Wednesday, 15 February 2017 16:42:55 UTC+5:30, Sumedh Yadav wrote: > > Hey there! > For cell-wise error estimation calculations, I want to use the > 'approximate_gradient', 'approximate_der

[deal.II] Matrix tools in MatrixCreator namespace

Hello, I want to use the *create_mass_matrix* and *create_laplace_matrix* functionality of MatrixCreator namespace. The function prototype here requires to pass a pointer (which is by default 0 meaning that there is no variable coefficient associated with variable or laplace of variable) to a f

[deal.II] Re: Matrix tools in MatrixCreator namespace

ss_matrix, ptr , constraints); ^ On Thursday, 16 February 2017 14:23:21 UTC+5:30, Sumedh Yadav wrote: > > Hello, > I want to use the *create_mass_matrix* and *create_laplace_matrix* > functionality of MatrixCreator namespace. The function prototype here > requires to pa

[deal.II] Transfer local cell data to global cell vector

Hello, I need to do some post-processing on computed solution data (say Vector Solution(dof_handler.n_dofs()) is the solution vector). For post-processing field (say Vector Curvature(triangulation.n_dofs()) is the scalar field to be computed) I decided to have one entry per cell. Once I calcula

[deal.II] Re: Transfer local cell data to global cell vector

Thankyou! that works :) On Saturday, 18 March 2017 12:03:55 UTC+5:30, Sumedh Yadav wrote: > > Hello, > I need to do some post-processing on computed solution data (say > Vector Solution(dof_handler.n_dofs()) is the solution vector). For > post-processing field (say V

[deal.II] Inhomogeneous Dirichlet bounday conditions with Raviart-Thomas (RT) elements

Hello, I intend to use RT elements for my fluid flow problem and the test case (2D) is shear flow. Consequently the I need to apply constant shear/sliding velocity (u_x = shear_velocity, u_y = 0) at top and bottom boundaries and velocities of form u_y = 0, u_x = y*shear_velocity for the right an

[deal.II] Finite Element Method for Two Phase Flow

Hello, In my project I am modeling two-phase flow using phase-field model (an interface capturing method). Now I am done with first draft of my code and I am facing the well-known issue of 'spurious currents in two-phase flow using FEM' (paper 1

[deal.II] Re: Finite Element Method for Two Phase Flow

Daniel, I had went through step-21 and it appears step-43 extends step-21 with the intentions of improving preconditioning et cetera. In essence both the tutorials solve the same set of equations, namely Darcy's Law, conservation of mass and saturation equation. But for this set of approximate

[deal.II] Re: Finite Element Method for Two Phase Flow

I would like to add an idea I intend to apply but right now am clueless of how to apply. In the earlier post I mentioned issue of 'spurious currents'. In the past researchers have tried quite a few approaches to handle this. One of them involves reconstruction of computed pressure field. In ess