New instruments added

[mizfit]

Here are a couple instruments with functions (need to be reviewed to include error checking.)

[greynotgrayskies]

I'm not sure if we need a Sensor class. I thought of organizing instruments into actuators and sensors, but in the case where instruments do both, it might get confusing. Right now, it isn't very clear that the instrument can record data, but once I add an interface for that, I'll clean up here a bit.

[vassiliou]

I agree. Most instruments will both accept and return values. What we
choose to do with that data varies, but from the software's perspective
it's all the same.

On Tue, Jan 19, 2016 at 3:33 PM, jeffreylu017 [email protected]
wrote:

I'm not sure if we need a Sensor class. I thought of organizing
instruments into actuators and sensors, but in the case where instruments
do both, it might get confusing. Right now, it isn't very clear that the
instrument can record data, but once I add an interface for that, I'll
clean up here a bit.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[mizfit]

Agreed. I wasn't quite sure in which class to place the Hall Probe (DTM
141), so I introduced the Sensor class, though perhaps in retrospect that
can be a bit confusing.

On Wed, Jan 20, 2016 at 1:33 AM, vassiliou [email protected] wrote:

I agree. Most instruments will both accept and return values. What we
choose to do with that data varies, but from the software's perspective
it's all the same.

On Tue, Jan 19, 2016 at 3:33 PM, jeffreylu017 [email protected]
wrote:

I'm not sure if we need a Sensor class. I thought of organizing
instruments into actuators and sensors, but in the case where instruments
do both, it might get confusing. Right now, it isn't very clear that the
instrument can record data, but once I add an interface for that, I'll
clean up here a bit.

—
Reply to this email directly or view it on GitHub
<
#5 (comment)

.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.