Design of Home Network Architecture using ACE/TAO Real Time Event Service

This paper proposes a home network design based on publisher/subscriber architecture which is developed using ACE/TAO Real-time Event Service (RTES) as the middleware platform. This design addresses a feature to support a real-time implementation for home network application such as home automation. Home network participants have been classified into several components based on consumer and supplier implementation in the ACE/TAO RTES in order to simplify the design. To optimize the network utilization, events are filtered based on their type and source for each publisher and subscriber. To deal with heterogeneous type of home appliances, event header information has been extended to wrap more information. Each of events can be configured with a specific scheduling and priority setting to meet its quality of service (QoS) according to the requirement. Network performance in handling an increasing number of consumer or supplier has been evaluated and show an acceptable result. Keywords: Home Network, ACE/TAO, RTES, QoS

Distributed simulation and the grid: Position statements

The Grid provides a new and unrivaled technology for large scale distributed simulation as it enables collaboration and the use of distributed computing resources. This panel paper presents the views of four researchers in the area of Distributed Simulation and the Grid. Together we try to identify the main research issues involved in applying Grid technology to distributed simulation and the key future challenges that need to be solved to achieve this goal. Such challenges include not only technical challenges, but also political ones such as management methodology for the Grid and the development of standards. The benefits of the Grid to end-user simulation modelers also are discussed

Abnormal proactive and reactive cognitive control during conflict processing in major depression

According to the Dual Mechanisms of Control framework, cognitive control consists of two complementary components: proactive control refers to anticipatory maintenance of goal-relevant information, whereas reactive control acts as a correction mechanism that is activated when a conflict occurs. Possibly, the well-known diminished inhibitory control in response to negative stimuli in Major Depressive Disorder (MDD) patients stems from a breakdown in proactive control, and/or anomalies in reactive cognitive control. In our study, MDD patients specifically showed increased response latencies when actively inhibiting a dominant response to a sad compared with a happy face. This condition was associated with a longer duration of a dominant ERP topography (800-900 ms poststimulus onset) and a stronger activity in the bilateral dorsal anterior cingulate cortex, reflecting abnormal reactive control when inhibiting attention to a negative stimulus. Moreover, MDD patients showed abnormalities in proactive cognitive control when preparing for the upcoming imperative stimulus (abnormal modulation of the contingent negative variation component), accompanied by more activity in brain regions belonging to the default mode network. All together, deficits to inhibit attention to negative information in MDD might originate from an abnormal use of both proactive resources and reactive control processes. This document is copyrighted by the American Psychological Association or one of its allied publishers. This article is intended solely for the personal use of the individual user and is not to be disseminated broadly

A model-driven approach to broaden the detection of software performance antipatterns at runtime

Performance antipatterns document bad design patterns that have negative influence on system performance. In our previous work we formalized such antipatterns as logical predicates that predicate on four views: (i) the static view that captures the software elements (e.g. classes, components) and the static relationships among them; (ii) the dynamic view that represents the interaction (e.g. messages) that occurs between the software entities elements to provide the system functionalities; (iii) the deployment view that describes the hardware elements (e.g. processing nodes) and the mapping of the software entities onto the hardware platform; (iv) the performance view that collects specific performance indices. In this paper we present a lightweight infrastructure that is able to detect performance antipatterns at runtime through monitoring. The proposed approach precalculates such predicates and identifies antipatterns whose static, dynamic and deployment sub-predicates are validated by the current system configuration and brings at runtime the verification of performance sub-predicates. The proposed infrastructure leverages model-driven techniques to generate probes for monitoring the performance sub-predicates and detecting antipatterns at runtime.Comment: In Proceedings FESCA 2014, arXiv:1404.043