Differences

This shows you the differences between two versions of the page.

--- tutorials:checkpointing_overview [2025/11/11 19:56] – [Challenges] ibchadmin
+++ tutorials:checkpointing_overview [2025/12/11 19:35] (current) – [Standard Checkpointing] ibchadmin
@@ Line 13: / Line 13: @@
   * **Adaptability**: an intermittent device should be able to adjust its operation to account for varying environments and energy availability, especially if it will be deployed across a variety of environments.  Even for more narrow deployments, an inflexible device may fail if the testing environment fails to accurately model its real world application.
-A general survey of the two main approaches tackling these challenges are explored below.  This list is not intended to be exhaustive, as checkpointing/state management in intermittent computing is a significant and evolving area of research: rather, the objective is to provide a general overview of the most common methods currently available, along with their benefits and tradeoffs.  These approaches also assume a standard (von Neumann) device architecture: while other hardware configurations are being explored in intermittent computing, low-power devices with traditional architectures such as the [[microcontrollers:msp430|MSP430]] are cheaper and more accessible and so currently make up the vast majority of intermittent devices being designed and tested.
+A general survey of the two main approaches tackling these challenges are explored below.  This list is not intended to be exhaustive, as checkpointing/state management in intermittent computing is a significant and evolving area of research: rather, the objective is to provide a general overview of the most common methods currently available, along with their benefits and tradeoffs.  These approaches also assume a standard (i.e. [[https://en.wikipedia.org/wiki/Von_Neumann_architecture|von Neumann]]) device architecture: while other hardware configurations are being explored in intermittent computing, low-power devices with traditional architectures such as the [[microcontrollers:msp430|MSP430]] are cheaper and more accessible and so currently make up the vast majority of intermittent devices being designed and tested.
 ===== Matched/Energy-Neutral Operation =====
@@ Line 24: / Line 24: @@
 **Examples**
-  * AsTAR
+  * [[https://anrg.usc.edu/www/papers/AsTAR-yang.pdf|AsTAR]]
-  * Flute
+  * [[https://lirias.kuleuven.be/retrieve/734534|Flute]]
 ===== Checkpointing =====
@@ Line 50: / Line 50: @@
 **Examples**
-  * Mementos
+  * [[https://dl.acm.org/doi/10.1145/1961295.1950386|Mementos]]
-  * Hibernus
+  * [[https://ieeexplore.ieee.org/document/6960060|Hibernus]]
-  * HarvOS
+  * [[https://dl.acm.org/doi/10.1145/3055031.3055082|HarvOS]]
-  * Broken Time Machine (https://dl.acm.org/doi/10.1145/2618128.2618136)
 ==== Task-based Checkpointing ====
@@ Line 62: / Line 61: @@
 **Examples**
-  * Alpaca?
+  * [[https://dl.acm.org/doi/10.1145/3133920|Alpaca]]
-  * Mayfly
+  * [[https://dl.acm.org/doi/10.1145/3131672.3131673|Mayfly]]
-  * Artemis
+  * [[https://dl.acm.org/doi/10.1145/3627703.3650070|ARTEMIS]]
-  * Chain
+  * [[https://dl.acm.org/doi/10.1145/2983990.2983995|Chain]]
-  * Ink
+  * [[https://dl.acm.org/doi/10.1145/3274783.3274837|InK]]
@@ Line 94: / Line 93: @@
   * [[https://cmuabstract.github.io/intermittence_tutorial/tutorial/|Getting Started With Intermittent Computing]]
+  * [[https://dl.acm.org/doi/10.1145/2618128.2618136|Nonvolatile Memory is a Broken Time Machine]]