edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-107) Add sample use of new Range class in recipe3 - detect value out of range?
Date Tue, 05 Apr 2016 23:03:25 GMT

    [ https://issues.apache.org/jira/browse/QUARKS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227321#comment-15227321
] 

ASF GitHub Bot commented on QUARKS-107:
---------------------------------------

Github user ddebrunner commented on a diff in the pull request:

    https://github.com/apache/incubator-quarks/pull/75#discussion_r58628617
  
    --- Diff: samples/utils/src/main/java/quarks/samples/utils/sensor/SimulatedTemperatureSensor.java
---
    @@ -0,0 +1,110 @@
    +/*
    +Licensed to the Apache Software Foundation (ASF) under one
    +or more contributor license agreements.  See the NOTICE file
    +distributed with this work for additional information
    +regarding copyright ownership.  The ASF licenses this file
    +to you under the Apache License, Version 2.0 (the
    +"License"); you may not use this file except in compliance
    +with the License.  You may obtain a copy of the License at
    +
    +  http://www.apache.org/licenses/LICENSE-2.0
    +
    +Unless required by applicable law or agreed to in writing,
    +software distributed under the License is distributed on an
    +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    +KIND, either express or implied.  See the License for the
    +specific language governing permissions and limitations
    +under the License.
    +*/
    +
    +package quarks.samples.utils.sensor;
    +
    +import java.text.DecimalFormat;
    +import java.util.Objects;
    +import java.util.Random;
    +
    +import quarks.analytics.sensors.Range;
    +import quarks.analytics.sensors.Ranges;
    +import quarks.function.Supplier;
    +
    +/**
    + * A Simulated temperature sensor.
    + * <p>
    + * The sensor starts off with an initial value.
    + * Each call to {@link #get()} changes the current value by
    + * a random amount between plus/minus a {@code deltaFactor}.
    + * The new current value is limited to a {@code maxTempRange}.
    + * <p>
    + * Temperature values are in Fahrenheit.
    --- End diff --
    
    'Temperature values are in Fahrenheit."
    
    Isn't that up to whoever is creating an instance?
    
    The default constructor maps to a normal air temperature Fahrenheit range, but wouldn't
something like this be suitable for Kelvin around the same range?
    
    `new SimulatedTemperatureSensor(300, Ranges.closed(265, 315), 0.5);`



> Add sample use of new Range class in recipe3 - detect value out of range?
> -------------------------------------------------------------------------
>
>                 Key: QUARKS-107
>                 URL: https://issues.apache.org/jira/browse/QUARKS-107
>             Project: Quarks
>          Issue Type: Improvement
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>              Labels: newbie
>
> Add sample use of new Range class in recipe3 - detect value out of range?
> Either or both of the recipe's existing samples could be use Range, or one of them could
be cloned to use it.
> ```
> TStream<Double> simpleFiltered = temp.filter(tuple ->
>             tuple < TEMP_LOW || tuple > TEMP_HIGH);
> // could be
> TStream<Double> simpleFiltered = temp.filter(Ranges.open(TEMP_LOW, TEMP_HIGH);
> TStream<Double> deadbandFiltered = Filters.deadband(temp,
>             identity(), tuple -> tuple >= TEMP_LOW && tuple <= TEMP_HIGH);
> // could instead be
> TStream<Double> deadbandFiltered = Filters.deadband(temp,
>             identity(), Ranges.closed(TEMP_LOW, TEMP_HIGH));
> ```
> Use of a Range simplifies the code a bit.  I can also avoid mistakes if one's code "duplicates"
the expressions for a particular range in multiple places.  
> Using Range can be more compelling for the simplicity with which a range may be expressed
and created from a config file for an app.  e.g. imagine how one would express the range in
a Properties config file.  A range property value in a Properties file would simply be:
> ```
> # my sensor filter range
> myFilterRange=[71.0..98.0]
> ```
> and the app code to create the Range would simply be:
> ```
> Range<Double> myFilterRange = Ranges.valueOfDouble(props.getProperty("myFilterRange"));
> ```
> Another compelling case is making a filter range dynamically changeable, for example
as a result of some received IoT "device command".  The range could be declared like:
> ```
> AtomicReference<Range<Double>> myFilterRange = new AtomicReference<>(
>     Ranges.valueOfDouble(props.getProperty("myFilterRange"));  // initial range value
> // code in the device's set-filter-range cmd handler is ultimately:
> //   myFilterRange.set(Ranges.valueOfDouble(the-new-range-string-from-the-cmd));  //
sets a new Range object
> // Using the changeable filter range is simply:
> TStream<Double> simpleFiltered = temp.filter(myFilterRange.get());
> ```
> Dynamic filter Predicates is probably a good recipe unto itself :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message