Communicating Process Architectures
Communicating Process Architectures 2014,
the 36th. WoTUG conference on concurrent and parallel systems, takes place from
Sunday August 24th to Wednesday August 27th 2014 and is hosted by the
Department of Computer Science, University of Oxford.
Accommodation and evening Fringe sessions will be at
St. Anne's College,
a few minutes walk from the Department.
WoTUG provides a forum for the discussion and promotion of concurrency ideas,
tools and products in computer science.
It organises specialist workshops and annual conferences that address
key concurrency issues at all levels of software and hardware granularity.
WoTUG aims to progress the leading state of the art in:
and to stimulate discussion and ideas on the roles concurrency will play in the future:
theory (programming models, process algebra, semantics, ...);
practice (multicore processors and run-times, clusters, clouds, libraries, languages, verification, model checking, ...);
education (at school, undergraduate and postgraduate levels, ...);
applications (complex systems, modelling, supercomputing, embedded systems, robotics, games, e-commerce, ...);
Of course, neither of the above sets of bullets are exclusive.
for the next generation of scalable computer infrastructure (hard and soft) and application,
where scaling means the ability to ramp up functionality (stay in control as complexity increases)
as well as physical metrics (such as absolute performance and response times);
for system integrity (dependability, security, safety, liveness, ...);
for making things simple.
A database of papers and presentations from WoTUG conferences is here.
The Abstract below has been randomly selected from this database.
Protocol Verification in Millipede
In this paper we present the MOPED module of the Millipede debugging system. Millipede is a multi-level debugging sytem for parallel message passing programs. MOPED allows the user to specify a protocol to which the communication of the program should adhere, and authomatically have all the messages sent in the system checked against the protocol. The specification language is small and easy to use, yet powerful enough to specify a wide range of protocols. Program variables can be passed easily to the verification module, allowing the construction of mode dynamic protocol specifications. Protocols can be specified incrementally, starting out very general working towards a more complex specification. Finally, the verification module can be run either online, that is, while the application is executing, or offline, using log files generated when the application was executed.