Skip to content

Commit 314f3bd

Browse files
committed
Update README.md
More README updates in my series - open to debate about if the pic should be above some of this text. @channemann @scottleibrand @bewest etc. (I unlinked from the wiki/getting started and directed toward our docs since that's currently the most up to date piece of work to help people)
1 parent 957f248 commit 314f3bd

File tree

1 file changed

+30
-2
lines changed

1 file changed

+30
-2
lines changed

README.md

+30-2
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,36 @@
44
These are the [core utilities][proposal] needed to develop an open source
55
artificial pancreas.
66

7-
See our [wiki for more information][wiki], including how to
8-
[get started with openaps][GettingStarted].
7+
This is part of a series of tools to support a self-driven DIY
8+
implementation based on the OpenAPS reference design. The tools may be
9+
categorized as *monitor* (collecting data about environment, and
10+
operational status of devices and/or aggregating as much data as is
11+
relevant into one place), *predict* (make predictions about what should
12+
happen next), or *control* (enacting changes, and feeding more data back
13+
into the *monitor*).
14+
15+
By proceeding using these tools or any piece within, you agree to the
16+
copyright (see LICENSE.txt for more information) and release any
17+
contributors from liability.
18+
19+
Check out [the openaps docs] (https://openaps.gitbooks.io/building-an-open-artificial-pancreas-system/content/index.html) to help get you started.
20+
21+
*Note:* This is intended to be a set of tools to support a self-driven DIY
22+
implementation and any person choosing to use these tools is solely
23+
responsible for testing and implement these tools independently or
24+
together as a system. The [DIY part of OpenAPS is important]
25+
(http://bit.ly/1NBbZtO). While formal training or experience as an
26+
engineer or a developer is not required, what *is* required is a growth
27+
mindset to learn what are essentially "building blocks" to implement an
28+
OpenAPS instance. This is not a "set and forget" system; it requires
29+
diligent and consistent testing and monitoring to ensure each piece of
30+
the system is monitoring, predicting, and performing as desired. The
31+
performance and quality of your system lies solely with you.
32+
33+
Additionally, this community of contributors believes in "paying it
34+
forward", and individuals who are implementing these tools are asked to
35+
contribute by asking questions, helping improve documentation, and
36+
contribute in other ways.
937

1038
[GettingStarted]: https://github.com/openaps/openaps/wiki/GettingStarted
1139
[wiki]: https://github.com/openaps/openaps/wiki

0 commit comments

Comments
 (0)