Thank you for your feedback. I needed a feekback. Your feedback is
clever, right to the point. THANKS!.
I wrote my points above, item by item. More than that, I posted a new
version of 2.5 in the page.
take care,
angela
-------------------------------------------------------------
-------------------------------------------------------------
Well, I believe that if there is a flaw, it will be found in Theorems
2.12
and 2.13. No gaps before that! See, no matter the way I make a
partition, the idea is:
PSI is satisfiable if and only if PSI' (partitioned version) is
satisfiable. Equivalently, PSI is unsatisfiable (not satisfiable) if
and only if PSI' is unsatisfiable.
If you accepted that PSI is in such a way that if $l$ is a literal of
$PSI,
then its negation, $NOT l$, is a literal of PSI as well, then, a
partition of PSI starts with a PARTITION (a set of pairwise disjoint
sets) of the clauses of PSI, $\{D_{l_{1}},...,D_{l_{k}\}$, $l$ ranging
a set of literals of PSI (I named it label, but think about a
partition of the set of clauses of PSI) $D_{l}$ a set of clauses of
PSI that contain $l$ (I do not mean that $D_{l}$ contains the set of
ALL clauses of PSI that contain $l$!). We have,
PSI= /\{C\in D_{l_{1}}} /\ ... /\ /\{C\in D_{l_{k}}}=
(l_{1}\/ S_{l_{1}}}) /\ ... /\ (l_{k}\/ S_{l_{k}}})
(/\ stands for AND, \/ stands for OR, = stands for equivalent)
Where /\{C\in D_{l_{i}}}= C_{1l_{1}}/\.../\C_{sl_{1}} is a
conjunction,
say, $s$ clauses, all of them containing $l_{i}$ among its literals,
so, factoring,
/\{C\in D_{l_{i}}}= C_{1l_{1}}/\.../\C_{sl_{1}} = l_{i}\/ S_{l_{i}}}
(I wrote it in a neater .pdf, 2.5 in More Words. It is posted in my
page).
-------------------------------------------------------------
-------------------------------------------------------------
>
> But let's assume for a moment that you are correct in 2.5, that my
> assessment is wrong, and you are able to rewrite 2.5 such that you can
> prove Ψ is satisfiable iff a partitioned version of it is satisfiable.
> The following red flags on the algorithm are, if not fatal flaws,
> worrying to anyone reading the paper for peer review:
>
> 1. Your algorithm requires search (and multiple iterative repeated
> procedures). Please watch the 2006 lecture of M. Sipser speaking at
> the Clay institute about the subject of search in an NP-complete
> problem and why we think search is not necessary if there is a
> solution to an NP-complete problem.
>
>
http://www.youtube.com/watch?v=msp2y_Y5MLE
>
-------------------------------------------------------------
-------------------------------------------------------------
Clever! Very nice, indeed!
The idea is that, if I am right I can tell you polysize if a formula
is satisfiable or unsatisfiable. But I cannot tell you which are the
valuations to make PSI true.
Sipser Lecture is just wonderful! I keep my focus on the
problem. Really, let us suppose that my manuscript is "The sorcerer
stone". Even so, jumping from the (theoretical) mathematician answer
to a applied scientist answer, I think it is a big jump (say 50 years
long?)
-------------------------------------------------------------
-------------------------------------------------------------
> 2. Your claim that your algorithm is simple, isn't true. While
> qualitative in nature, this red flag shows up around page 6 or 7, and
> is at that moment, your paper is an extra complicated piece to
> decipher. I had a much easier time reading Mike and Ike's Quantum
> computation book... ;-)
> -------------------------------------------------------------
-------------------------------------------------------------
Oh, boy! I will never use the magic words: "It is quite simple!" It
never is that simple and the magic never works, spite my will! My
apologies!
-------------------------------------------------------------
-------------------------------------------------------------
> 3. You do not provide pseudocode or a working language code version of
> your algorithm. It shouldn't be difficult to do this if your algorithm
> works, yet it is missing. This would let other's test your claim.
>
> 4. You do not provide any benchmark certificates. Here is a list of
> benchmark problems, so that when you do have a working algorithm, you
> can test it:
http://www.cs.ubc.ca/~hoos/SATLIB/benchm.html
>
> -------------
> -------------------------------------------------------------
-------------------------------------------------------------
It took me some time to decide writing the Algorithm. I felt not that
sure I will perform the task of writing a simple code. I can write
algorithms, but I never wrote a program, at least such a big
one. I was divided in between the decision of writing the algorithm or
just the manuscript. My doubts were raised by the possibility of,
maybe if I do not write clearly, people will associate my weak side (I
am not a
programmer) to the idea that the manuscript is weak or totally wrong,
which is not true.
The algorithms will be posted in my page. Anyone, accordingly to
her(his) wishes can "translate" it into a nice language, e.g, lisp or
shemme.
-------------------------------------------------------------
-------------------------------------------------------------
> I would be happy to provide you with a copy of my paper. I temporarily
> self-published a draft copy on scribd about a year ago, but I have
> since taken it off the internet because my new draft is going to be
> significantly more powerful and has corrected a few errors and
> clarified a few points. I expect to have this draft completed soon and
> I plan to submit it to arXiv.org. I will let you know as soon as it is
> available!
>
> Cheers,
>
-------------------------------------------------------------
-------------------------------------------------------------
Thanks!
-------------------------------------------------------------
-------------------------------------------------------------