<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://docs.tlapl.us/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://docs.tlapl.us/feed.php">
        <title>TLA+ Wiki - using:tlc</title>
        <description></description>
        <link>http://docs.tlapl.us/</link>
        <image rdf:resource="http://docs.tlapl.us/_media/logo.png" />
       <dc:date>2026-04-30T08:29:31+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://docs.tlapl.us/using:tlc:config_file?rev=1727564665&amp;do=diff"/>
                <rdf:li rdf:resource="http://docs.tlapl.us/using:tlc:liveness?rev=1727539118&amp;do=diff"/>
                <rdf:li rdf:resource="http://docs.tlapl.us/using:tlc:start?rev=1727564603&amp;do=diff"/>
                <rdf:li rdf:resource="http://docs.tlapl.us/using:tlc:trace_validation?rev=1727539117&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://docs.tlapl.us/_media/logo.png">
        <title>TLA+ Wiki</title>
        <link>http://docs.tlapl.us/</link>
        <url>http://docs.tlapl.us/_media/logo.png</url>
    </image>
    <item rdf:about="http://docs.tlapl.us/using:tlc:config_file?rev=1727564665&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T23:04:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>config_file</title>
        <link>http://docs.tlapl.us/using:tlc:config_file?rev=1727564665&amp;do=diff</link>
        <description>Config files

The config files are used for TLC model checking.

The possible contents of the config file itself are presented below. The config file has .cfg extension, and usually has the same name of your spec (.tla file).

TODO: values supported in config files. Typed model values.</description>
    </item>
    <item rdf:about="http://docs.tlapl.us/using:tlc:liveness?rev=1727539118&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T15:58:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>liveness</title>
        <link>http://docs.tlapl.us/using:tlc:liveness?rev=1727539118&amp;do=diff</link>
        <description>Liveness checks

if TLC is configured to check three temporal formulas A,B,C; TLC does not check if A, B or C are identical formulas. If TLC is set to check A, A, A (it will still create three OrderOfSolutions). It is up to the user to prevent this.</description>
    </item>
    <item rdf:about="http://docs.tlapl.us/using:tlc:start?rev=1727564603&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T23:03:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>http://docs.tlapl.us/using:tlc:start?rev=1727564603&amp;do=diff</link>
        <description>TLC Model Checker

TLC is an explicit state model checker originally written by Yu et al. [1999] to verify TLA+ specifications. TLC can check a subset of TLA+ that is commonly needed to describe real-world systems, most notably finite systems.

To run it, you will need Java runtime environment version 11.</description>
    </item>
    <item rdf:about="http://docs.tlapl.us/using:tlc:trace_validation?rev=1727539117&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T15:58:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>trace_validation</title>
        <link>http://docs.tlapl.us/using:tlc:trace_validation?rev=1727539117&amp;do=diff</link>
        <description>Trace Validation

This is a comment from Markus Kuppe from Github.

Trace Validation (TV) essentially adopts this approach by mapping recorded implementation states to TLA+ specification states. This method is practical as it derives implementation states directly from the execution of the implementation, avoiding the complexities of symbolic interpretation of the source code. However, TV is not exhaustive. It verifies that only a certain subset of all potential system executions aligns with the…</description>
    </item>
</rdf:RDF>
