From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id BF1B480211 for ; Fri, 27 Oct 2017 21:36:46 +0200 (CEST) Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=geoff@cs.miami.edu; spf=Pass smtp.mailfrom=geoff@cs.miami.edu; spf=None smtp.helo=postmaster@mail-ua0-f226.google.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of geoff@cs.miami.edu) identity=pra; client-ip=209.85.217.226; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="geoff@cs.miami.edu"; x-sender="geoff@cs.miami.edu"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of geoff@cs.miami.edu designates 209.85.217.226 as permitted sender) identity=mailfrom; client-ip=209.85.217.226; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="geoff@cs.miami.edu"; x-sender="geoff@cs.miami.edu"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ua0-f226.google.com) identity=helo; client-ip=209.85.217.226; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="geoff@cs.miami.edu"; x-sender="postmaster@mail-ua0-f226.google.com"; x-conformance=sidf_compatible IronPort-PHdr: =?us-ascii?q?9a23=3AT4zHvxfyPWA42KD7wgBNH/HklGMj4u6mDksu8pMi?= =?us-ascii?q?zoh2WeGdxc2+Zh7h7PlgxGXEQZ/co6odzbGJ4+a9ASQp2tWojjMrSNR0TRgLiM?= =?us-ascii?q?EbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpW1aJhKqYQF8?= =?us-ascii?q?I+CwHo/Jk+y20fqz8tvdeVMbqiC6ZOZ9IRK4oy3arY8TgIJnK+A8xgaa8TNzZ+?= =?us-ascii?q?1KyDYwdhqolBHm65Lo8Q=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CVAQDvifNZhuLZVdFSCoRzgRWPDY4gm?= =?us-ascii?q?W4DXAEJI4Feg1GENkIVAQEBAQEBAQEBAQESAQEBCAsLCCgvgjgigmcjAQEmBQ0?= =?us-ascii?q?7NB0IAQUBIoo2EJxdQIshgxKDCAEBBYR/B4JyAQseCAkBCIMcRYFCgzmEZoMeB?= =?us-ascii?q?AGDaoIygWKgJodmjQmCIl6FIoNONYcVjF9yiCsUJIEVNYIKfINACYJfBIIPWwG?= =?us-ascii?q?JIAEmgh0BAQE?= X-IPAS-Result: =?us-ascii?q?A0CVAQDvifNZhuLZVdFSCoRzgRWPDY4gmW4DXAEJI4Feg1G?= =?us-ascii?q?ENkIVAQEBAQEBAQEBAQESAQEBCAsLCCgvgjgigmcjAQEmBQ07NB0IAQUBIoo2E?= =?us-ascii?q?JxdQIshgxKDCAEBBYR/B4JyAQseCAkBCIMcRYFCgzmEZoMeBAGDaoIygWKgJod?= =?us-ascii?q?mjQmCIl6FIoNONYcVjF9yiCsUJIEVNYIKfINACYJfBIIPWwGJIAEmgh0BAQE?= X-IronPort-AV: E=Sophos;i="5.44,305,1505772000"; d="scan'208";a="242643406" Received: from mail-ua0-f226.google.com ([209.85.217.226]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 27 Oct 2017 21:36:45 +0200 Received: by mail-ua0-f226.google.com with SMTP id 47so5623356uas.8 for ; Fri, 27 Oct 2017 12:36:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs-miami-edu.20150623.gappssmtp.com; s=20150623; h=subject:to:message-id:date:from; bh=/zF6XRH9UXfK7IkmYPiAoTbtLQB4SvqDjqEYbK+2stI=; b=cvwydD46FoOaSQrG+jMplstrj2iCeDvnBryfDsOi4caiA3TnZ9b1vNbVSs1D4zGrSP H8RN1ombFxSg5Fh0ECsrjrgNKscMQxmiHK3QKK/2QFXVztaIUCi0LfXNeTb3JbiGNRLx 2jCkkTHHA5J/MOHboUUN/N58dlZ7y6HyozUmtTYTjcw7a8q0RJ8HQiJitHcqXyQFRT3M 7t209QI8TcQ4IghEPM1zTN5RS9TPewWvVMn/qCKMxfkRDuMZZPkEy4rJ5/ZUwwHx8mjM g/8PeND7yxS3RSn30qbmikrJ7NEnmfeUPo0KsWugSAP0Qsd47fbAhHD8ihHa4b6Zs7n5 Lbug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:message-id:date:from; bh=/zF6XRH9UXfK7IkmYPiAoTbtLQB4SvqDjqEYbK+2stI=; b=eZzaqIh0FocyZ2o223YUwOOjiLI0clSOQkHQwShMFDKmqQ3i/rVCrTELFtTzcJXfGC l/pYJRdh7M2jafMEKx+V5kkA422xTyflcQnkEoyn456Oci7XmLSIE3QgbvhV69UWcctk 27Kfh09ugYC3bZR/+e4L828LhcWZl+B7NovR6xxMQ+dxktCoO3/wm1ETYH/qjVIF/PYl i/V+9ibaGjFE+pxGyTpoWeL9K8art0dP9ewc1OWe7e6enSoC7LBnbm+2sB4PfhnDz1PS /7pHJ0EeZmqLztyunC4CudgPkog4y50urwBRCtPSeMAD+Ksl4vUxRS0tIPFFKFvONk0N OelA== X-Gm-Message-State: AMCzsaU+zQ4BWoCg1mNAC1AiGTXG5Tvk2aN8bh1fH5sJUFHk1OIjBrqE Md6oAx4L6ixpcEtbB4l/JvaX1bkgqDoyTi/NNvNCoty/0xMVKA== X-Google-Smtp-Source: ABhQp+TPgdu9TLkSDndAbe90/DxGDFwxmX0YEddvejZY+07Itc37jUSfDHsFGrm69ZakY5Red1/yTp1suDXj X-Received: by 10.176.30.136 with SMTP id o8mr1477140uak.170.1509133004606; Fri, 27 Oct 2017 12:36:44 -0700 (PDT) Received: from cs.miami.edu (ewell.cs.miami.edu. [192.31.89.12]) by smtp-relay.gmail.com with ESMTP id g23sm161138vke.13.2017.10.27.12.36.43 for ; Fri, 27 Oct 2017 12:36:44 -0700 (PDT) X-Relaying-Domain: cs.miami.edu Received: by cs.miami.edu (Postfix, from userid 3640) id 57E121700E35; Fri, 27 Oct 2017 15:36:36 -0400 (EDT) To: X-Mailer: mail (GNU Mailutils 2.99.98) Message-Id: <20171027193636.57E121700E35@cs.miami.edu> Date: Fri, 27 Oct 2017 15:36:36 -0400 (EDT) From: geoff@cs.miami.edu X-Validation-by: geoff@cs.miami.edu Subject: [Caml-list] CAV 2018 - Call for Papers Call for papers CAV 2018: The 30th International Conference on Computer Aided Verification July 14-17 2018, Oxford, UK, Part of the Federated Logic Conference, FLoC 2018 http://cavconference.org/2018/ http://floc2018.org Important dates: Paper submission deadline: January 31, 2018 (firm) Rebuttal period: March 15-17, 2018 Author notification: March 31st, 2018 CAV 2018 is the 30th in a series dedicated to the advancement of the theory and practice of computer-aided formal analysis methods for hardware and software systems. The conference covers the spectrum from theoretical results to concrete applications, with an emphasis on practical verification tools and the algorithms and techniques that are needed for their implementation. CAV considers it vital to continue spurring advances in hardware and software verification while expanding to new domains such as machine learning, autonomous systems, and computer security. The proceedings of the conference will be published in the Springer-Verlag Lecture Notes in Computer Science series. A selection of papers is expected to be invited to a special issue of Formal Methods in System Design and the Journal of the ACM. CAV'18 will take place in Oxford, UK, and is a part of the Federated Logic Conference (FLoC) 2018. Topics of interest include but are not limited to: + Algorithms and tools for verifying models and implementations + Algorithms and tools for system synthesis + Algorithms and tools that combine verification and learning + Mathematical and logical foundations of verification and synthesis + Specifications and correctness criteria for programs and systems + Deductive verification using proof assistants + Hardware verification techniques + Program analysis and software verification + Software synthesis + Hybrid systems and embedded systems verification + Formal methods for cyber-physical systems + Compositional and abstraction-based techniques for verification + Probabilistic and statistical approaches to verification + Verification methods for parallel and concurrent systems + Testing and run-time analysis based on verification technology + Decision procedures and solvers for verification and synthesis + Applications and case studies in verification and synthesis + Verification in industrial practice + New application areas for algorithmic verification and synthesis + Formal models and methods for security + Formal models and methods for biological systems Submissions on a wide range of topics are sought, particularly ones that identify new research directions. CAV 2018 is not limited to topics discussed in previous instances of the conference. Authors concerned about the appropriateness of a topic may communicate with the conference chairs prior to submission. Program committee See http://cavconference.org/2018/organization/ CAV Award The CAV award is given annually at the CAV conference for fundamental contributions to the field of Computer-Aided Verification. For details please check http://cavconference.org/cav-award CAV Award Committee Kim Larsen (chair) Natarajan Shankar Piere Wolper Somesh Jha Paper Submission - Full papers should be uploaded by the submission deadline. - Tool papers require the submission of an artifact together with the paper submission. As in 2017, CAV will follow a lightweight double-blind review process. Simultaneous submission to other conferences with proceedings or submission of material that has already been published elsewhere is not allowed. The review process will include a feedback/rebuttal period where authors will have the option to respond to reviewer comments. The PC chairs may solicit further reviews after the rebuttal period. Submissions will be in two categories: Regular Papers and Tool Papers. Regular Papers Regular Papers should not exceed 16 pages in LNCS format, not counting references and appendices. Authors can include a clearly marked appendix at the end of their submissions that is exempt from the page limit restrictions. However, the reviewers are not obliged to read the contents of these appendices. These papers should contain original research and sufficient detail to assess the merits and relevance of the contribution. Papers will be evaluated on basis of a combination of correctness, technical depth, significance, novelty, clarity, and elegance. We welcome papers on theory, case studies, and comparisons with existing experimental research, as well as combinations of new theory with experimental evaluation. A strong theoretical paper is not required to have an experimental component. On the other hand, strong papers reproducing and comparing existing results experimentally do not require new theoretical insights. Authors of accepted regular papers will be invited (but are not required) to submit the relevant artifact for evaluation by the artifact evaluation committee. Tool Papers: Tool Papers should not exceed 6 pages, not counting references. These papers should describe system and implementation aspects of a tool with a large (potential) user base (experiments not required, rehash of theory strongly discouraged). Papers describing tools that have already been presented (in any conference) will be accepted only if significant and clear enhancements to the tool are reported and implemented. Note that tool papers require the submission of an artifact for evaluation by the submission deadline. Artifacts will be evaluated concurrently with the review process and the program committee will have access to the artifact evaluation while making their decision. In special cases, where an artifact cannot be submitted, the authors should contact the program chairs to find alternate modes of artifact evaluation.