Re: AW: [deal.II] step-42 clarification

> In such a case, one wants to restart the computations We have support for snapshot&resume in parallel with adaptive meshes by using the SolutionTransfer class. See "Use for serialization" in https://urldefense.proofpoint.com/v2/url?u=http-3A__www.dealii.org_developer_doxygen_deal.II_classparalle

Re: AW: [deal.II] step-42 clarification

Thank you, Timo. Your remarks have been very useful. It turned out that I made a mistake in the way the mesh was prepared, specifically some hanging nodes were not properly dealt with. This caused also a related issue, that I shared here some time ago (Nov. 25). This leads to another question, th

Re: AW: AW: [deal.II] step-42 clarification

I can do that for you. Do I understand correctly that the only change that needs to happen is to move active_set_old = active_set; to *after* the if-statement? Exactly. Great, thanks for confirming, Joerg! The patch is now here: https://www.dealii.org/8.5.1/doxygen/deal.II/Tutorial.htm

Re: AW: [deal.II] step-42 clarification

> in the code and re-implemented it. In serial version, all works fine so far. > However, when running in parallel, I am seeing an issue in the method > PlasticityContactProblem::update_solution_and_constraints. > > In particular, it turns out that the value of > > const unsigned int index_z = dof_

Re: AW: [deal.II] step-42 clarification

Hi Wolfgang and Jörg I am taking advantage for a second question. I have made a few minor changes in the code and re-implemented it. In serial version, all works fine so far. However, when running in parallel, I am seeing an issue in the method PlasticityContactProblem::update_solution_and_constra

AW: AW: [deal.II] step-42 clarification

>>On 01/17/2018 02:45 PM, Frohne, Joerg wrote: >> obviously this is a mistake. I checked the source files which we have used >> for results in corresponding paper. >> There I have found the following coding: >> >>resid_old = resid; >> >>resid_vector = system_rhs_newton; >>

Re: AW: [deal.II] step-42 clarification

On 01/17/2018 02:45 PM, Frohne, Joerg wrote: obviously this is a mistake. I checked the source files which we have used for results in corresponding paper. There I have found the following coding: resid_old = resid; resid_vector = system_rhs_newton; resid_vecto

AW: [deal.II] step-42 clarification

pers! Joerg Von: Wolfgang Bangerth [bange...@colostate.edu] Gesendet: Dienstag, 16. Januar 2018 21:48 An: dealii@googlegroups.com; Frohne, Joerg Cc: Suttmeier, Franz-Theo Betreff: Re: [deal.II] step-42 clarification On 01/16/2018 12:59 AM, Alberto Salvadori wrote: >

Re: [deal.II] step-42 clarification

On 01/16/2018 12:59 AM, Alberto Salvadori wrote: Dear community, I am studying with pleasure step-42 and I got a bit confused in the method PlasticityContactProblem::solve_newton. At the very end of it, we find these instructions: old_active_set = active_set; previous_residual_norm = residua

[deal.II] step-42 clarification

Dear community, I am studying with pleasure step-42 and I got a bit confused in the method PlasticityContactProblem::solve_newton. At the very end of it, we find these instructions: old_active_set = active_set; previous_residual_norm = residual_norm; if (Utilities::MPI::sum