Ambient-Oriented Programming

User Tools

Site Tools

Trace:
crime:sunspot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
crime:sunspot [2011/04/24 14:33]
wamerijc 		crime:sunspot [2011/06/02 12:51] (current)
wamerijc
Line 1: Line 1:
-====== Event Crime ======+====== CrimeSPOT ======
 CRIME has been ported for wireless sensor networks.  CRIME has been ported for wireless sensor networks. 
 In this project we have used sunspots, small nodes equipped with sensors and wireless communication. In this project we have used sunspots, small nodes equipped with sensors and wireless communication.
 Every node sends events over the network which can be received by one or more nodes within communication range. Writing applications which are driven by external events is significantly different from writing traditional sequential programs or algorithms. When applications are driven by external events, the control flow of these applications is also driven by these events which can trigger at any order and at any moment in time. Every node sends events over the network which can be received by one or more nodes within communication range. Writing applications which are driven by external events is significantly different from writing traditional sequential programs or algorithms. When applications are driven by external events, the control flow of these applications is also driven by these events which can trigger at any order and at any moment in time.
  
-In this project we have used CRIME in order to deal with the complexity of composing and deriving meaningful information from a continuos stream of events received from the surrounding. While CRIME has been previously used for the development of context aware applications we have seen that CRIME did not scale for the development such event driven applications. We therefore had to significantly adapt the reasoning engine in order to deal with the transient nature of events.+In this project we have used CRIME in order to deal with the complexity of composing and deriving meaningful information from a continuous stream of events received from the surrounding. While CRIME has been previously used for the development of context aware applications we have seen that CRIME did not scale for the development such event driven applications. We therefore had to significantly adapt the reasoning engine in order to deal with the transient nature of events.
  
 <note> <note>
 This project is still under development, as such the documentation can be out of sync with actual implementation.  This project is still under development, as such the documentation can be out of sync with actual implementation. 
 </note> </note>
 +
  
 ===== Repository ===== ===== Repository =====
-The repository for Event CRIME is located at:+The repository for CrimeSPOT is located at:
  
 https://soft.vub.ac.be/svn-gen/projects/stadium/code/CrimeLoociSunspot https://soft.vub.ac.be/svn-gen/projects/stadium/code/CrimeLoociSunspot
Line 76: Line 77:
   # activate ID XXXX.XXXX.XXXX.XXXX   # activate ID XXXX.XXXX.XXXX.XXXX
  
-As can be observed, unlike LooCI components, it's not required to manually add wirings for CrimeSPOT components. The CrimeSPOT runtime automatically adds toAll&fromAll wirings for: +As can be observed, unlike for LooCI components, it's not required to manually add wirings for CrimeSPOT components. The CrimeSPOT runtime automatically adds toAll&fromAll wirings for: 
  
 - the internal CrimeSPOT event types, - the internal CrimeSPOT event types,
Line 90: Line 91:
  
  
 +====== Creating a CrimeSPOT Component ======
 +===== Netbeans =====
 +Individual CrimeSPOT components can be created in Netbeans.
 +
 +Steps:
 +
 +1. Create a New Project: Sun SPOT Application
 +
 +2. Extend the abstract CrimeComponent class and give an implementation for:
 +
 +  o execute(): invoked when the component is activated; expressions can be installed via processExpression(String) or registerRule(String,Action)
 +
 +  o all methods invoked from within the interaction rules (cfr. is-operator) && invoke(String,Object[]); the dispatcher method to access these methods
 +
 +3. Compile the component:
 +
 +  $ ant jar-app
 +
 +===== Macro-CrimeSPOT =====
 +==== The network-level dialect ====
 +A CrimeSPOT WSN application can be created from the network-level perspective in the Macro-CrimeSPOT dialect.
 +
 +Examples can be found on https://soft.vub.ac.be/svn-gen/projects/stadium/code/CrimeLoociSunspot/Macro_CRIMESpot/Examples/.
 +
 +==== The precompiler ====
 +The precompiler for compiling Macro-CrimeSPOT code to node-level component jars can be obtained via SVN:
 +
 +1. Checkout the Eclipse project from https://soft.vub.ac.be/svn-gen/projects/stadium/code/CrimeLoociSunspot/Macro_CRIMESpot/ & compile.
 +
 +2. Use edu.vub.crimespot.precompiler.Main to compile a source file
  
 +3. The resulting components can be found in Macro_CRIMESpot/components. Their Java code can be further refined, or the jars can be deployed immediately on SunSPOTs.
crime/sunspot.1303648387.txt.gz ยท Last modified: 2011/04/24 15:02 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki