Skip to content

Commit

Permalink
Update parallel notebook.ipynb
Browse files Browse the repository at this point in the history
  • Loading branch information
skrawcz authored Nov 21, 2024
1 parent 3120471 commit d932eab
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions examples/parallelism/notebook.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@
"2. `run_llms` -- runs the different LLM models in parallel (not defined below)\n",
"3. `join_outputs` -- writes a map of LLM -> result\n",
"\n",
"We will first define actions (1) and (3), then redefine (2) according to whether we're using recursion or parallelism."
"We will first define actions (1) and (3), then redefine (2) according to whether we're using recursion/hierarchy or parallelism."
]
},
{
Expand Down Expand Up @@ -401,11 +401,11 @@
"id": "becfab1b-f89d-49a0-b1af-2f01359bfefa",
"metadata": {},
"source": [
"# Approach #2 -- using Burr within Burr, i.e. recursion\n",
"# Approach #2 -- using Burr within Burr, i.e. recursion/hierarchy\n",
"\n",
"Burr allows you to create Burr applications within Burr applications and wire through tracking to the UI so you can visualize sub-applications. For this, we will be representing the LLM calls with different models as their own (single-node) application. While this is built for more complex sub-application shapes, and is a bit of overkill for our toy example, it still works quite well with the simplicity of a single action (node) application. My point here is that you could add more actions to the application very easily and do more complex operations than what we're doing here. The Burr sub-applications can be used independently elsewhere.\n",
"Burr allows you to create Burr applications within Burr applications and wire through tracking to the UI so you can visualize sub-applications. For this, we will be representing the LLM calls with different models as their own (single-node) application. While this is built for more complex sub-application shapes, and is a bit of overkill for our toy example, it still works quite well with the simplicity of a single action (node) application. My point here is that you could add more actions to the application very easily and do more complex operations and model hierarchy than what we're doing here. The Burr sub-applications/graphs can be used independently elsewhere.\n",
"\n",
"For more on the code constructs in this section see Burr's [recursive tracking capabilities](https://burr.dagworks.io/concepts/recursion/)."
"For more on the code constructs in this section see Burr's [recursive/hierarchy tracking capabilities](https://burr.dagworks.io/concepts/recursion/)."
]
},
{
Expand Down

0 comments on commit d932eab

Please sign in to comment.