Paper Details

db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
@InProceedings{Groothuis05,
  title = "g{CSP} occam {C}ode {G}eneration for {RM}o{X}",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  author= "Groothuis, Marcel A. and Liet, Geert K. and Broenink, Jan F.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  editor= "Broenink, Jan F. and Roebbers, Herman and Sunter, Johan P. E. and Welch, Peter H. and Wood, David C.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  pages = "375--383",
  booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2005",
  isbn= "978-1-58603-561-7",
  year= "2005",
  month= "sep",
  abstract= "gCSP is a graphical tool for creating and editing CSP
     diagrams. gCSP is used in our labs to generate the embedded
     software framework for our control systems. As a further
     extension to our gCSP tool, an occam code generator has been
     constructed. Generating occam from CSP diagrams gives
     opportunities to use the Raw-Metal occam eXperiment (RMoX)
     as a minimal operating system on the embedded control PCs in
     our mechatronics laboratory. In addition, all processors
     supported by KRoC can be reached from our graphical CSP
     tool. The commstime benchmark is used to show the trajectory
     for gCSP code generation for the RMoX operating system. The
     result is a simple means for using RMoX in our laboratory
     for our control systems. We want to use RMoX for future
     research on distributed control and for performance
     comparisons between a minimal operating system and our
     CTC++/RT-linux systems."
}

If you have any comments on this database, including inaccuracies, requests to remove or add information, or suggestions for improvement, the WoTUG web team are happy to hear of them. We will do our best to resolve problems to everyone's satisfaction.

Copyright for the papers presented in this database normally resides with the authors; please contact them directly for more information. Addresses are normally presented in the full paper.