minor elaboration on columnar data

Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
PowerGridModel · Oct 21, 2024 · 19be23d · 19be23d
1 parent 313834a
commit 19be23d
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/examples/Power Flow Example.ipynb b/docs/examples/Power Flow Example.ipynb
@@ -129,7 +129,7 @@
    "source": [
     "It is also possible to specify a component input data in a columnar data format.\n",
     "\n",
-    "A columnar data format allows better integration with existing databases. In addition, it may bring memory and, in some cases, even computational performance improvements, because unused attribute columns can be omitted.\n",
+    "A columnar data format better integrates with most databases. In addition, it may bring memory and, in some cases, even computational performance improvements, because unused attribute columns can be omitted.\n",
     "\n",
     "Make sure to provide the correct `dtype` to the numpy arrays, exposed for each dataset type, component and attribute via the `power_grid_meta_data` object."
    ]
@@ -1352,11 +1352,11 @@
       "[[9.99401170e-001 9.92685785e-001 9.94521366e-001]\n",
       " [9.99347687e-001 9.86226389e-001 9.89352855e-001]\n",
       " [9.99288384e-001 9.79654011e-001 9.84095542e-001]\n",
-      " [6.01347174e-154 7.39986091e-038 6.55490955e-260]\n",
+      " [0.00000000e+000 3.04369633e+101 3.41345331e+241]\n",
       " [9.99151380e-001 9.66149483e-001 9.73298790e-001]\n",
       " [9.99073166e-001 9.59205860e-001 9.67750710e-001]\n",
       " [9.98988099e-001 9.52126208e-001 9.62096474e-001]\n",
-      " [6.95195146e-310 6.95195146e-310 6.95195146e-310]\n",
+      " [1.66994188e-321 3.12878333e-312 9.75772002e+199]\n",
       " [9.98796126e-001 9.37530046e-001 9.50447962e-001]\n",
       " [9.98688504e-001 9.29997471e-001 9.44441670e-001]]\n",
       "Node data with only valid results\n",