Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

check conformance between claims (in first line, in CPF) #13

Closed
jwaldmann opened this issue Jul 24, 2017 · 2 comments
Closed

check conformance between claims (in first line, in CPF) #13

jwaldmann opened this issue Jul 24, 2017 · 2 comments

Comments

@jwaldmann
Copy link
Owner

jwaldmann commented Jul 24, 2017

So far, the competition specification prescribes that output starts with the plain result, as in

YES
<?xml version="1.0" ...

Do we still want this?

  • pro: the answer is clearly visibible (for a human, for a simple-minded program) (otherwise, need to parse a huge XML structure)
  • con: this is just another source of ambiguity (what if the first line reads "YES" but the actual proof contains "NO") that needs to be checked - by whom? By another un-verified program?

Ideally, conformance of the claims (in the first line, in the CPF) should be checked by CeTA, which then actually needs three arguments:

  1. benchmark (TRS),
  2. claim,
  3. proof (CPF)

Cf. https://github.com/jwaldmann/ceta-postproc/blob/master/src/Main.hs#L43

... case certify_proof a problemString {- claim -} proofString of ...

Note that the current post-processor ceta-2.30-1 does NOT check conformance of claims (and hence, this issue is marked as a bug)

@jwaldmann jwaldmann changed the title read the first (plain text) line, or not? check conformance between claims (in first line, in CPF) Jul 25, 2017
@jwaldmann
Copy link
Owner Author

three-argument ceta: see 7d4881e

@jwaldmann
Copy link
Owner Author

this seems to be fixed in principle now. Closing this issue, will open separate issues if any problem turns up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant