Search results

From Event-B
Jump to navigationJump to search

Create the page "Proof" on this wiki! See also the search results found.

Page title matches

  • File:Proof Control Profiles.png
    (682 × 198 (29 KB)) - 20:49, 30 April 2020
  • Extending the Proof Manager
    ...le for constructing proofs and maintaining existing proofs associated with proof obligations. There are two ways for extending the Proof Manager:
    3 KB (400 words) - 10:27, 27 October 2011
  • Proof Dependencies and Reasoner Conflicts
    ..., proof status is determined from proof dependencies on the one hand and a proof skeleton on the other hand. The skeleton is entirely visited, searching for ...e proofs to allow for quick access. This improves performances in updating proof statuses, which is by far the most time-consuming build operation.
    1 KB (175 words) - 14:49, 6 June 2011
  • File:Proof Tree and Rule Details.png
    (271 × 275 (14 KB)) - 20:50, 30 April 2020
  • ADVANCE D3.2 Improvement of automated proof
    ...h could be customized and parameterized tactics to discharge some specific proof obligations. The user can furthermore share and backup these defined tactic ...time frame of ADVANCE, and increases the rate of automatically discharged proof obligations.
    4 KB (596 words) - 13:21, 18 July 2012
  • ADVANCE D3.3 Improvement of automated proof
    ...e the diversity of predicates and increase the automated proofs of trivial proof obligations often encountered in degenerated cases (that is not interesting The proportion of automatically discharged proof obligations heavily depends on the auto-tactic configuration. Sometimes, th
    7 KB (1,145 words) - 10:05, 8 October 2013
  • Current Proof Tree Node in UI
    ...e Environment) display some information which is associated to the current proof tree node, if any. However, in Rodin 2.3 these view do not always display t ...w does not refresh. One has to click on the current proof tree node in the Proof Tree view to force a refresh.
    4 KB (683 words) - 18:33, 16 December 2011
  • Proof Obligation Names (Rodin User Manual)
    Next is a table describing the names of context proof obligations: Next is a table showing the name of machine proof obligations:
    4 KB (575 words) - 15:09, 15 September 2011
  • User:Nicolas/Collections/ADVANCE D3.4 Improvement of automated proof
    ...ase). AWE, an external user of Rodin, reported a 31% increase in automatic proof by using the SMT plugin. See AWE presentation at the ADVANCE Industry Day For certain classes of proof obligations, i.e. those that heavily rely on enumerated or otherwise finite
    4 KB (639 words) - 16:46, 21 November 2014
  • Extending the Proof Obligation Generator(How to extend Rodin Tutorial)
    ...[Extending_the_Static_Checker(How_to_extend_Rodin_Tutorial)|Generating the proof obligations]]}} ...provided architecture for static checking is really similar to the one for proof obligation generation. Thus, it can be useful for the reader to understand
    13 KB (1,774 words) - 13:57, 5 September 2013
  • Extending the Proof Obligation Generator (How to extend Rodin Tutorial)
    ...provided architecture for static checking is really similar to the one for proof obligation generation. Thus, it can be useful for the reader to understand ...oof obligation, which is described in the paper. This PO overrides the FIN proof obligation. Thus we will see here, how to :
    13 KB (1,755 words) - 07:19, 7 September 2010

Page text matches

  • File:ProofStatus.png
    ...y diagram showing relationships between the classes/interfaces involved in proof status management.
    (884 × 675 (26 KB)) - 20:50, 30 April 2020
  • File:ProofTree.png
    ...y diagram showing relationships between the classes/interfaces involved in proof tree management.
    (858 × 660 (27 KB)) - 20:50, 30 April 2020
  • Proof Obligation Names (Rodin User Manual)
    Next is a table describing the names of context proof obligations: Next is a table showing the name of machine proof obligations:
    4 KB (575 words) - 15:09, 15 September 2011
  • Proof Hints
    1. '''Description''': A brief description of the proof hints with the situation where this can be helpful. ...to select these hypotheses automatically when generating the corresponding proof obligation.
    4 KB (545 words) - 22:17, 5 March 2010
  • File:ShowRuleDetailsView.png
    The command available after a right click on a proof tree node.
    (284 × 144 (16 KB)) - 20:50, 30 April 2020
  • File:Operation po.png
    Working with a proof obligation generated from an action using an operation call.
    (776 × 390 (30 KB)) - 20:50, 30 April 2020
  • Proof Contextual Information
    ...) to handle cases where their behaviour shall depend on the context of the proof obligation. Usually, as was the case until the Rule-Based Prover appeared, * rule-based prover needs to know whether the rules in a proof are still valid (reusable)
    4 KB (600 words) - 14:09, 15 December 2010
  • Category:Proof patterns
    [[Category:Proof]]
    1 member (0 subcategories, 0 files) - 12:53, 12 August 2009
  • Extending the Proof Manager
    ...le for constructing proofs and maintaining existing proofs associated with proof obligations. There are two ways for extending the Proof Manager:
    3 KB (400 words) - 10:27, 27 October 2011
  • File:PO Commands.png
    - Proof Replay on Undischarged POs
    (468 × 656 (31 KB)) - 20:49, 30 April 2020
  • Scenarios for Merging Proofs
    == Proof structure == With respect to the merging objective, a proof is made of:
    6 KB (1,046 words) - 10:34, 27 October 2011
  • Generic Instantiation
    ...xtending the instantiation to a chain of refinements. We define sufficient proof obligations to ensure that the proofs associated to a generic development r ...n the instantiation. In that sense our approach avoids re-proof of pattern proof obligations in the instantiation. The reusability of a development is expre
    2 KB (232 words) - 15:23, 4 July 2013
  • Proof Purger Design
    ...sed proofs by selecting projects and/or files to purge. In addition, empty proof files are also proposed for purging. Integration of the proof purger as a popup menu is achieved in the manifest through the ''org.eclips
    3 KB (505 words) - 12:54, 12 August 2009
  • Proof Manager
    ...le for constructing proofs and maintaining existing proofs associated with proof obligations. Proof obligations are generated by the proof obligation generator and have the form of ''[http://handbook.cobra.cs.uni-d
    9 KB (1,478 words) - 10:33, 27 October 2011
  • Proof Obligation Commands
    In this page are presented various proof obligations commands that can be run from the Event-B Explorer as follows: ...rer. The selection can be a whole project, a model (context/machine), the 'Proof Obligations' node (equivalent to selecting the corresponding model), an ele
    3 KB (457 words) - 10:43, 18 March 2010
  • Refactoring Framework Release History
    ...). This renaming is not fully-functional at the moment and some discharged proof obligations may have to be discharged again. We intend to fix this problem ** Renaming of proofs would not save the proof files after renaming
    2 KB (357 words) - 12:18, 8 June 2010
  • SMT Plug-in Performance
    Performance is measured by running the SMT solvers on a set of proof obligations coming from some Event-B projects. Each solver is run in the ex :contains proof obligations to test, organized in Event-B projects
    4 KB (652 words) - 08:48, 6 June 2014
  • D23 Improvements to Existing Provers
    ...html One point rule], arithmetic rules), have been added to discharge more proof obligations more easily. * Reducing proof storage space.
    5 KB (789 words) - 11:41, 27 January 2010
  • Modeling Feedback
    Real goal is to obtain a proof, not a model. The model is only our mean of choice to obtain a proof.
    1 KB (153 words) - 13:44, 28 October 2008
  • User:Mathieu/Collections/Essai
    :[[Proof Purger Interface]]
    177 bytes (18 words) - 16:24, 6 January 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Retrieved from ‘https://wiki.event-b.org/index.php/Special:Search’