Proof Dependencies and Reasoner Conflicts: Difference between revisions
imported>Nicolas mNo edit summary |
imported>Nicolas mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Until Rodin 2.1, 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 conflicts in reasoner versions. | Until Rodin 2.1 (included), 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 conflicts in reasoner versions. | ||
Hence the idea of integrating reasoners in proof dependencies and have them processed the same way as other proof dependency components, that are stored in the root element of the proofs to allow for quick access. This improves performances in updating proof statuses, which is by far the most time-consuming build operation. | Hence the idea of integrating reasoners in proof dependencies and have them processed the same way as other proof dependency components, that are stored in the root element of the proofs to allow for quick access. This improves performances in updating proof statuses, which is by far the most time-consuming build operation. | ||
This evolution is available since Rodin 2.2. It applies to all proofs edited using Rodin 2.2+. Proofs edited using previous versions of the tool are kept in the older format, thus slowing down the build time. | |||
In order to upgrade proof storage for proofs made using Rodin prior to 2.2, use '''Simplify Proof(s)''' on a proof or component or project. | |||
This works for reusable proofs, broken proofs need to be manually edited. (It will not actually make any modification as the simplification has been disabled since Rodin 2.0.) | |||
{{TODO|Document proof storage}} | {{TODO|Document proof storage}} | ||
Latest revision as of 14:49, 6 June 2011
Until Rodin 2.1 (included), 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 conflicts in reasoner versions.
Hence the idea of integrating reasoners in proof dependencies and have them processed the same way as other proof dependency components, that are stored in the root element of the proofs to allow for quick access. This improves performances in updating proof statuses, which is by far the most time-consuming build operation.
This evolution is available since Rodin 2.2. It applies to all proofs edited using Rodin 2.2+. Proofs edited using previous versions of the tool are kept in the older format, thus slowing down the build time.
In order to upgrade proof storage for proofs made using Rodin prior to 2.2, use Simplify Proof(s) on a proof or component or project.
This works for reusable proofs, broken proofs need to be manually edited. (It will not actually make any modification as the simplification has been disabled since Rodin 2.0.)
TODO: Document proof storage
