conferences.computer.science

All conferences / RV / 2024

RV 2024

24th International Conference on Runtime Verification

Held15–18 Oct 2024 Whereİstanbul 🇹🇷 RankCORE B Website bouncmpe.github.io/rv24/ ↗
Closed

Submission closed on 28 May 2024, after an extension of 14 days.

Submission timeline

  • 28 May 2024 Abstract registration AoE 14 May 2024 → 28 May 2024 +14 days
  • 28 May 2024 Full paper AoE 14 May 2024 → 28 May 2024 +14 days
  • 25 Jun 2024 Notification
  • 15 Oct 2024 Conference opens

What to submit

Format
regular (16 pages LNCS + references) / short / tool demonstration / benchmarks (8 pages)
Proceedings
Springer LNCS — Paywalled, for-profit

The Program Committee will give a Springer-sponsored Best Paper Award to an elected regular paper. The Program Committee will invite a selection of accepted papers to submit extended versions to a special journal issue, currently planned to be in the International Journal on Software Tools for Technology Transfer (STTT).

Call for papers

The call, as published

Reproduced verbatim from the organisers’ announcement, after a deadline extension. The conference’s own page is at bouncmpe.github.io/rv24/.

Last CfP and Deadline Extension: Runtime Verification
 (RV) 2024

Runtime Verification 2024

October 15-18

Istanbul, Türkiye

We are pleased to invite you to submit papers for the 24th International
Conference on Runtime Verification (RV'24), which will take place in Istanbul,
Türkiye, on October 15-18, 2024. The full Call for Papers, with submission
details, is at https://yeni.cmpe.bogazici.edu.tr/rv24/call-for-papers/


 Important Dates

  *   Paper submission:                   May 28, 2024 (extended)
  *   Notification:                              June 25, 2024
  *   Camera-ready:                         July 23, 2024
  *   Conference:                             October 15-18, 2024

Website

https://yeni.cmpe.bogazici.edu.tr/rv24/
<https://yeni.cmpe.bogazici.edu.tr/rv24/call-for-papers/>

Objectives and Scope

Runtime verification is concerned with the monitoring and analysis of the
runtime behavior of software, hardware, and cyber-physical systems.

The topics of the conference include, but are not limited to:

  *   specification languages for monitoring
  *   formal requirements elicitation, specification mining, and machine
learning over runtime traces
  *   monitor construction techniques
  *   program instrumentation
  *   combination of static and dynamic analysis
  *   dynamic type checking and assurance cases
  *   monitoring techniques for concurrent and distributed systems
  *   runtime checking of privacy and security policies
  *   metrics and statistical information gathering
  *   fault localization, containment, resilience, recovery and repair
  *   monitoring of systems with learning-enabled components, including
reinforcement learning
  *   runtime verification for autonomy and runtime assurance

New areas we are soliciting this year include:

  *   integrating the results of runtime monitoring with downstream tasks,
especially metareasoning, control, fault recovery, and design modifications
  *   case studies of using RV in industrial settings, with lessons learned
and challenges faced

Papers

Papers can be submitted in one of four categories:

  *   Regular papers (up to 16 pages +  references) should present original
unpublished results.
  *   Short papers (up to 8 pages + references) should present original
unpublished ideas but which are not necessarily thoroughly worked out.
  *   Tool papers (up to 8 pages + references) should present a new tool or
novel extensions to an existing tool supporting runtime verification.
  *   Benchmark papers (up to 8 pages + references) should describe a
benchmark or benchmark generator useful for evaluating RV tools
Tutorials


Tutorials are two-to-three-hour presentations on a selected topic. A tutorial
proposal is at most 2 pages, and must describe the subject and outline of the
tutorial, relevance to RV community, schedule in some detail, and brief
biographies of the presenters.

Tutorial proposers also have the option to submit a Regular Paper (up to 16
pages) on the subject of the tutorial.



The Program Committee<https://yeni.cmpe.bogazici.edu.tr/rv24/committees/> will
give a Springer-sponsored Best Paper Award to an elected regular paper.



Special Journal Issue The Program Committee will invite a selection of
accepted papers to submit extended versions to a special journal issue,
currently planned to be in the International Journal on Software Tools for
Technology Transfer
(STTT<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flink.springer.com%2Fjournal%2F10009&data=05%7C02%7Ca.lukina%40tudelft.nl%7Cbe3cf7f0edc7440a6fe508dc47489f2a%7C096e524d692940308cd38ab42de0887b%7C0%7C0%7C638463624450094368%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qSXddHrqbDD4ow%2FiOk2ChYV5dyIR3YEXqq9QWO8quf4%3D&reserved=0>).

Data entirely hand-typed, one call for papers at a time. There is no scraper behind any of this: I read the announcement and type the dates in, in the gaps between other work, and with the hope it is useful to others. Organisers then move deadlines without telling anyone, calls get edited in place, and now and then the typing is simply wrong. Treat this as a well-meaning notebook rather than an authority, and check the conference’s own page before you submit anything you care about.