EATCS-IPEC Nerode Prize - Call for Nominations
Deadline: 15 May, 2022
The EATCS-IPEC Nerode Prize for outstanding papers in the area of
multivariate algorithmics, is presented annually with the presentation
taking place at IPEC (International Symposium on Parameterized and Exact
Computation). IPEC 2022 is due to take place as part of ALGO 2022 on 5-9
September in Potsdam, Germany. The Prize is named in honor of Anil
Nerode in recognition of his major contributions to mathematical logic,
theory of automata, computability and complexity theory.
Award Committee
The winning paper(s) will be selected by the EATCS-IPEC Nerode Prize
Award Committee. This year's committee consists of the following people.
Anuj Dawar, chair (University of Cambridge, anuj.dawar(a)cl.cam.ac.uk)
Fedor Fomin (University of Bergen, fedor.fomin(a)uib.no)
Thore Husfeldt (IT University of Copenhagen, thore(a)itu.dk)
Deadline for Nominations: 15 May, 2022.
Decision: 1 July, 2022.
The Award Committee is solely responsible for the selection of the
winner of the award which may be shared by more than one paper or series
of papers. The Award Committee reserves the right to declare no winner
at all.
Eligibility
Any research paper or series of research papers by a single author or by
a team of authors published in a recognized refereed journal. The
research work nominated for the award should be in the area of
multivariate algorithms and complexity meant in a broad sense, and
encompasses, but is not restricted to those areas covered by IPEC. The
Award Committee has the ultimate authority to decide on the eligibility
of a nomination. Papers authored by a member of the Award Committee are
not eligible for nomination.
Note that the past restrictions that require a certain number of years
before/after the publication of the nominated papers have been removed.
Nominations
Nominations may be made by any member of the scientific community
including the members of the Award Committee. A nomination should
contain a brief summary of the technical content of each nominated paper
and a brief explanation of its significance. Nominations are done by an
email to the Award Committee Chair with copies to the members of the
committee. The Subject line of the nomination E-mail should contain the
group of words "Nerode Prize Nomination".
[ Apologies for cross posting ]
Runtime Verification 2022 CALL FOR PAPERS
[ https://rv22.gitlab.io/ | https://rv22.gitlab.io ]
We are pleased to invite you to submit papers for the 22nd International Conference on Runtime Verification (RV'22), which will take place as part of the Computational Logic Autumn Summit CLAS 2022 ( [ http://viam.science.tsu.ge/clas2022/ | http://viam.science.tsu.ge/clas2022/ ] ) in Tbilisi, Georgia, from September 28-30, 2022.
### Dates ###
Paper submission: Thursday, 5 May 2022
Notification: Wednesday, 22 June 2022
Camera-ready: Sunday, 24 July 2022
Conference: 28-30 September 2022
Deadlines expire at 23:59 anywhere on earth on the dates displayed above.
### Conference Objectives and Scope ###
Runtime verification is concerned with the monitoring and analysis of the runtime behaviour of software and hardware systems. Runtime verification techniques are crucial for system correctness, reliability, and robustness; they provide an additional level of rigor and effectiveness compared to conventional testing and are generally more practical than exhaustive formal verification. Runtime verification can be used prior to deployment, for testing, verification, and debugging purposes, and after deployment for ensuring reliability, safety, and security and for providing fault containment and recovery as well as online system repair.
The topics of the conference include, but are not limited to:
- specification languages for monitoring
- monitor construction techniques
- program instrumentation
- logging, recording, and replay
- combination of static and dynamic analysis
- specification mining and machine learning over runtime traces
- monitoring techniques for concurrent and distributed systems
- runtime checking of privacy and security policies
- metrics and statistical information gathering
- program/system execution visualization
- fault localization, containment, resilience, recovery and repair
- systems with learning-enabled components
- dynamic type checking and assurance cases
- runtime verification for autonomy and runtime assurance
Application areas of runtime verification include cyber-physical systems, autonomous systems, safety/mission critical systems, enterprise and systems software, cloud systems, reactive control systems, health management and diagnosis systems, and system security and privacy.
### Papers ###
There are four categories of papers which can be submitted: regular, short, tool demo, and benchmark papers. Papers in each category will be reviewed by at least three members of the Program Committee.
- Regular Papers (up to 16 pages, not including references) should present original unpublished results. We welcome theoretical papers, system papers, papers describing domain-specific variants of RV, and case studies on runtime verification.
- Short Papers (up to 8 pages, not including references) may present novel but not necessarily thoroughly worked out ideas, for example emerging runtime verification techniques and applications, or techniques and applications that establish relationships between runtime verification and other domains.
- Tool Demonstration Papers (up to 8 pages, not including references) should present a new tool, a new tool component, or novel extensions to existing tools supporting runtime verification. The paper must include information on tool availability, maturity, selected experimental results and it should provide a link to a website containing the theoretical background and user guide. Furthermore, we strongly encourage authors to make their tools and benchmarks available with their submission.
- Benchmark Papers (up to 8 pages, not including references) should describe a benchmark, suite of benchmarks, or benchmark generator useful for evaluating RV tools. Papers should include information as to what the benchmark consists of and its purpose (what is the domain), how to obtain and use the benchmark, an argument for the usefulness of the benchmark to the broader RV community and may include any existing results produced using the benchmark. We are interested in both benchmarks pertaining to real-world scenarios and those containing synthetic data designed to achieve interesting properties. Broader definitions of benchmark e.g. for generating specifications from data or diagnosing faults are within scope. We encourage benchmarks that are tool agnostic, especially if they have been used to evaluate multiple tools. We also welcome benchmarks that contain verdict labels and with rigorous arguments for correctness of these verdicts, and benchmarks that are demonstrably challenging with respect to the state-of-the-art tools. Benchmark papers must be accompanied by an easily accessible and usable benchmark submission. Papers will be evaluated by a separate benchmark evaluation panel who will assess the benchmarks relevance, clarity, and utility as communicated by the submitted paper.
The Program Committee of RV 2021 will give a Springer-sponsored Best Paper Award to one eligible regular paper.
### Submissions ###
All papers and tutorials will appear in the conference proceedings in an LNCS volume. Submitted papers and tutorials must use the LNCS/Springer style detailed here: [ http://www.springer.de/comp/lncs/authors.html | http://www.springer.de/comp/lncs/authors.html ] .
Springer encourages authors to include their ORCIDs ( [ https://www.springer.com/gp/authors-editors/orcid | https://www.springer.com/gp/authors-editors/orcid ] ) in their papers.
Papers must be original work and not be submitted for publication elsewhere. Papers must be written in English and submitted electronically (in PDF format) using the EasyChair submission page here: [ https://easychair.org/conferences/?conf=rv2022 | https://easychair.org/conferences/?conf=rv2022 ] .
The page limitations mentioned above include all text and figures, but exclude references. Additional details omitted due to space limitations may be included in a clearly marked appendix, that will be reviewed at the discretion of reviewers, but not included in the proceedings.
At least one author of each accepted paper and tutorial must register and attend RV'22 to present.