[deal.II] Re: variable time step in step44

Dear Anup, Why don't you reinterpret the parameter passed as "delta_t" to be the initial timestep size "delta_t_0" and then adjust the current timestep size "delta_t" however you want? How you do this adjustment algorithm-wise is, of course, entirely up to you. Regards, J-P On Tuesday, Augus

Re: [deal.II] matrix factorization reuse?

On 08/30/2016 11:09 AM, David F wrote: Hi, I'm interested in this as well. Could you post or link to your solution? David -- this went into the code base with this patch: https://github.com/dealii/dealii/pull/2493 Best Wolfgang -- ---

[deal.II] Re: Neumann condtitions in the mixed space setting

I managed to imply the Neumann conditions on stress only by first projecting the boundary values to the entire mixed space (affecting rotations), and then manually removing the constraints associated with rotations. The code is below if someone is interested. VectorTools::project_boundary_values

[deal.II] Neumann condtitions in the mixed space setting

I am trying to implement mixed elasticity with Neumann conditions using deal.ii. The formulation seeks for stress, displacement and rotation as the unknowns, and the Neumann conditions are to set stress normal components to be equal to some function g. I know that for mixed Darcy it is possibl

Re: [deal.II] matrix factorization reuse?

Hi, I'm interested in this as well. Could you post or link to your solution? Thanks. On Friday, 19 February 2016 17:21:22 UTC+1, Michael Harmon wrote: > > If you want to use Trilinos, I refactored their direct solver so that it > can be used the way you want, I will submit the patch, but if you

[deal.II] variable time step in step44

Hello all, I was trying to implement an adaptive time step in step44. In the given example 'delta_t' has been considered to be fixed and its value is taken from the .prm file. Now let us say one changes the value of 'delta_t' in the function 'run()'. What will be the convenient way to replace ol

[deal.II] Re: Vector-valued gradient of solution vector

Dear Joel, No, this functionality doesn't exist. However, you can create a quadrature rule with the quadrature points located at the support points (see the FAQ ), a

[deal.II] Re: Vector-valued gradient of solution vector

Dear Daniel, I was just wondering if their exist a similar function to DoFTools::map_dofs_to_support_points, but that maps a vector-valued solution Vector into to a std::vector> instead? Best, Joel On Monday, August 22, 2016 at 9:03:22 PM UTC+2, Daniel Arndt wrote: > > Joel, > > You should not

Re: [deal.II] Strange issue with KellyErrorEstimator functionality

On 08/30/2016 03:28 AM, Deepak Gupta wrote: In my problem case, I do not have any distributed load at the boundary which means no boundary Neumann boundary condition. However, I have a point load at one of the nodes (found the node and change the value) which I do not state in the KellyEstimator

Re: [deal.II] Question concerning BlockSparsityPattern.copy_from() member function

Dear Martin, unfortunately I have to revise all my statements. Updating the deal.II library to the most recent developement version did not solve the problem. I made a stupid mistake while creating the file for the test case. The function make_offdiagonal_sparsity_pattern () has been commented

Re: [deal.II] Strange issue with KellyErrorEstimator functionality

Dear All, In my problem case, I do not have any distributed load at the boundary which means no boundary Neumann boundary condition. However, I have a point load at one of the nodes (found the node and change the value) which I do not state in the KellyEstimator module and I am blind-guessing that