🌐 AI搜索 & 代理 主页
Skip to content

Commit 57ebe61

Browse files
authored
Merge pull request #236 from postgresml/montana/welcom
tweaks
2 parents f402703 + 840cec0 commit 57ebe61

File tree

1 file changed

+89
-97
lines changed

1 file changed

+89
-97
lines changed

pgml-dashboard/notebooks/fixtures/notebooks.yml

Lines changed: 89 additions & 97 deletions
Original file line numberDiff line numberDiff line change
@@ -57,36 +57,57 @@
5757
fields:
5858
notebook: 0
5959
cell_type: 1
60-
contents: "## Welcome!\n\nHi there. Welcome to what we hope is the future of machine
61-
learning!\n\nPostgresML is an end-to-end system for training and deploying real
62-
time machine learning models. It handles data versioning, model training, ranking,
63-
\nand safe production release. This dashboard gives an overview of what's happening
64-
in the system and also helps build and deploy experiments. The notebooks,\none
65-
of which you're reading right this moment, are our take on what ML notebooks
66-
could be when used with a real time data store like PostgreSQL.\n\n\n\n\n###
67-
Notebooks\n\nOur Notebooks are similar to Jupyter Notebooks, which you might
68-
be familiar with already. On the bottom of the page, you will find a text editor
69-
which is used to create new cells. Each cell can contain either Markdown which
70-
is just text really, and SQL which can be executed directly on this PostgresML
71-
instance.\n\nEach cell has a little menu in the top right corner, allowing you
72-
to (re)run it (if it's SQL), edit it, and delete it.\n\n\nLet me give you an
73-
example. The next cell (cell #2) will be a SQL cell which will execute a simple
74-
query."
75-
rendering: "<article class=\"markdown-body\"><h2>Welcome!</h2>\n<p>Hi there. Welcome
76-
to what we hope is the future of machine learning!</p>\n<p>PostgresML is an
77-
end-to-end system for training and deploying real time machine learning models.
78-
It handles data versioning, model training, ranking, \nand safe production release.
79-
This dashboard gives an overview of what's happening in the system and also
80-
helps build and deploy experiments. The notebooks,\none of which you're reading
81-
right this moment, are our take on what ML notebooks could be when used with
82-
a real time data store like PostgreSQL.</p>\n<h3>Notebooks</h3>\n<p>Our Notebooks
83-
are similar to Jupyter Notebooks, which you might be familiar with already.
84-
On the bottom of the page, you will find a text editor which is used to create
85-
new cells. Each cell can contain either Markdown which is just text really,
86-
and SQL which can be executed directly on this PostgresML instance.</p>\n<p>Each
87-
cell has a little menu in the top right corner, allowing you to (re)run it (if
88-
it's SQL), edit it, and delete it.</p>\n<p>Let me give you an example. The next
89-
cell (cell #2) will be a SQL cell which will execute a simple query.</p></article>"
60+
contents: '## Welcome!
61+
62+
63+
You''re set up and running on PostgresML! This is an end-to-end system for training
64+
and deploying real time machine learning models. It handles data versioning,
65+
model training and validation, and safe production release. This dashboard web
66+
app will give you an overview of what''s happening in the system and also helps
67+
build and deploy projects. You can use notebooks like this one to interact with
68+
your database in real time and organize your SQL while documenting your code.
69+
70+
71+
72+
### Notebooks
73+
74+
75+
These notebooks are similar to Jupyter Notebooks, which you might be familiar
76+
with already. On the bottom of the page, you will find a text editor which is
77+
used to create new cells. Each cell can contain either Markdown which is just
78+
text really, and SQL which will be executed directly by your Postgres database
79+
server.
80+
81+
82+
Each cell has a little menu in the top right corner, allowing you to (re)run
83+
it (if it''s SQL), edit it, and delete it.
84+
85+
86+
87+
Let me give you an example. The next cell (cell #2) will be a SQL cell which
88+
will execute a simple query.'
89+
rendering: '<article class="markdown-body"><h2>Welcome!</h2>
90+
91+
<p>You''re set up and running on PostgresML! This is an end-to-end system for
92+
training and deploying real time machine learning models. It handles data versioning,
93+
model training and validation, and safe production release. This dashboard web
94+
app will give you an overview of what''s happening in the system and also helps
95+
build and deploy projects. You can use notebooks like this one to interact with
96+
your database in real time and organize your SQL while documenting your code.</p>
97+
98+
<h3>Notebooks</h3>
99+
100+
<p>These notebooks are similar to Jupyter Notebooks, which you might be familiar
101+
with already. On the bottom of the page, you will find a text editor which is
102+
used to create new cells. Each cell can contain either Markdown which is just
103+
text really, and SQL which will be executed directly by your Postgres database
104+
server.</p>
105+
106+
<p>Each cell has a little menu in the top right corner, allowing you to (re)run
107+
it (if it''s SQL), edit it, and delete it.</p>
108+
109+
<p>Let me give you an example. The next cell (cell #2) will be a SQL cell which
110+
will execute a simple query.</p></article>'
90111
execution_time: null
91112
cell_number: 1
92113
version: 1
@@ -97,11 +118,8 @@
97118
notebook: 0
98119
cell_type: 3
99120
contents: SELECT random();
100-
rendering: "<div class=\"markdown-body\">\n<table>\n <thead>\n <tr>\n \n
101-
\ <td><strong>random</strong></td>\n \n </tr>\n </thead>\n <tbody>\n
102-
\ \n <tr>\n \n <td>0.6822832295608556</td>\n \n </tr>\n
103-
\ \n </tbody>\n</table>\n</div>\n"
104-
execution_time: '00:00:00.000654'
121+
rendering: null
122+
execution_time: null
105123
cell_number: 2
106124
version: 1
107125
deleted_at: null
@@ -110,62 +128,34 @@
110128
fields:
111129
notebook: 0
112130
cell_type: 1
113-
contents: 'I just asked Postgres to give me a random number. Pretty simple query,
131+
contents: "We just asked Postgres to return a random number. Pretty simple query,
114132
but it demonstrates the notebook functionality pretty well. You can see that
115-
the result of `random()` is currently `0.6822832295608556`. On the bottom right
116-
corner, you can see that it took `0:00:00.000654` or 0 hours, 0 minutes, 0 seconds
117-
and only 00006ns, which I believe is 0.6ms, for Postgres to run this query for
118-
us. This runtime is good to know, because you''ll be able to benchmark some
119-
of PostgresML functionality, including the models we provide, right here in
120-
these notebooks.
121-
122-
123-
Try rerunning the cell again by clicking the "play" button in the top right
124-
corner. You''ll see that the random number will change. Rerunning is a real
125-
time operation and Postgres will give you a different random number every time
126-
(otherwise it wouldn''t be random).
127-
128-
129-
#### Editing a cell
130-
131-
132-
You can edit a cell at any time, including SQL cells which will then run the
133-
new query immediately.
134-
135-
136-
#### Deleting a cell
137-
138-
139-
Deleting a cell is pretty easy: just click on the delete button in the top right
140-
corner. You''ll have 10 seconds to undo the delete if you so desire; we wouldn''t
141-
want you to lose your work because of an accidental click.
142-
143-
144-
#### Shortcuts
145-
146-
147-
The text editor supports the following helpful shortcuts:
148-
149-
150-
151-
| Shortcut | Description |
152-
153-
-----------| --------------------------------------
154-
155-
| `Cmd-/` or `Ctrl-/` | Comment out SQL code. |
156-
157-
| `Cmd-Enter` or `Ctrl-Enter` | Save/create a cell.|
158-
159-
160-
By the way, this was a Markdown table, you can make those here as well.'
161-
rendering: '<article class="markdown-body"><p>I just asked Postgres to give me
133+
the result of `random()` is a float between 0 and 1. On the bottom right corner,
134+
you can see that it took `0:00:00.000654` or 0 hours, 0 minutes, 0 seconds and
135+
only 654ns, or 0.6ms. This run time is good to keep an eye on. It will help
136+
build an intuition for how fast Postgres really is, and how certain operations
137+
scale as the data grows. You'll be able to see how long \n\nTry rerunning the
138+
cell again by clicking the \"play\" button in the top right corner. You'll see
139+
that the random number will change. Rerunning is a real time operation and Postgres
140+
will give you a different random number every time (otherwise it wouldn't be
141+
random).\n\n#### Editing a cell\n\nYou can edit a cell at any time, including
142+
SQL cells which will then run the new query immediately.\n\n#### Deleting a
143+
cell\n\nDeleting a cell is pretty easy: just click on the delete button in the
144+
top right corner. You'll have 10 seconds to undo the delete if you so desire;
145+
we wouldn't want you to lose your work because of an accidental click.\n\n####
146+
Shortcuts\n\nThe text editor supports the following helpful shortcuts:\n\n\n|
147+
Shortcut | Description |\n-----------| --------------------------------------\n|
148+
`Cmd-/` or `Ctrl-/` | Comment out SQL code. |\n| `Cmd-Enter` or `Ctrl-Enter`
149+
| Save/create a cell.|\n\nBy the way, this was a Markdown table, you can make
150+
those here as well."
151+
rendering: '<article class="markdown-body"><p>We just asked Postgres to return
162152
a random number. Pretty simple query, but it demonstrates the notebook functionality
163-
pretty well. You can see that the result of <code>random()</code> is currently
164-
<code>0.6822832295608556</code>. On the bottom right corner, you can see that
165-
it took <code>0:00:00.000654</code> or 0 hours, 0 minutes, 0 seconds and only
166-
00006ns, which I believe is 0.6ms, for Postgres to run this query for us. This
167-
runtime is good to know, because you''ll be able to benchmark some of PostgresML
168-
functionality, including the models we provide, right here in these notebooks.</p>
153+
pretty well. You can see that the result of <code>random()</code> is a float
154+
between 0 and 1. On the bottom right corner, you can see that it took <code>0:00:00.000654</code>
155+
or 0 hours, 0 minutes, 0 seconds and only 654ns, or 0.6ms. This run time is
156+
good to keep an eye on. It will help build an intuition for how fast Postgres
157+
really is, and how certain operations scale as the data grows. You''ll be able
158+
to see how long </p>
169159
170160
<p>Try rerunning the cell again by clicking the "play" button in the top right
171161
corner. You''ll see that the random number will change. Rerunning is a real
@@ -237,14 +227,19 @@
237227
238228
239229
Thank you for trying out PostgresML! We hope you enjoy your time here and have
230+
fun learning about machine learning, in the comfort of your favorite database.
231+
240232
241-
fun learning about machine learning, in the comfort of your favorite database.'
233+
You may want to check out the [rest of the tutorial''s](/nb/) or dive straight
234+
in with a notebook to test [real time fraud detection](/notebooks/notebook/1/).'
242235
rendering: '<article class="markdown-body"><h3>Thank you</h3>
243236
244237
<p>Thank you for trying out PostgresML! We hope you enjoy your time here and
245-
have
238+
have fun learning about machine learning, in the comfort of your favorite database.</p>
246239
247-
fun learning about machine learning, in the comfort of your favorite database.</p></article>'
240+
<p>You may want to check out the <a href="/nb/">rest of the tutorial''s</a>
241+
or dive straight in with a notebook to test <a href="/notebooks/notebook/1/">real
242+
time fraud detection</a>.</p></article>'
248243
execution_time: null
249244
cell_number: 4
250245
version: 1
@@ -255,11 +250,8 @@
255250
notebook: 0
256251
cell_type: 3
257252
contents: SELECT 'Have a nice day!' AS greeting;
258-
rendering: "<div class=\"markdown-body\">\n<table>\n <thead>\n <tr>\n \n
259-
\ <td><strong>greeting</strong></td>\n \n </tr>\n </thead>\n <tbody>\n
260-
\ \n <tr>\n \n <td>Have a nice day!</td>\n \n </tr>\n
261-
\ \n </tbody>\n</table>\n</div>\n"
262-
execution_time: '00:00:00.000580'
253+
rendering: null
254+
execution_time: null
263255
cell_number: 5
264256
version: 1
265257
deleted_at: null

0 commit comments

Comments
 (0)