CINXE.COM
<!DOCTYPE html> <html><head> <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css"> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="description" content="ITCS 2025 CFP"> <meta name="title" content="ITCS 2025 Call for Papers"> <link rel="stylesheet" href="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css"> <link rel="stylesheet" type="text/css" href="../style.css"> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script> <script src="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"></script> <script src="//code.jquery.com/jquery-1.10.2.js"></script> <script> $(function(){ $("#header").load("../header.html"); $("#footer").load("../footer.html"); }); </script> </head><body style=""><div id="logo-bar" class="col-md-11"> <img id="itcs-logo" src="https://itcsconf.github.io/images/itcs_logo.png"> <h3 id="itcs-title">ITCS - Innovations in Theoretical Computer Science</h3> </div> <div class="col-md-11"> <br> </div> <nav class="navbar navbar-inverse col-md-11"> <div class="container-fluid "> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#myNavbar"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="navbar-brand" href="https://itcsconf.github.io/index.html" style="font-size:16px">Home</a> <a class="navbar-brand" href="https://itcsconf.github.io/itcs25/itcs25-cfp.html" style="font-size:16px">ITCS 2025 CFP</a> </div> <div class="collapse navbar-collapse" id="myNavbar"> <ul class="nav navbar-nav"> <!-- <li><a href="https://itcsconf.github.io/itcs24/itcs24-cfp.html">ITCS 2024 CFP</a></li> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2024<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs24/itcs24-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs23/itcs23-accepted.html">Accepted Papers</a></li> <<li><a href="http://itcsconf.github.io/itcs22/schedule-itcs22.html">Program</a></li> <li><a href="http://itcsconf.github.io/itcs22/graduating-bits.html">Graduating bits</a></li> <li><a href="https://simons.berkeley.edu/forms/itcs-2022-registration">Registration</a></li> </ul> </li>--> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">Past Conferences<b class="caret"></b></a> <ul class="dropdown-menu"> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2024<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs24/itcs24-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs24/itcs24-accepted.html">Accepted Papers</a></li> <li><a href="http://itcs-conf.org/itcs24/itcs24-program.html">Program</a></li> <li><a href="https://itcsconf.github.io/itcs24/itcs23-conduct.html">Code of conduct</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2023<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs23/itcs23-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs23/itcs23-accepted.html">Accepted Papers</a></li> <li><a href="http://itcs-conf.org/itcs23/itcs23-program.html">Program</a></li> <li><a href="https://itcsconf.github.io/itcs23/itcs23-conduct.html">Code of conduct</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2022<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs22/itcs22-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs22/itcs22-accepted.html">Accepted Papers</a></li> <li><a href="http://itcs-conf.org/itcs22/schedule-itcs22.html">Program</a></li> <li><a href="https://itcsconf.github.io/itcs22/itcs22-conduct.html">Code of conduct</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2021<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs21/itcs21-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs21/itcs21-accepted.html">Accepted Papers</a></li> <li><a href="https://itcsconf.github.io/itcs21/program.html">Program</a></li> <li><a href="https://itcsconf.github.io/itcs21/itcs21-conduct.html">Code of conduct</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2020<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs20/itcs20-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs20/itcs20-accepted.html">Accepted Papers</a></li> <li><a href="https://itcsconf.github.io/itcs20/itcs20-conduct.html">Code of conduct</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2019<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs19/itcs19-cfp.html">Call for papers</a></li> <li><a href="https://itcsconf.github.io/itcs19/itcs19-accepted.html">Accepted Papers</a></li> <li><a href="http://cseweb.ucsd.edu/%7Eslovett/conferences/itcs2019">Local information</a></li> </ul> </li> <li class="dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2018<b class="caret"></b></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs18/itcs18-cfp.html">Call For Papers</a></li> <li><a href="https://itcsconf.github.io/itcs18/itcs18-accepted.html">Accepted Papers</a></li> <li><a href="https://projects.csail.mit.edu/itcs/">Local information</a></li> </ul> </li> <li class="dropdown dropdown-submenu"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">ITCS 2017<span class="caret"></span></a> <ul class="dropdown-menu"> <li><a href="https://itcsconf.github.io/itcs17/itcs17-info.html">Information</a></li> <li><a href="https://itcsconf.github.io/itcs17/itcs17-cfp.html">Call For Papers</a></li> <li><a href="https://itcsconf.github.io/itcs17/itcs17-accepted.html">Accepted Papers</a></li> <li><a href="https://itcsconf.github.io/itcs17/itcs17-program.html">Program</a></li> <li><a href="https://itcsconf.github.io/itcs17/itcs17-graduating-bits.html">Graduating Bits</a></li> </ul> </li> <li><a href="https://itcsconf.github.io/itcs10to16/itcs10to16.html">ITCS 2010-2017</a></li> </ul> </li> <li><a href="https://itcsconf.github.io/governance.html">Governance</a></li> </ul> </div> </div> </nav> <script type="text/javascript"> (function($){ $(document).ready(function(){ $('ul.dropdown-menu [data-toggle=dropdown]').on('click', function(event) { event.preventDefault(); event.stopPropagation(); $(this).parent().siblings().removeClass('open'); $(this).parent().toggleClass('open'); }); }); })(jQuery); </script> </div> <div id="pg-wrapper"> <div class="container-fluid" id="all-but-header"> <div class="row"> <div class="col-md-11"> <br> The <b>16th Innovations in Theoretical Computer Science (ITCS)</b> conference will take place at Columbia University. It will be held <b>in person</b> from January 7 - January 10 2025. <br><br> ITCS seeks to promote research with innovative or bold agendas, which could be conceptual, technical, or methodological, and whose message will advance and inspire the greater theory community. The program committee welcomes papers introducing a new concept, model or understanding; opening a new line of inquiry within traditional or interdisciplinary areas; introducing new mathematical techniques and methodologies, or new applications of known techniques; putting forth a bold, even if preliminary, vision or line of attack; or unearthing novel or surprising connections between different topics. </p><hr> <!-- <h3>Registration</h3><p> Participants should register using the following <a class="c1" style="color:blue;font-weight:bold" href="https://www.eventbrite.com/e/itcs-2023-tickets-468543495207?utm-campaign=social&utm-content=attendeeshare&utm-medium=discovery&utm-term=listing&utm-source=cp&aff=escb">[registration link]</a>. </p> <h3>Hotel Reservations</h3> <p>Click <a class="c1" style="color:blue;font-weight:bold" href="https://www.marriott.com/events/start.mi?id=1668723624644&key=GRP">here</a> to book a room at Le Méridien Boston Cambridge at the group rate of 149 USD per night. Last Day to Book: Monday, December 19, 2022.</p> <h3>Program</h3><p>The program is available <a class="c1" style="color:blue;font-weight:bold" href="http://itcs-conf.org/itcs23/itcs23-program.html">here</a>.</p> --> <!-- <h3><a href="itcs24/itcs24-program.html">Conference Program (with links to Videos and Proceedings)</a></h3> <ul> <li><h4><a href="itcs24/itcs24-accepted.html">List of accepted papers</a></h4></li> </ul> <p></p>The conference program will be posted by January 6th. The program will run 4 full days, with 4 single-track sessions per day. Graduating bits will be during lunch hour (with pizza provided) on Thursday, Feb 1. There will be a reception (with brief remarks by the PC chair) the evening of January 30.</p> <hr> <h3><a href="https://drops.dagstuhl.de/entities/volume/LIPIcs-volume-287">Conference Proceedings</a></h3><hr> <h3><a href="https://www.eventbrite.com/e/itcs-2024-tickets-760602722217?aff=oddtdtcreator">Conference registration page</a></h3> <hr> <h3>Hotel information:</h3> There is no negotiated hotel room block for the conference; the <a href="https://simons.berkeley.edu/workshops/15th-innovations-theoretical-computer-science-itcs-conference">local event page</a> has a link to a list of recommended accomodation options.<hr> --> <h3>Important dates</h3><hr> <table> <tbody> <tr> <td> <p><b>Abstract submission deadline:</b></p> <p><b>Submission deadline:</b></p> <p>Notification to authors:</p> <p>Conference dates:</p> </td> <td> </td> <td> <p>September 3, 2024 (04:59pm PDT)</p> <p>September 5, 2024 (04:59pm PDT)</p> <p>November 2, 2024</p> <p>January 7-January 10, 2025</p> </td> </tr> </tbody> </table> <br>You can find registation and local organization (hotel, location, etc.) <a href="https://theory.cs.columbia.edu/itcs-2025.html">here</a>. <br> <strong>The program is <a href="itcs25/itcs25-program.html">here</a></strong>.<br> The list of accepted papers can be accessed <a href="itcs25/itcs25-accepted.html">here</a>.<br> <h3>Program committee</h3><hr> <p> </p><table> <tbody> <tr> <td style="padding:0 20px 0 20px;"> Ittai Abraham, Intel<br> Sepehr Assadi, University of Waterloo<br> Andris Ambainis, University of Latvia<br> Prabhanjan Ananth, University of California, Santa Barbara<br> Srinivasan Arunachalam, IBM Research<br> Hadley Black, University of California, San Diego<br> Adam Bouland, Stanford University<br> Eshan Chattopadhyay, Cornell University<br> Lijie Chen, University of California, Berkeley<br> Rishabh Goyal, University of Wisconsin-Madison<br> Prahladh Harsha, Tata Institute of Fundamental Research<br> Aayush Jain, Carnegie Mellon University<br> Rahul Jain, National University of Singapore<br> Michael Kapralov, École polytechnique fédérale de Lausanne<br> Robert Kleinberg, Cornell University<br> Vasilis Kontonis, University of Texas at Austin<br> Pravesh Kothari, Princeton University<br> Ravi Kumar, Google Research<br> Jason Li, Carnegie Mellon University<br> </td> <td style="padding:0 20px 0 20px;"> </td> <td style="padding:0 20px 0 20px;"> Daniel Lokshtanov, University of California, Santa Barbara<br> Pasin Manurangasi, Google Research<br> <b>Raghu Meka, UCLA (Chair)</b><br> Dor Minzer, Massachussetts Institute of Technology<br> Chinmay Nikhre, University of Washington, Seattle<br> Shayan Oveis Gharan, University of Washington, Seattle<br> Prasad Raghavendra, University of California, Berkeley<br> Guy Rothblum, Apple<br> Shubhangi Saraf, University of Toronto<br> Sushant Sachdeva, University of Toronto<br> Tselil Schramm, Stanford University<br> Sahil Singla, Georgia Institute of Technology<br> Srikanth Srinivasan, University of Copenhagen<br> Avishay Tal, University of California, Berkeley<br> Roei Tell, University of Toronto<br> Christos Tzamos, University of Athens<br> David Wajc, Technion<br> Ryan Williams, Massachussetts Institute of Technology<br> Jiapeng Zhang, University of Southern California<br> </td> </tr> </tbody> </table> <p></p> <!-- <p> </p><h3>Submission Instructions</h3><hr> <p> Authors should register and submit their paper via <a href="https://itcs2024.hotcrp.com">the hotcrp submission site</a>, by the above <b>strict</b> deadlines. The font size should be at least 11 point and the paper should be single column. Beyond these, there are no formatting requirements. Authors are required to submit a COI declaration upon submission. </p><p> The conference will employ a lightweight double-blind reviewing process. <b>Submissions should not reveal the identity of the authors in any way.</b> In particular, authors’ names, affiliations, and email addresses should not appear at the beginning or in the body of the submission. (Author and institution information will be uploaded separately on the submission site.) The purpose of this double-blind process is to help PC members and external reviewers come to a judgment about the paper without unconscious bias, and is not intended to make it impossible for them to discover who the authors are. Nothing should be done in the name of anonymity that weakens the submission or makes the job of reviewing the paper more difficult. In particular, important references should not be omitted or anonymized. In addition, authors should feel free to disseminate their ideas or draft versions of their paper as they normally would. For example, authors may (and are in fact encouraged to) post their papers to arXiv/ECCC/IACR etc. </p><p> Authors should strive to make their paper accessible not only to experts in their subarea, but also to the theory community at large. The submission should include clear proofs of all central claims. In addition, it is strongly recommended that the paper contain, within the first 10 pages, a concise and clear presentation of the merits of the paper, including a discussion of its significance, innovations, and place within (or outside) of our field's scope and literature. The committee will put a premium on writing that conveys clearly, in as simple and straightforward a manner as possible, what the paper accomplishes. </p> <p>Submissions authored by program committee members (with the exception of the PC chair) are allowed. Utmost care will be taken to avoid COIs with PC submissions, ensuring that such submissions receive no unfair advantage, and that the reviews and the discussion remain confidential from the authors. </p><p> All submissions will be treated as confidential, and will only be disclosed to the committee and their chosen sub-referees. In addition, the program committee may consult with journal editors and program chairs of other conferences about controversial issues such as parallel submissions. </p> <p></p> <h3>Prior, simultaneous, and subsequent submissions</h3><hr> <p> Results published/presented/submitted at another archival conference will not be considered for ITCS. Simultaneous submission to ITCS and to a journal is allowed. Papers accepted to ITCS should not be submitted to any other archival conferences. </p> --> <h3>Online posting</h3> <p> Authors are encouraged to post full versions of their submissions in a freely accessible online repository such as the arxiv, the ECCC, or the Cryptology ePrint archive. It is generally expected that authors of accepted papers will make full versions of their papers, with proofs, available before the conference begins. </p> <hr> <h3>Conference presentation</h3> <p> All the talks are expected to be in person. The talks in the conference will not be recorded, and instead the authors of each paper will be asked to upload a 20-25 minute talk, which will be posted online. </p> <!-- <p> The list of accepted papers is available <a href="https://itcsconf.github.io/itcs18/itcs18-accepted.html">here</a>. </p> --> <hr> <h3>Graduating bits</h3> <p> Participants near to graduation (on either side) will be given an opportunity to present (in 2-3 minutes) their results, research, plans, personality, and so on during the "Graduating bits" session. This is one of the important traditions of ITCS, and not to be missed! Details on how to participate will be provided closer to the conference date. <!-- If you are interested in participating please add your name <a href="https://docs.google.com/spreadsheets/d/1Z3bp_Ch1vK4Lpf0RQDTI1hCQ7AQFFiOyugBuD-4q9QU/edit#gid=0">here</a>. If you would like to use a few slides please dowlowd them <a href="https://www.dropbox.com/request/zZVCKBep3yvKmssZmX60">here</a>. Each presentation should be only 2-3 minutes long. --> </p> <hr> <h3>Awards</h3> <p> The committee may award a "best student paper" award. </p> <!-- <h3>Poster session</h3><hr> <p> We will have a fun evening with a poster session and a reception. We would love it if you participated. The poster should be of size 4' by 4' and it can be printed near the conference venue, for example <a href="https://local.fedex.com/en-us/ma/cambridge/office-0992">here</a>. </p> --> <hr> <h3>Code of Conduct</h3> <p> ITCS is committed to an inclusive conference experience, respectful of all participants, and free from any discrimination or harassment, including unwelcome advances or propositions of an intimate nature, particularly when coming from a more senior researcher to a less senior one. All ITCS attendees are expected to behave accordingly. If you experience or witness discrimination, harassment or other unethical behavior at the conference, we encourage you to seek advice by contacting SafeToC advocates (<a href="http://safetoc.org/index.php/toc-advisors/">http://safetoc.org/index.php/toc-advisors/</a>) </p> <hr> <h3>Proceedings</h3> <p> The accepted papers will be published by LIPIcs in the electronic proceedings of the conference. To accommodate the publishing traditions of different fields, authors of accepted papers can ask the PC chair to have only a one page abstract of the paper appear in the proceedings, along with a URL pointing to the PDF of the full paper on an online archive. </p> <hr> <h3>Sponsors</h3> <p> <img style="height:100px" src="/images/2023_sponsor_simons.jpg"></p> </div> </div> </div> </div> <!-- <div id="footer"><!-- Changing this will add a footer to all pages. </div>--> </body></html>