aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPjotr Prins2024-12-31 05:36:23 -0600
committerPjotr Prins2024-12-31 05:36:23 -0600
commit0347fd8bb2b3c71b9bfa0365cc5b7c7e7ebace4c (patch)
tree538d5c2df37d9245ea07d262e93a9ae0f8973829 /doc
parentdf1df93c5a10050a1913f4f50a457bd344e3e355 (diff)
downloadpangemma-0347fd8bb2b3c71b9bfa0365cc5b7c7e7ebace4c.tar.gz
doc: and why it matters for gemma
Diffstat (limited to 'doc')
-rw-r--r--doc/code/pangemma.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/code/pangemma.md b/doc/code/pangemma.md
index 3c9e6d4..f0788c3 100644
--- a/doc/code/pangemma.md
+++ b/doc/code/pangemma.md
@@ -66,3 +66,7 @@ runs one path and
```
will run both.
+
+This simple example shows how simple complex running logic can be described without (1) predicting how people will use the software and (2) no complex if/then statements.
+
+Why does this matter for gemma? It will allow us to run old parts of gemma as part of the network in addition to new parts - and potentially validate them. It also allows us to create multiple implementations, such as for CPU and GPU, that can run in parallel and validate each other's outcomes.