RTAS’19, the 25th in a series of annual conferences sponsored by the IEEE, will be held in Montreal, Canada, as part of the Cyber-Physical Systems Week (CPSWeek) in April, 2019. The scope of RTAS’19 consists of three tracks:
- Track 1: Applications, Operating Systems and Run-Time Software;
- Track 2: Applied Methodologies and Foundations; and
- Track 3: Hardware Architectures and Analysis Tools.
Expanded scope: RTAS is a top-tier conference with a focus on systems research related to embedded systems and time-sensitive systems (of any size). The broad scope of RTAS’19 ranges from traditional hard real-time systems to embedded systems without explicit timing requirements, including latency-sensitive systems with informal or soft real-time requirements.
As in previous years, RTAS’19 is going to feature a Brief Presentations session dedicated to tools and systems demos, work-in-progress (WiP) papers, and brief announcements of journal papers that have not yet previously been presented at a conference (i.e., work-already-published, WaP).
The submission deadline is anticipated to be in early March and will be announced shortly once the CPSWeek early-registration deadline has been determined. Stay tuned for further details.
As in previous years, authors of accepted papers will be invited to participate in an artifact evaluation (AE) process. The goal of the AE process is to improve the reproducibility of results and reusability of the systems, tools, and other research artifacts underlying the papers published at RTAS. Besides being good scientific practice, a well-documented, easy to reuse artifact also stands to greatly improve a paper’s longterm impact.
While participation in the AE process is voluntary, we strongly encourage all authors of accepted papers to make their work as reproducible and reusable as possible, and to prepare an artifact submission to this end. The artifact submission deadline is January 11, 2019.
Further details, including detailed evaluation criteria, may be found on the Artifact Evaluation page.
Acceptance/rejection notifications will be sent tomorrow (December 21, 2018).
The paper submission deadline has passed and RTAS’19 has received a substantial increase in submissions — a big ‘thank you’ to all authors!
All papers are now under review. In the meantime, we’ll soon have updates on the Work-in-Progress / Brief Presentations track — stay tuned.
The submission deadline is today (end of the day, anywhere on Earth).
Once a paper has been registered, authors can still make improvements and upload new versions as many times as needed (right up until the deadline), so please don’t wait until the last minute to fill out the submission form.
When submitting your paper, make sure to select a track and take note of the track requirements.
Good luck with those final edits! We are looking forward to receiving your submissions.
When in doubt about how to properly anonymize your paper, please get in touch with the PC and Track Chairs.
The RTAS’19 call for papers has been posted — come check it out here!
There are three notable changes with regard to last year’s edition:
- Broadened scope: Submissions to Track 1 — the systems track — are no longer required to necessarily address timing issues. Of course, papers addressing timing issues are very welcome, but so are papers addressing other systems issues in embedded systems (broadly construed). Check out the detailed track description for details and contact the program chair in case of questions or doubts.
- Any kind of timing: the Call for Papers has been revised to make it more clear that RTAS welcomes work not just on classical hard real-time systems (which of course remain of interest), but also time-sensitive applications in a broader sense, including applications subject to probabilistic, soft real-time, quality-of-service (QoS), or latency requirements (e.g., as they often arise in cloud/edge/fog computing systems and IoT applications).
- And last but not least, RTAS’19 is moving to a double-blind peer reviewing process where the identities and affiliations of authors will not be disclosed to reviewers. Implementation details and a guide on how to properly anonymize submissions will be made available shortly.