Return-Path: X-Original-To: apmail-quarks-dev-archive@minotaur.apache.org Delivered-To: apmail-quarks-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BE00C19770 for ; Tue, 5 Apr 2016 17:18:36 +0000 (UTC) Received: (qmail 40068 invoked by uid 500); 5 Apr 2016 17:18:36 -0000 Delivered-To: apmail-quarks-dev-archive@quarks.apache.org Received: (qmail 40041 invoked by uid 500); 5 Apr 2016 17:18:36 -0000 Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@quarks.incubator.apache.org Delivered-To: mailing list dev@quarks.incubator.apache.org Received: (qmail 40030 invoked by uid 99); 5 Apr 2016 17:18:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2016 17:18:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AAC7D1A4695 for ; Tue, 5 Apr 2016 17:18:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id vQdVlvt-QGvJ for ; Tue, 5 Apr 2016 17:18:34 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id E4F595F59E for ; Tue, 5 Apr 2016 17:18:33 +0000 (UTC) Received: (qmail 40020 invoked by uid 99); 5 Apr 2016 17:18:33 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2016 17:18:33 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0B01CDFC6E; Tue, 5 Apr 2016 17:18:33 +0000 (UTC) From: queeniema To: dev@quarks.incubator.apache.org Reply-To: dev@quarks.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-quarks-website pull request: [QUARKS-107] Add use of Ran... Content-Type: text/plain Message-Id: <20160405171833.0B01CDFC6E@git1-us-west.apache.org> Date: Tue, 5 Apr 2016 17:18:33 +0000 (UTC) Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-quarks-website/pull/32#discussion_r58578295 --- Diff: site/recipes/recipe_value_out_of_range.md --- @@ -137,6 +137,36 @@ When the final application is run, the output looks something like the following Note that the deadband filter outputs a warning message for the very first temperature reading of 79.1°F. When the temperature falls to 76.5°F (which is outside the optimal range), both the simple filter and deadband filter print out a warning message. However, when the temperature returns to normal at 77.5°F, only the deadband filter prints out a message as it is the first value inside the optimal range after a period of being outside it. +## Range values + +Filtering against a range of values is such a common analytic activity that the ``quarks.analytics.sensors.Range`` class is provided to assist with that. + +Using a Range can simplify and clarify your application code and lessen mistakes that may occur when writing expressions to deal with ranges. +Though not covered in this recipe, Ranges offer additional conveniences for creating applications with external range specifications and adaptable filters. + +In the above examples, a single Range can be used in place of the two +different expressions for the same logical range: --- End diff -- @dlaboss For consistency, could you combine these two lines into one? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---