<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Open-Problem on CS Theorems</title><link>https://cs.lozic.me/kinds/open-problem/</link><description>Recent content in Open-Problem on CS Theorems</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 12 Mar 2027 12:00:00 +0100</lastBuildDate><atom:link href="https://cs.lozic.me/kinds/open-problem/index.xml" rel="self" type="application/rss+xml"/><item><title>P vs NP</title><link>https://cs.lozic.me/posts/t026-p-vs-np/</link><pubDate>Fri, 12 Mar 2027 12:00:00 +0100</pubDate><guid>https://cs.lozic.me/posts/t026-p-vs-np/</guid><description>&lt;h2 id="symptom"&gt;Symptom&lt;/h2&gt;
&lt;p&gt;You are handed a scheduling problem. Two hundred tasks, precedence constraints,
shared resources, and a deadline. Somebody wants an optimal schedule.&lt;/p&gt;
&lt;p&gt;Checking a proposed schedule takes seconds: walk the list, verify each
constraint, add up the makespan. Finding one is different. Your search runs for
a day and finds nothing. You try simulated annealing, then a genetic algorithm,
then branch and bound. Each gives good schedules and none gives the best one, and
you cannot tell whether the problem is hard or you are not clever enough.&lt;/p&gt;</description></item></channel></rss>