remove hypersuperposition #401
Conversation
|
Hmm, I just tested it over the 870 FOF 2020+2021 problems on top of casc mode getting 6 unique solutions problems (casc mode 776, casc+hs-on 746). Maybe we could just test it and incorporate in schedules next years? |
|
OK - it looks a little unloved so maybe it doesn't work for e.g. polymorphic problems, but happy to leave it for now. Thanks for testing! |
|
Reopened at the request of @quickbeam123. |
MichaelRawson
force-pushed
the
michael-remove-hyper-superposition
branch
from
60e1987
to
d31a0d8
Compare
MichaelRawson
force-pushed
the
michael-remove-hyper-superposition
branch
from
d31a0d8
to
20b7af5
Compare
|
Rebased onto master. Post-competition, do we have any evidence that hypersuperposition is useful? Paging @quickbeam123 @easychair. |
|
I think vampire can live without hypersuperposition. I don't think I ever tested it, so it's potentially dangerous. So unless @easychair remembers what it was and feels some regret, I think it should go. |
|
Hyperresolution can be removed. Unit-resulting resolution should stay
…On Wed, 12 Jul 2023 at 14:13, Martin Suda ***@***.***> wrote:
I think vampire can live without hypersuperposition. I don't think I ever
tested it, so it's potentially dangerous. So unless @easychair
<https://github.com/easychair> remembers what it was and feels some
regret, I think it should go.
—
Reply to this email directly, view it on GitHub
<#401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVY4BJRQFBIPBC6O3ZU2PTXP2PHFANCNFSM54SUHI7Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@easychair - this one's hyper-superposition - I think hyperresolution is already gone or never existed. Thanks for confirmation anyway, axing hypersuperposition. |
See #157.
Inferences::HyperSuperpositiondoes not appear in schedules and nobody seems to think it is used. Please object if you do want/need this.