Difference between revisions of "D23 Improvements to Existing Provers"
From Event-B
Jump to navigationJump to searchimported>Nicolas m (→Overview) |
imported>Nicolas m |
||
| Line 7: | Line 7: | ||
* evolving prover API to fit with the needs of prover plug-in developers | * evolving prover API to fit with the needs of prover plug-in developers | ||
| + | Part of implemented rules and user interface features come from user feedback, mainly through SourceForge feature requests. SourceForge bugs are also an important source of input for corrections. | ||
Systerel is in charge of prover improvements. | Systerel is in charge of prover improvements. | ||
| Line 13: | Line 14: | ||
Areas of improvement for provers can be summarized as follows: | Areas of improvement for provers can be summarized as follows: | ||
* reducing proving time and effort | * reducing proving time and effort | ||
| − | * | + | : New Proof Rules |
| − | + | * reflecting prover implementation corrections | |
| − | * | + | : Reasoner Versioning |
| − | * | + | * reducing proof storage space |
| + | : Proof Purging | ||
| + | : Proof Simplifying | ||
| + | : Non textual Database Storage | ||
| + | * facilitating manual proof review or reuse | ||
| + | : Proof Skeleton View | ||
| + | : Copy paste from skeleton to edited proof | ||
| + | * Prover API evolution | ||
| + | : New Tactic Provider API | ||
| − | |||
= Choices / Decisions = | = Choices / Decisions = | ||
| − | Proof storage in database ? | + | Proof storage in database ? {{TODO}} |
A more generical way to contribute tactics (New tactic provider API) | A more generical way to contribute tactics (New tactic provider API) | ||
| Line 40: | Line 48: | ||
* Versioned Reasoners | * Versioned Reasoners | ||
: See [http://wiki.event-b.org/index.php/Versioned_Reasoners http://wiki.event-b.org/index.php/Versioned_Reasoners] | : See [http://wiki.event-b.org/index.php/Versioned_Reasoners http://wiki.event-b.org/index.php/Versioned_Reasoners] | ||
| + | |||
= Planning = | = Planning = | ||
| − | Proof storage in database ? | + | Proof storage in database ? {{TODO}} |
[[Category:D23 Deliverable]] | [[Category:D23 Deliverable]] | ||
Revision as of 10:57, 17 November 2009
Overview
All along the lifecycle of the provers, the following improvements can be achieved :
- adding new useful proof rules (to prove sequents that are hard to prove or even not provable at all)
- correcting bugs in implementations of existing proof rules
- implementing new tools to help the user do proofs
- evolving prover API to fit with the needs of prover plug-in developers
Part of implemented rules and user interface features come from user feedback, mainly through SourceForge feature requests. SourceForge bugs are also an important source of input for corrections. Systerel is in charge of prover improvements.
Motivations
Areas of improvement for provers can be summarized as follows:
- reducing proving time and effort
- New Proof Rules
- reflecting prover implementation corrections
- Reasoner Versioning
- reducing proof storage space
- Proof Purging
- Proof Simplifying
- Non textual Database Storage
- facilitating manual proof review or reuse
- Proof Skeleton View
- Copy paste from skeleton to edited proof
- Prover API evolution
- New Tactic Provider API
Choices / Decisions
Proof storage in database ? TODO A more generical way to contribute tactics (New tactic provider API)
Available Documentation
The following pages give useful information about prover improvements:
- Prover Rules
- See http://wiki.event-b.org/index.php/Inference_Rules
- See http://wiki.event-b.org/index.php/All_Rewrite_Rules
- Proof Skeleton View
- Proof Purger
- Prover API evolution
- Versioned Reasoners
Planning
Proof storage in database ? TODO
