Changes for page Products

From version 13.1
edited by Nazzareno Pompei
on 08/10/2020 00:15
Change comment: There is no comment for this version
To version 19.1
edited by Andrea Omicini
on 12/12/2020 00:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.NazzarenoPompei
1 +XWiki.AndreaOmicini
Content
... ... @@ -12,7 +12,7 @@
12 12  #alchemist() is a simulation framework offering both high performance and flexibility. Alchemist tries to get the best from ABMs and stochastic simulators and build an hybrid.
13 13  
14 14  *Space*: [#alchemist() Home|Alchemist.WebHome]
15 -\\
15 +<br />
16 16  *Contact*: [Danilo Pianini|DaniloPianini.WebHome]
17 17  
18 18  
... ... @@ -24,7 +24,7 @@
24 24  ALOO is the most recent evolution of the simpAL project.
25 25  
26 26  *Space*: [ALOO Home|ALOO.WebHome]
27 -\\
27 +<br />
28 28  *Contact*: [Alessandro Ricci|AlessandroRicci.WebHome]
29 29  
30 30  
... ... @@ -35,7 +35,7 @@
35 35  #cartago() is based on the #aea() (Agents and Artifacts) meta&#45;model model, which introduces the ~~artifact~~ abstraction as a first&#45;class building block to model and engineer those objects, resources, tools, that can be dynamically constructed, shared and co-used by agents to perform their activities, both individual and social.
36 36  
37 37  *Space*: [#cartago() Home|CARTAGO.WebHome]
38 -\\
38 +<br />
39 39  *Contact*: [Alessandro Ricci|AlessandroRicci.WebHome]
40 40  
41 41  
... ... @@ -48,7 +48,7 @@
48 48  The implementation is Java-based, developed on top of the TuCSoN agent infrastructure, and deployable also on low-cost devices such as Raspberry PI2.
49 49  
50 50  *Space*: [#hm() Home|Products.HomeManager]
51 -\\
51 +<br />
52 52  *Contact*: [Roberta Calegari|RobertaCalegari.WebHome]
53 53  
54 54  
... ... @@ -59,7 +59,7 @@
59 59  #moklong() (#mok() for short) is a model for knowledge self-organisation, exploiting the biochemical metaphor for its basic abstractions, and biochemical coordination as its coordination model.
60 60  
61 61  *Space*: [#mok() Home|MoK.WebHome]
62 -\\
62 +<br />
63 63  *Contact*: [Stefano Mariani|StefanoMariani.WebHome]
64 64  
65 65  1.1 MS-BioNET
... ... @@ -67,7 +67,7 @@
67 67  MS-BioNet (MultiScale-Biochemical NETwork) is a computational framework for modelling and simulating large networks of compartments hosting a chemical solution and communicating through an enhanced model of chemical reaction addressing molecule transfer.
68 68  
69 69  *Space*: [MS-BioNET Home|MS-BioNET.WebHome]
70 -\\
70 +<br />
71 71  *Contact*: [Sara Montagna|SaraMontagna.WebHome]
72 72  
73 73  1.1 P@J
... ... @@ -79,7 +79,7 @@
79 79  * an annotation layer, that aims at truly extending Java programming with the ability of specifying Prolog&#45;based declarative implementations of Java methods, relying on Java annotations.
80 80  
81 81  *Space*: [P@J|Tuprolog.PatJ]
82 -\\
82 +<br />
83 83  *Contact*: [Mirko Viroli|MirkoViroli.WebHome]
84 84  
85 85  
... ... @@ -86,9 +86,9 @@
86 86  1.1 #respect()
87 87  
88 88  {image:r_logo.png|109|100|left|floatleft}
89 -\\
89 +
90 90  #respect() is a logic-based coordination language both to define the behaviour of tuple centres and to coordinate software agents.
91 -\\
91 +
92 92  #respect() assumes a tuple-based coordination model, where communication is based on logic tuples, and the behaviour of the coordination media in response to communication events is not fixed once and for all by the coordination model, but can be defined and tailored according to system's global requirements.
93 93  According to this conceptual framework, #respect() has a twofold role:
94 94  
... ... @@ -96,19 +96,19 @@
96 96  * as a reaction language - #respect() supports the notion of reaction as a computational activity to be executed locally to a tuple centre in response to communication events, by providing for both a logic-based syntax for the definition of reactions, and a model for their execution.
97 97  
98 98  *Space*: [#respect() Home|ReSpecT.WebHome]
99 -\\
99 +<br />
100 100  *Contact*: [Stefano Mariani|StefanoMariani.WebHome]
101 101  
102 102  1.1 #simpa()
103 103  
104 104  {image:simpa-logo.jpg|109|100|left|floatleft}
105 -\\
105 +
106 106  #simpa() is a framework extending the basic Java environment with an agent-oriented abstraction layer for programming complex (concurrent in particular) applications.
107 -\\
107 +
108 108  #simpa() is based on the #aea() (Agents and Artifacts) programming model, which introduces high-level metaphors taken from human society, namely agents &#45; analogous to humans, as executors of activities and activities &mdash; and artifacts &mdash; analogous of the objects, resources, tools that are dynamically constructed, used, manipulated by humans to support / realise their individual and social activities.
109 109  
110 110  *Space*: [#simpa() Home|SimpA.WebHome]
111 -\\
111 +<br />
112 112  *Contact*: [Alessandro Ricci|AlessandroRicci.WebHome]
113 113  
114 114  1.1 simpAL
... ... @@ -120,7 +120,7 @@
120 120  Differently from #simpa(), simpAL is not a Java extension, but a fully independent language and platform.
121 121  
122 122  *Space*: [simpAL Home|SimpAL.WebHome]
123 -\\
123 +<br />
124 124  *Contact*: [Alessandro Ricci|AlessandroRicci.WebHome]
125 125  
126 126  1.1 #soda()
... ... @@ -131,7 +131,7 @@
131 131  Recently a new and extended version of the methodology has been proposed, which takes into account both the Agents and Aartifacts (#aea()) meta-model, and a mechanism to manage the complexity of system description.
132 132  
133 133  *Space*: [#soda() Home|SODA.WebHome]
134 -\\
134 +<br />
135 135  *Contact*: [Ambra Molesini|AmbraMolesini.WebHome]
136 136  
137 137  1.1 #traumatracker()
... ... @@ -140,10 +140,10 @@
140 140  
141 141  Developed in collaboration with the Trauma Center and the Emergency Department of the "Bufalini" Hospital in Cesena, Italy, #traumatracker() is a project in which agent technologies are exploited to realise Personal Medical Digital Assistant Agents (PMDA) supporting a Trauma Team in trauma management operations. This project aims at exploring the fruitful integration of software personal agents with wearable/eyewear computing, based on mobile and wearable devices such as smart-glasses.
142 142  
143 -The key functionality of #traumatracker() is to keep track of relevant events occurring during the management of a trauma, for two basic purposes. The first one is about tracking, i.e. to have an accurate documentation of the trauma, to automate the creation (and management) of reports and to enable offlne data analysis. The second one is a first kind of assistance, in terms of the real-time generation of warnings and suggestions to be perceived through the smartglasses, by analysing and reasoning upon the tracked events and data. The system has been designed and developed using cognitive agent technologies based on the Belief-Desire-Intention (BDI) architecture, as supported by the JaCaMo agent platform.
143 +The key functionality of #traumatracker() is to keep track of relevant events occurring during the management of a trauma, for two basic purposes. The first one is about tracking, i.e. to have an accurate documentation of the trauma, to automate the creation (and management) of reports and to enable offlne data analysis. The second one is a first kind of assistance, in terms of the real-time generation of warnings and suggestions to be perceived through the smartglasses, by analysing and reasoning upon the tracked events and data. The system has been designed and developed using cognitive agent technologies based on the Belief-Desire-Intention (BDI) architecture, as supported by the JaCaMo agent platform.
144 144  
145 145  *Space*: [#traumatracker() Home|TraumaTracker.WebHome]
146 -\\
146 +<br />
147 147  *Contact*: [Angelo Croatti>https://www.unibo.it/sitoweb/a.croatti/en], [Sara Montagna>https://www.unibo.it/sitoweb/sara.montagna/en], [Alessandro Ricci>https://www.unibo.it/sitoweb/a.ricci/en]
148 148  
149 149  
... ... @@ -161,7 +161,7 @@
161 161  This suits both roles of Internet agents, that is, as either network-aware entities or (network-unaware) local agents.
162 162  
163 163  *Space*: [#tucson() Home|TuCSoN.WebHome]
164 -\\
164 +<br />
165 165  *Contact*: [Stefano Mariani|StefanoMariani.WebHome]
166 166  
167 167  
... ... @@ -171,5 +171,5 @@
171 171  #tuprolog() is a Java-based light-weight Prolog for Internet applications and infrastructures. For this purpose, #tuprolog() is designed to feature some interesting qualities: it is ~~easily deployable~~, just requiring the presence of a Java VM and an invocation upon a single JAR file; its core is both ~~minimal~~, taking the form of a tiny Java object containing only the most essential properties of a Prolog engine, and ~~configurable~~, thanks to the loading and unloading of predicates, functors and operators embedded in libraries; the ~~integration between Prolog and Java~~ is as wide, deep, clean as possible; finally, ~~interoperability~~ is developed along the two main lines of Internet standard patterns and coordination models.
172 172  
173 173  *Space*: [#tuprolog() Home|Tuprolog.WebHome]
174 -\\
174 +<br />
175 175  *Contact*: [Enrico Denti|EnricoDenti.WebHome]