From 0926010739679c453dfb7a6a4a61f8f6e7fec801 Mon Sep 17 00:00:00 2001 From: Marcus Rockwell Date: Mon, 1 Jul 2024 10:58:59 -0500 Subject: [PATCH] Updated checkpointing best practices --- docs/howto_guides/Checkpointing-Best-Practices.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/howto_guides/Checkpointing-Best-Practices.md b/docs/howto_guides/Checkpointing-Best-Practices.md index 0c24bcae0..c3b8fce76 100644 --- a/docs/howto_guides/Checkpointing-Best-Practices.md +++ b/docs/howto_guides/Checkpointing-Best-Practices.md @@ -91,14 +91,14 @@ If the Trick Memory Manager **"knows"** about all of the allocations that compri There are certain things that simply cannot be checkpointed like file-pointers, and network connections. Perhaps there are other things as well. For these situations, Trick provides four special job classes: ```"checkpoint"```, ```"post_checkpoint"```, ```“preload_checkpoint”```, and ```“restart”``` (described below). -### What Happens When You Dump a Checkpoint (Under Construction) +### What Happens When You Dump a Checkpoint A checkpoint of a simulation is usually initiated from the Input Processor. That is, via: 1. The input file, or 2. The variable server. -```trick.checkpoint(