Home
last modified time | relevance | path

Searched refs:plotting (Results 1 – 3 of 3) sorted by relevance

/petsc/src/ts/utils/dmplexlandau/tutorials/
H A Dex2.c39 PetscBool plotting; member
231 if (rectx->plotting || stepi == 0 || reason || rectx->pulse_start == time + 0.98 * dt) { in testSpitzer()
424 if (stepi > rectx->plotStep && rectx->plotting) { in Monitor()
425 rectx->plotting = PETSC_FALSE; /* was doing diagnostics, now done */ in Monitor()
434 if (!rectx->plotting) { /* first step of possible backtracks */ in Monitor()
435 rectx->plotting = PETSC_TRUE; in Monitor()
440 rectx->plotting = PETSC_TRUE; in Monitor()
450 …if (rectx->plotting) PetscCall(PetscPrintf(PETSC_COMM_WORLD, " ERROR rectx->plotting=%s step %" Pe… in Monitor()
558 rectx->plotting = PETSC_FALSE; in ProcessREOptions()
699 rectx->plotting = PETSC_FALSE; in main()
/petsc/src/ts/tutorials/
H A Dex48.c46 PetscBool plotting; member
73 options->plotting = PETSC_FALSE; in ProcessOptions()
312 if (stepi > ctx->plotStep && ctx->plotting) { in Monitor()
313 ctx->plotting = PETSC_FALSE; /* was doing diagnostics, now done */ in Monitor()
324 if (!ctx->plotting) { /* first step of possible backtracks */ in Monitor()
325 ctx->plotting = PETSC_TRUE; in Monitor()
328 ctx->plotting = PETSC_TRUE; in Monitor()
/petsc/doc/manual/
H A Dperformance.md710 affects a particular code, one can try plotting the total flop rate