Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Operating a low-latency data access and analysis system using domain-specific chronometry may include obtaining, in the low-latency data access and analysis system, data expressing usage intent with respect to the low-latency data access and analysis system, in response to obtaining the data expressing usage intent, obtaining ontological data for a chronometric object in the low-latency data access and analysis system indicated by the data expressing usage intent, identifying a chronometry dataset from a plurality of chronometry datasets, wherein the plurality of chronometry datasets includes a domain-specific chronometry dataset and a canonical chronometry dataset, obtaining results data in accordance with the chronometry dataset and the chronometric object, generating output data representing the results data in accordance with the chronometry dataset, and outputting the output data for presentation via a user interface.

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining, in the low-latency database analysis system, data expressing a usage intent with respect to the low-latency database analysis system, in response to obtaining the data expressing the usage intent, obtaining ontological data for a chronometric object in the low-latency database analysis system indicated by the data expressing the usage intent, identifying a chronometry dataset from a plurality of chronometry datasets, wherein the plurality of chronometry datasets includes a domain-specific chronometry dataset and a canonical chronometry dataset, obtaining results data in accordance with the chronometry dataset and the chronometric object, generating output data representing the results data in accordance with the chronometry dataset, and outputting the output data for presentation via a user interface.

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining, in the low-latency database analysis system, data expressing a usage intent with respect to the low-latency database analysis system, in response to obtaining the data expressing the usage intent, obtaining ontological data for a chronometric object in the low-latency database analysis system indicated by the data expressing the usage intent, identifying a chronometry dataset from a plurality of chronometry datasets, wherein the plurality of chronometry datasets includes a domain-specific chronometry dataset and a canonical chronometry dataset, obtaining results data in accordance with the chronometry dataset and the chronometric object, generating output data representing the results data in accordance with the chronometry dataset, and outputting the output data for presentation via a user interface.

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Systems and techniques for monitoring driver state are described herein. In an example, a driver state monitoring system is adapted to receive a set of color images of a person, such as images of a driver of a vehicle with varying levels of illumination in the images. The driver state monitoring system may be further adapted to generate a set of synthesized thermal images from the set of color images. The driver state monitoring system may be further adapted to use a trained thermal image face detector to locate a human face in the synthesized thermal images. The driver state monitoring system may be further adapted to use a trained thermal image facial landmark predictor to locate facial landmarks in the synthesized thermal images. The driver state monitoring system may be further adapted to analyze the facial landmarks in the synthesized thermal images to determine facial feature movements.

Abstract: A method for print scaling includes receiving, at a computing device, a request to print a digital markup-based document as a printed document, the digital markup-based document including one or more markup tags of a markup-based language specifying formatting of the markup-based document. Target page dimensions are received for the printed document, including at least a target page height. A native-background print view of the digital markup-based document is rendered, the native-background print view having a format compatible with a print driver of the computing device. Rendered dimensions of the native-background print view are calculated. The native-background print view is resealed into a scaled-background print view having a print height that is a function of the target page height by applying a height scaling factor to the native-background print view. The scaled-background print view is output for printing.

Abstract: Systems and techniques for monitoring driver state are described herein. In an example, a driver state monitoring system is adapted to receive a set of color images of a person, such as images of a driver of a vehicle with varying levels of illumination in the images. The driver state monitoring system may be further adapted to generate a set of synthesized thermal images from the set of color images. The driver state monitoring system may be further adapted to use a trained thermal image face detector to locate a human face in the synthesized thermal images. The driver state monitoring system may be further adapted to use a trained thermal image facial landmark predictor to locate facial landmarks in the synthesized thermal images. The driver state monitoring system may be further adapted to analyze the facial landmarks in the synthesized thermal images to determine facial feature movements.

Abstract: Methods and arrangements for providing cooperative caching in a distributed system. A cache and a communicator are provided at a node in a distributed system. The communicator is used to communicate with at least one other node with respect to related data stored at the node and the at least one other node, via: communicating a status of the cache at the node and receiving notification of a status of at least one cache of at least one other node. There is updated, upon communicating with the at least one other node, at least one of: a cache replacement policy at the node and a cache pre-fetching policy at the node. Other variants and embodiments are broadly contemplated herein.

Abstract: Methods and arrangements for providing cooperative caching in a distributed system. A cache and a communicator are provided at a node in a distributed system. The communicator is used to communicate with at least one other node with respect to related data stored at the node and the at least one other node, via: communicating a status of the cache at the node and receiving notification of a status of at least one cache of at least one other node. There is updated, upon communicating with the at least one other node, at least one of: a cache replacement policy at the node and a cache pre-fetching policy at the node. Other variants and embodiments are broadly contemplated herein.

Abstract: Embodiments of the invention relate to systems, methods, and computer program products for implementing a customer loyalty rewards program by assigning point values to a customer's completion of certain activities, monitoring the customer's activities to determine when the customer has completed an activity, crediting the customer the assigned value of points for the completed activities, correlating points to one or more rewards and facilitating the exchange of rewards.

Abstract: Embodiments of the invention relate to systems, methods, and computer program products for allowing a customer to choose rewards as part of a customer incentive program by receiving a first customer input, wherein the first customer input is a characteristic of the customer, receiving a second customer input, wherein the second customer input is a category of reward in which the customer is interested, correlating the first customer input to a plurality of activities to be completed by the customer, correlating the second customer input to rewards to be provided to the customer for completing an activity, monitoring the customer's activities to determine when the customer has completed an activity and providing a reward to the customer corresponding to the completed activity.

Abstract: A budget monitoring, alerting and bill payment facilitation system retrieves macro-budgeting information associated with a user, where the macro-budgeting information includes a plurality of budget categories each having an associated budget amount corresponding to a macro time period, divides the budget amount corresponding to the macro time period into a plurality of micro budget amounts corresponding to a plurality of micro time periods, and presents, to the user by a mobile device, micro-budgeting information corresponding to at least one of the plurality of micro budget amounts or its corresponding micro time period. In some embodiments, the system retrieves user data, determines the user may be experiencing a life event based on the user data, where the micro-budgeting information is based on the determination that the user may be experiencing a life event, and confirms that the user is experiencing a life event.

Abstract: A context-aware mobile banking system determines a location of a user of the mobile device, identifies at least one product of interest to the user based at least in part on the determined location of the user, determines based on the determined product of interest, information corresponding to the product of interest, and presents the information corresponding to the product of interest to the user. In some embodiments, the system retrieves user budgeting information including a plurality of budget categories each having an associated budget amount and an associated remaining amount indicating an amount remaining in from the budget amount, determines a budget category from the plurality of budget categories associated with the product of interest, and determines the budget amount and remaining amount associated with the determined budget category. The system then may present information corresponding to the remaining amount and the budget amount to the user.