From e3e17cee910d151679e2a5f93dbc7a89341e8209 Mon Sep 17 00:00:00 2001 From: Torkel Date: Fri, 28 Jun 2024 18:04:12 -0400 Subject: [PATCH] change wrong statement on convert compelteness --- docs/src/v14_migration_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/v14_migration_guide.md b/docs/src/v14_migration_guide.md index 8634945793..8e1e9737c5 100644 --- a/docs/src/v14_migration_guide.md +++ b/docs/src/v14_migration_guide.md @@ -16,7 +16,7 @@ A model's completeness depends on how it was created: - To *use the DSL to create models that are not marked as complete*, use the `@network_component` macro (which in all other aspects is identical to `@reaction_network`). - Models generated through the `compose` and `extend` functions are *not marked as complete*. -Furthermore, any systems generated through e.g. `convert(ODESystem, rs)` are also complete. +Furthermore, any systems generated through e.g. `convert(ODESystem, rs)` are *not marked as complete*. Complete models can be generated from incomplete models through the `complete` function. Here is a workflow where we take completeness into account in the simulation of a simple birth-death process. ```@example v14_migration_1