You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: chapter_2/llms_for_biology.ipynb
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@
13
13
"\n",
14
14
"As the volume of scientific literature continues to grow rapidly, manually extracting and organizing this information becomes increasingly difficult and time-consuming. Therefore, automating data extraction from the literature using AI can help researchers to rapidly identify relevant findings, convert unstructured text into structured datasets, and integrate knowledge across thousands of publications. \n",
15
15
"\n",
16
-
"::{admonition} 🚀 Getting Started\n",
16
+
":::{admonition} 🚀 Getting Started\n",
17
17
":class: tip\n",
18
18
"\n",
19
19
"This tutorial can be launched using the rocket button at the top of the page.\n",
Copy file name to clipboardExpand all lines: chapter_3/agent_mcp_example.ipynb
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
"\n",
9
9
"In chapters 3.2 and 3.3 we learned how to write boilerplate code and implement agents. But the problem is, if you are not a python programmer you might find this to be tedious. This may not be the main problem you want to solve and might be interested in a simpler solution.\n",
10
10
"\n",
11
-
"::{admonition} 🚀 Getting Started\n",
11
+
":::{admonition} 🚀 Getting Started\n",
12
12
":class: tip\n",
13
13
"\n",
14
14
"This tutorial can be launched using the rocket button at the top of the page.\n",
Copy file name to clipboardExpand all lines: chapter_3/aviary_agent_implementation.ipynb
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@
20
20
"Figure 3.2.1: An agent iteratively received observations from the environment, takes an action based on the observation until the task is completed.\n",
21
21
"```\n",
22
22
"\n",
23
-
"::{admonition} 🚀 Getting Started\n",
23
+
":::{admonition} 🚀 Getting Started\n",
24
24
":class: tip\n",
25
25
"\n",
26
26
"This tutorial can be launched using the rocket button at the top of the page.\n",
Copy file name to clipboardExpand all lines: index.md
+48-2Lines changed: 48 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,52 @@ By the end of this series, you should:
23
23
24
24
- A curious mindset
25
25
26
-
# Contact Us for Questions, Suggestions and Feedback
26
+
# Using Tutorials
27
27
28
-
Email us at: tutorials@futurehouse.org
28
+
The tutorials can be launched using the rocket (🚀) button at the top of the page.
29
+
30
+
### Option 1 — Google Colab (**recommended**)
31
+
Opens the notebook in Google Colab with the fastest and most reliable experience.
32
+
33
+
Before running the tutorial, add your API keys using **either**:
34
+
35
+
- a `.env` file, or
36
+
-**Colab Secrets** (`🔑 Secrets` tab in the left sidebar)
37
+
38
+
Example `.env`:
39
+
```bash
40
+
OPENAI_API_KEY=your_key_here
41
+
ANTHROPIC_API_KEY=your_key_here
42
+
```
43
+
44
+
### Option 2 — MyBinder
45
+
Launches a temporary cloud Jupyter environment directly in your browser.
46
+
47
+
⚠️ Binder environments can take a few minutes to build and start.
48
+
49
+
After the notebook loads, create a `.env` file in the notebook directory containing your API keys:
50
+
51
+
```bash
52
+
OPENAI_API_KEY=your_key_here
53
+
ANTHROPIC_API_KEY=your_key_here
54
+
```
55
+
56
+
### Notes
57
+
- You only need API keys for the providers used in a given notebook.
58
+
- Never commit or publicly share your API keys.
59
+
- If a cell fails due to missing credentials, verify that your keys were loaded correctly before rerunning the cell.
60
+
61
+
62
+
# Contacting Us
63
+
64
+
We’d love to hear from you! Whether you run into issues, have ideas for improving the tutorials, or want to suggest new topics, feel free to reach out.
65
+
66
+
Email us at: [tutorials@futurehouse.org](tutorials@futurehouse.org)
67
+
68
+
When reporting an issue, it’s helpful to include:
69
+
70
+
- The tutorial chapter number and/or title
71
+
- Whether you used Google Colab or Binder
72
+
- The full error message or screenshot (if available)
73
+
74
+
We’re actively improving these tutorials and appreciate your feedback and contributions.
0 commit comments