Re: [deal.II] Debug multithread code

Yes, I'm in debug mode. I mean I cannot step over one line each time or step into a function. I have to set a lot of breakpoints to stop the program at these lines. > On Aug 5, 2021, at 6:16 PM, Timo Heister wrote: > >  > What do you mean by "cannot do step debug"? Are you compiling in debug

Re: [deal.II] Debug multithread code

What do you mean by "cannot do step debug"? Are you compiling in debug mode? On Thu, Aug 5, 2021, 18:34 Michael Li wrote: > I put *MultithreadInfo::set_thread_limit(**1**)* in *main* function, but > still cannot do step debug in the function > > *assemble_neumann_contribution_one_cell. *Am I doi

RE: [deal.II] Debug multithread code

I put MultithreadInfo::set_thread_limit(1) in main function, but still cannot do step debug in the function assemble_neumann_contribution_one_cell. Am I doing something wrong?    From: Timo HeisterSent: Thursday, August 5, 2021 1:19 PMTo: dealii@googlegroups.comSubject: Re: [deal.II] Debug multithr

[deal.II] ASPECT v2.3.0 released

Hi all, We recently released version 2.3.0 of ASPECT, the Advanced Solver for Problems in Earth's ConvecTion, which is built on deal.II. See https://aspect.geodynamics.org/ and https://github.com/geodynamics/aspect/releases/tag/v2.3.0 for more information about ASPECT. Best, Timo -- Timo Heist

Re: [deal.II] Step 79 - Topology Optimization

Howdy! The step-79 program uses simultaneous analysis and design (SAND) as well as second derivative information to solve this 2d problem. Most people doing large scale, 3d problems today use only first derivative information and sensitivity analysis in a nested analysis and design (NAND) context.

[deal.II] Step 79 - Topology Optimization

Hey there, I looked at tutorial 79 dealing with topology optimization and the tutorial mentions that step 79 deals with elastic isotropic material and at the end presents a case study in 2D. Is 3D case already considered in this module? and also is it possible to deal with high resolution larg

Re: [deal.II] Debug multithread code

Take a look at set_thread_limit: https://www.dealii.org/current/doxygen/deal.II/classMultithreadInfo.html As you can see, you can also control it using an environment variable, so you don't have to recompile. On Thu, Aug 5, 2021, 13:36 Michael Lee wrote: > Hi, > > I find it's difficult to debug

[deal.II] Debug multithread code

Hi, I find it's difficult to debug multithread code on a multiple-core computer. Sometimes it does not step into a function (I'm using vscode + wsl). Does deal.II use all the cores available? For the sake of debug, how can I limit the cores used? Is there a way to debug the code just like seri

Re: [deal.II] Output file

Thank you very much for your answer. Is it then not possible to use somehow the DataOut approach presented in step-29 and use a 'txt' parameter in the .prm file? In case of doing that manually as you suggested, how could I access the real and imaginary parts in the solution vector (step-29)? Doin