device_control 0.0.0.3 → 0.1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cf0616f0c1a9a604310b793eea313261cc6f70ecefe3a401ae3df83b973a4f45
-  data.tar.gz: 7ad33892bf3ad7420d4c72f3c94efe0aa9861889427d1028cba27a2fd1bc9fb1
+  metadata.gz: bdcd9344b15b304432916abc67301349241f87f6001e1b8501ed391e810adccf
+  data.tar.gz: 601ff3ef86d511d25ee7357b3798580f57f1afba3efccb9647d8b77ac7c165d4
 SHA512:
-  metadata.gz: 1c71afb1964f420e16fa7941e7470cf33c19183218d3bb97f040f34047d653b3e52d1f86e2874ff96997caf5de38a9902f9d4e112f25a516bd1e316da40f79c3
-  data.tar.gz: a24a1a3e8d7dd72b3f30a4470f5cff0a5590c1c7ec00c76b711e5c91d9e799386182477a1400f57d3a2d701375ecfa417c11fcf36d8e3bbde9f09d75d50db802
+  metadata.gz: 5ce49d473ee9c6c380f1e1f91b254b529db2a04bdc3652786d84a8e5c9c88b8a495530256ebbff5d4f60fe9e6323be6c965d85eda1161a378a048b329a8c017a
+  data.tar.gz: 850d60e4173e84cbb2cd3aea55502a9b159e220c8dbed038f3b7391c6594ffe428c38dd6e0ed149f5ae0fd5d732f1ea74a47285f3975a8ce73c6986947efe36f

data/README.md

@@ -52,7 +52,7 @@ to make sense.
 Our control loop is composed of the 3 concepts above:
 
 ```
-CONTROLLER  ==>  DEVICE
+CONTROLLER ----> DEVICE
         ^         |
         |         |
         |         V
@@ -215,6 +215,10 @@ class Thermostat < Controller
 end
 ```
 
+Notice, the thermostat essentially answers the question: *is it hot enough?*
+(or: *is it too cold?*).  You can run it either or both ways, but notice that
+you can simply pick one orientation and remain logically consistent.
+
 Now consider:
 
 ```ruby
@@ -237,15 +241,12 @@ temp = 24.9
 
 ```
 
-Notice, the thermostat essentially answers the question: *is it hot enough?*
-(or: *is it too cold?*).  You can run it either or both ways, but notice that
-you can simply pick one orientation and remain logically consistent.  So the
-**heat knob** goes to 1 when its thermostat goes *below* setpoint.
+So the **heat knob** goes to 1 when its thermostat goes *below* setpoint.
 The **cool knob** goes to 1 when its thermostat goes *above* setpoint.
 
 # Finale
 
 If you've made it this far, congratulations!  For further reading:
 
-* [lib/pid_controller.rb](lib/pid_controller.rb#L155)
-* [test/pid_controller.rb](test/pid_controller.rb)
+* [lib/device_control.rb](lib/device_control.rb#L155)
+* [test/device_control.rb](test/device_control.rb)

data/VERSION

@@ -1 +1 @@
-0.0.0.3
+0.1.0.1

data/test/{pid_controller.rb → device_control.rb}

@@ -1,4 +1,4 @@
-require 'pid_controller'
+require 'device_control'
 require 'minitest/autorun'
 
 # create a basic class that includes Updateable as a Mixin

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: device_control
 version: !ruby/object:Gem::Version
-  version: 0.0.0.3
+  version: 0.1.0.1
 platform: ruby
 authors:
 - Rick Hull
@@ -20,8 +20,8 @@ files:
 - Rakefile
 - VERSION
 - device_control.gemspec
-- lib/pid_controller.rb
-- test/pid_controller.rb
+- lib/device_control.rb
+- test/device_control.rb
 homepage: https://github.com/rickhull/device_control
 licenses:
 - LGPL-3.0