Line 22: | Line 22: | ||
== Sample Models == | == Sample Models == | ||
Some of the examples below are now [https://gitlab.cs.uni-duesseldorf.de/general/stups/prob2-jupyter-notebooks available as Jupyter notebooks] and can be [https://mybinder.org/v2/git/https%3A%2F%2Fgitlab.cs.uni-duesseldorf.de%2Fgeneral%2Fstups%2Fprob2-jupyter-notebooks.git/master launched using binder]. | Some of the examples below are now [https://gitlab.cs.uni-duesseldorf.de/general/stups/prob2-jupyter-notebooks available as Jupyter notebooks] and can be [https://mybinder.org/v2/git/https%3A%2F%2Fgitlab.cs.uni-duesseldorf.de%2Fgeneral%2Fstups%2Fprob2-jupyter-notebooks.git/master launched using binder]. Another [https://gitlab.cs.uni-duesseldorf.de/general/stups/prob-teaching-notebooks repository contains notebooks for teaching]. | ||
* [[TrainSwitchingPuzzle]] | * [[TrainSwitchingPuzzle]] |
ProB is a graphical animator and model checker for the B method. The ProB homepage is at http://www.stups.uni-duesseldorf.de/ProB, where precompiled binaries, installation instructions and documentation are available.
If you find a problem with ProB or this documentation please let us know. We are happy to receive suggestions for improvements to ProB or the documentation. More information about submitting bug reports is available in the "bugs" section or directly in our bug tracker. You can also post a question in our prob-users group or send an email to Michael Leuschel.
We are redesigning the user manual and developer handbook.
Animation and Visualisation with ProB:
Validation with ProB:
Other Interfaces to ProB:
ProB and Other Tools:
ProB for Other Languages:
Advanced Features of ProB:
Advanced Visualization Features of ProB:
FAQ, Tips and Troubleshootings:
(Also have a look at the tutorial; in particular Starting ProB and first animation steps).
Some of the examples below are now available as Jupyter notebooks and can be launched using binder. Another repository contains notebooks for teaching.
Please help us to improve this documentation by providing feedback in our bug tracker, asking questions in our prob-users group or sending an email to Michael Leuschel.