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.
HW/SW Design Space Exploration on the Production Cell Setup
This paper describes and compares five CSP based and two CSP related
process-oriented motion control system implementations that are made
for our Production Cell demonstration setup. Five implementations are
software-based and two are FPGA hardware-based. All implementations
were originally made with different purposes and investigating
different areas of the design space for embedded control software
resulting in an interesting comparison between approaches, tools and
software and hardware implementations. Common for all implementations
is the usage of a model-driven design method, a communicating process
structure, the combination of discrete event and continuous time and
that real-time behaviour is essential. This paper shows that many
small decisions made during the design of all these embedded control
software implementations influence our route through the design space
for the same setup, resulting in seven different solutions with
different key properties. None of the implementations is perfect, but
they give us valuable information for future improvements of our
design methods and tools.