136 findings. 135 test cases catalogued: 54 marked done, 53 still to do. Checked against Logisim-evolution 5.0.0 and classic 2.7.1. Last test run: 11 November 2026.
What “tested by us” means
We use four labels. Here is a real example of each.
The rule: we only write “we tested” when a finding or a test ID backs it. Every screenshot and verdict names its machine, and results from emulation or a virtual machine say so.
Our testing model: free machines only
We buy and borrow nothing, so every test runs on a free machine. That gives us real Windows and macOS desktops on GitHub’s runners, real package installs, and every Logisim window photographed in the lab. It cannot give us a student’s own laptop screen and scaling, touch on a real tablet, ChromeOS system screens, Wayland or tiling window managers, or an FPGA board. Tests that need those are marked as not possible in our catalog, and the page sections that depend on them rest on cited sources and say so.
The machines
| lab-lnx | Linux lab (Ubuntu 24.04 container, Xvfb) | lab |
|---|---|---|
| ci-w25 | GitHub-hosted Windows Server 2025 | ci |
| ci-w22 | GitHub-hosted Windows Server 2022 | ci |
| ci-warm | GitHub-hosted Windows 11 ARM64 | ci |
| ci-mac-arm | GitHub-hosted macOS 15 (Apple Silicon) | ci |
| ci-mac-x64 | GitHub-hosted macOS 15 (Intel) | ci |
| ci-ubu | GitHub-hosted Ubuntu 24.04 | ci |
| ci-fedora | Fedora container on a GitHub-hosted runner | ci |
| ci-arch | Arch Linux container on a GitHub-hosted runner | ci |
| ci-debian | Debian 12 container (Chromebook Linux stand-in) | ci |
| web-emu | Playwright device emulation (emulated, not a real phone) | emulated |
No rows match.
These are virtual machines in GitHub’s data centres with a real Windows or macOS desktop. A screenshot from them shows what Logisim draws on that system; it does not show a student’s own laptop. No physical PC, Mac, Chromebook, iPad, phone or FPGA board is used.
Test rounds
| 0 | 9 Nov 2026 | Local lab (40 scripted cases) and install lab on GitHub runners | lab1-2026-11-09-linux-local, ci-install-2026-11-09-run1 to run3 | F01 to F36 |
|---|---|---|---|---|
| 2 | 9 Nov 2026 | Components: truth tables, counter modes, port names | lab2-2026-11-09-components | F39 to F44, F51 |
| 3 | 9 Nov 2026 | Lab GUI shots, browsers, package managers | lab3-2026-11-09-gui, ci-round3-2026-11-09 | F45 to F50, F52 to F58 |
| 4 | 9 Nov 2026 | CI retries and stand-ins | ci-round4-2026-11-09 | F59 to F63 |
| 5 | 9 Nov 2026 | macOS Gatekeeper dialog and first paint | ci-round5-2026-11-09 | F64 |
| 6 | 11 Nov 2026 | Sequential vectors, flip-flops, RAM, older jars, port geometry, circuit generation | lab4, lab5-2026-11-11 | F65 to F73 |
| 7 | 11 Nov 2026 | Oscillation, clock, tutorial, 7-segment, subcircuits and tool acceptance runs | lab6 to lab10-2026-11-11 | F74 to F90 |
No rows match.
The lab runs are scripts that can be re-run: lab/run_local.py, lab/gen_components.py, lab/gen_counter_modes.py, lab/run_osc.sh, scripts/verify_circuits.py and the tool tests scripts/qa_*.mjs.
How circuits and tools are checked
Every downloadable circuit has a sidecar file with its SHA-256 and how it was checked: a test vector run in Logisim-evolution 5.0.0, or a command-line table compared with the expected rows. Circuits that oscillate by design are checked to fail with the word oscillating on the expected rows. Classic 2.7.1 twins are read through the 5.0.0 reader in tty mode. Tools are checked by browser tests, and the ones that write files for Logisim (the splitter and memory image tools) are checked by loading their output into Logisim.
What we have not tested
The catalog marks 53 test cases as still to do. The main gaps: nothing on a physical machine, no FPGA board, no Wayland or tiling window managers, no Windows or macOS GUI hand tests (only the runners’ screenshots), and several attribute and dialog tests in the window. Each page lists its own gaps next to the claim.
Evidence browser
File compatibility results are explained on the .circ file page. Every finding and every test has a stable link: /how-we-test/#F17 or /how-we-test/#T-ERR-02.
Findings (136)
F01 Logisim-evolution 5.0.0 command-line options
--help lists 18 options (corrected 12 Nov 2026: an earlier count of 19 was wrong), including -t/--tty <format>, -w/--test-vector <circuit> <vector> <file>, -b/--test-circuit, -l/--load <file> [label], --save, -n/--new-file-format <in> <out>, -s/--substitute, -f/--test-fpga, --fpga-cable, -g/--gates ANSI|IEC, -o/--locale, -m/--geometry, -u/--user-template, --toplevel-circuit, --no-splash, --clear-prefs, -v/--version, -h/--help. The tty formats accepted (comma-separated, e.g. table,speed) are table, speed, tty, halt, stats, binary, hex, csv, tabs (source: Startup.java at the v5.0.0 tag). Evidence: lab1…/logs/cli-help.txt; research/upstream/upstream-facts.md §5.3.
Evidence: lab1…/logs/cli-help.txt; research/upstream/upstream-facts.md §5.3.
F02 Opening a classic (2.7.1-format) file in 5.0.0 shows a compatibility warning
Dialog title "Old file format -- compatibility mode": the file was made with original Logisim, some components evolved, and labels will be converted to match VHDL naming rules. In tty mode the same text goes to the log; in the GUI the dialog must be dismissed before anything else happens. Evidence: logs/compat-warning.txt, shot lab-lnx-le500-compat-mode-dialog-01.png.
Evidence: logs/compat-warning.txt, shot lab-lnx-le500-compat-mode-dialog-01.png.
F03 After opening a classic-format file in the 5.0.0 GUI, wires stayed grey and pins showed 0 until Simulate → Reset Simulation (Ctrl+R)
After the reset the expected colours appeared (bright green 1, red E, blue U). Observed twice with two different files on Linux and again on macOS (F35). Later checks (F45) show it also happens with files saved by 5.0.0 and that a single click on the canvas also updates it; see F45 and F49. Evidence: shots lab-lnx-le500-wire-colours-grey-before-reset-01/02.png vs …-after-reset-01/02.png.
Evidence: shots lab-lnx-le500-wire-colours-grey-before-reset-01/02.png vs …-after-reset-01/02.png.
F04 Classic Logisim 2.7.1 cannot open a file saved by 5.0.0, even a plain full adder
It stops with "File Error: … The built-in library FPArithmetic is not available" because every 5.0.0 file declares the Floating Point Arithmetic library. Evidence: shot lab-lnx-l271-file-error-fparithmetic-01.png; the converted file is lab1…/circuits/full-adder-v5.circ (its header lists #FPArithmetic).
Evidence: shot lab-lnx-l271-file-error-fparithmetic-01.png; the converted file is lab1…/circuits/full-adder-v5.circ (its header lists #FPArithmetic).
F05 `--tty table` means different things in the two versions
5.0.0 enumerates every input combination and prints a full truth table, then exits (full adder: 8 correct rows). Classic 2.7.1 prints the outputs for the current inputs and keeps simulating until a pin labelled halt goes high: without a halt pin it never exits (killed after 25 s). Evidence: logs/tty-table-full-adder-le.txt, logs/tty-table-full-adder-271.txt.
Evidence: logs/tty-table-full-adder-le.txt, logs/tty-table-full-adder-271.txt.
F06 A NOT gate wired to its own input settles at E in tty output and shows a red loop in the GUI
The tty run prints no "Oscillation apparent" text; the value is simply E. Evidence: logs/err-oscillation*.txt, shot lab-lnx-le500-oscillation-loop-01.png. (The GUI message and its behaviour with auto-propagate: test T-ERR-07.)
Evidence: logs/err-oscillation*.txt, shot lab-lnx-le500-oscillation-loop-01.png. (The GUI message and its behaviour with auto-propagate: test T-ERR-07.)
F07 Two drivers on one net:
disagreeing values give E (red wire); equal values give the value. Evidence: logs/err-conflict.txt, shot …wire-colours-after-reset-01.png (case 2).
Evidence: logs/err-conflict.txt, shot …wire-colours-after-reset-01.png (case 2).
F08 A net that nothing drives reads `U` in tty output and is drawn blue; an output pin on it shows `U`
(Older docs and users call this "X"; 5.0.0 displays U.) Evidence: logs/err-floating.txt, shot …wire-colours-after-reset-02.png (case 3).
Evidence: logs/err-floating.txt, shot …wire-colours-after-reset-02.png (case 3).
F09 A 4-bit wire into a 1-bit pin is drawn orange with "Incompatible widths" at the bottom of the canvas; the output reads `U` for every input
Evidence: logs/err-width.txt, shot …wire-colours-grey-before-reset-01.png (orange wire and message).
Evidence: logs/err-width.txt, shot …wire-colours-grey-before-reset-01.png (orange wire and message).
F10 Tri-state bus with two Controlled Buffers:
none enabled → U; exactly one enabled → its value; both enabled with different values → E; both enabled with equal values → the value. Evidence: logs/tristate-bus.txt (16 rows).
Evidence: logs/tristate-bus.txt (16 rows).
F11 Splitter 8 → 4+4:
the first fan-out end carries bits 0–3 (low nibble), the second bits 4–7, e.g. input 0x12 gives Lo = 0010, Hi = 0001. Evidence: logs/splitter.txt. (Lab note: a splitter written to a file without its per-bit mapping attributes loaded with no bits mapped; only hand-written files hit this.)
Evidence: logs/splitter.txt. (Lab note: a splitter written to a file without its per-bit mapping attributes loaded with no bits mapped; only hand-written files hit this.)
F12 ROM contents saved inside the .circ load with the file
(16 words read back correctly). Evidence: logs/rom-embedded.txt.
Evidence: logs/rom-embedded.txt.
F13 `--load` is silently ignored by `--tty table` when the circuit has no `halt` pin
The truth table is computed before memories are loaded (source: TtyInterface.java, table analysis at line 344, memory loading at line 356), so a ROM driven by an input pin reads all zeros. Use a clocked circuit with a halt pin, or store the contents in the file. Evidence: logs/rom-load-table-ignored.txt.
Evidence: logs/rom-load-table-ignored.txt.
F14 Memory image formats that load (5.0.0, `--load` into a 16×8 ROM):
v2.0 raw (including run-length 4*aa), v3.0 hex words plain, v3.0 hex words addressed (word addresses; gaps become 0), v3.0 hex bytes plain. Evidence: logs/rom-load-{raw,raw-rle,words-plain,words-addr,bytes-plain}.txt, images in lab1…/memory-images/.
Evidence: logs/rom-load-{raw,raw-rle,words-plain,words-addr,bytes-plain}.txt, images in lab1…/memory-images/.
F15 Memory image failure modes:
a file without a recognised first-line header (including a plain list of 0x11 0x22 …) is rejected with "Hex file header not recognized" and the memory stays empty; an invalid token (zz) gives a warning ("Line 2: "zz" is not valid hex data") and that word becomes 0; a value wider than the memory (100 in an 8-bit ROM) is silently truncated to 00 with no warning. Evidence: logs/rom-load-{noheader,hex0x, bad,toowide}.txt.
Evidence: logs/rom-load-{noheader,hex0x, bad,toowide}.txt.
F16 `--load` takes every following argument as its own
(unlimited values: file, then label), so the .circ file must come before it: --tty table circuit.circ --load image.txt [label]. Putting --load file label before the circuit makes the parser report "Invalid arguments for --load". Evidence: lab notes in prd/D-testing-guide.md §5 (T-MEM-03), Startup.java (Option.UNLIMITED_VALUES).
Evidence: lab notes in prd/D-testing-guide.md §5 (T-MEM-03), Startup.java (Option.UNLIMITED_VALUES).
F17 Command-line test vectors print a pass/fail summary but always exit with code 0,
even when a vector fails ("Error on test vector 8: S = 1 (expected 0)", "Passed: 7, Failed: 1"). Same on Linux, Windows x64, Windows ARM64, macOS arm64 and Intel. Autograders must parse the text, not the exit code. Note: upstream docs/test_vector.md in the 5.0.0 source says a failing run exits non-zero; our runs on five systems contradict that. Root cause in source: Startup.java (v5.0.0, around line 1090) calls proj.doTestVector(…) and discards its return value, while doTestVector itself returns a failure count/code; the separate -b/--test-circuit test bench does exit −1 on failure. Evidence: logs/tv-pass.txt, logs/tv-fail.txt, ci-…-run2/*/test-vector-fail.txt.
Evidence: logs/tv-pass.txt, logs/tv-fail.txt, ci-…-run2/*/test-vector-fail.txt.
F18 `--test-vector` and `--new-file-format` need a display
With -Djava.awt.headless=true or no X display they crash with java.awt.HeadlessException (exit code 1); --tty works headless. --new-file-format also stops at the compatibility dialog (F02) until it is dismissed, writes the new file, and then does not exit. On a server, run these under Xvfb. Evidence: logs/tv-headless.txt, ci-…-run2/macos-15/test-vector-pass-headless.txt.
Evidence: logs/tv-headless.txt, ci-…-run2/macos-15/test-vector-pass-headless.txt.
F19 Simulation speed, 16-bit counter counting to 65,535 (131,069 ticks), `--tty speed`:
5.0.0 ran at 405–465 kHz (3 runs: 404,533 / 426,934 / 464,783 Hz) and classic 2.7.1 at 112–138 kHz (3 runs: 121,585 / 138,112 / 111,548 Hz) on the same machine and Java 21: about 3.5× faster (ratio of medians 426,934 / 121,585). (An earlier unrecorded run gave a similar 3.7–4× spread; only the stored logs count.) GitHub Windows runners ran 5.0.0 at 496 kHz (x64) and 526 kHz (ARM64). Evidence: logs/speed-*.txt, ci-…-run2/windows-*/tty-speed.txt. (Synthetic benchmark; real CPU designs: test T-PERF-02.)
Evidence: logs/speed-*.txt, ci-…-run2/windows-*/tty-speed.txt. (Synthetic benchmark; real CPU designs: test T-PERF-02.)
F20 The 5.0.0 jar needs Java 21
Java 8: "Error: A JNI error has occurred … UnsupportedClassVersionError … class file version 65.0, this version of the Java Runtime only recognizes class file versions up to 52.0". Java 17: "Error: LinkageError occurred while loading main class … (class file version 65.0) … up to 61.0". Java 21 runs it. Evidence: logs/java8-le.txt, logs/java17-le.txt, logs/java21-le.txt.
Evidence: logs/java8-le.txt, logs/java17-le.txt, logs/java21-le.txt.
F21 Classic 2.7.1 runs on Java 17 and 21
On Ubuntu's openjdk-8-jre-headless it crashes with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper; adding -Djavax.accessibility.assistive_technologies=" " (or using a newer Java) fixes it. Evidence: logs/java8-271.txt, logs/java8-271-fix.txt, logs/java17-271.txt, logs/java21-271.txt.
Evidence: logs/java8-271.txt, logs/java8-271-fix.txt, logs/java17-271.txt, logs/java21-271.txt.
F22 `apt install logisim` on Ubuntu 24.04 installs classic 2.7.1
(package 2.7.1~dfsg-4, universe), not Logisim-evolution; its jar is a rebuild with a different SHA-256 from the SourceForge jar. Evidence: datasets/jar-hashes.txt, ci-…-run1/ubuntu-24.04/apt-policy.txt.
Evidence: datasets/jar-hashes.txt, ci-…-run1/ubuntu-24.04/apt-policy.txt.
F23 Component counts:
5.0.0 has 178 components that can be placed from the library tree, in 14 libraries (Wiring 14, Gates 13, Plexers 5, Arithmetic 13, FP Arithmetic 18, Memory 11, I/O 17, Input/Output-Extra 7, TTL 65, HDL-IP 2, TCL 2, BFH-Praktika 2, Soc 8, Base 1); classic 2.7.1 has 57 in 7 libraries. Evidence: datasets/component-ports-le500.tsv, datasets/component-ports-l271.tsv. (The upstream count of 179 in research/upstream/components.json includes one component without an Add tool.)
Evidence: datasets/component-ports-le500.tsv, datasets/component-ports-l271.tsv. (The upstream count of 179 in research/upstream/components.json includes one component without an Add tool.)
F24 Official 5.0.0 asset sizes and SHA-256 (downloaded 9 Nov 2026):
| Asset | Bytes | SHA-256 | |---|---|---| | logisim-evolution-5.0.0-all.jar | 54,448,596 | 6b368e894742c04cc83aa9830f869bcab0190ede4df43ad6fecdb89b3a23a41c | | logisim-evolution-5.0.0-amd64.msi | 79,131,012 | a6eb97f814bb4ca0f083efe3e44081af94fe528b5c480bcc8380b4e741bb9b65 | | logisim-evolution-5.0.0-aarch64.msi | 77,194,873 | 5a2a57d58fa60328dd9dc8a69085ba88060f8cf7347a9deca41c3ef3b42a6c8a | | logisim-evolution-5.0.0-windows-amd64.zip | 77,440,974 | 59f11c42d4ae45c8656ab280403cf215a4a8d391f22468dc9a57deccb7e83427 | | logisim-evolution-5.0.0-windows-aarch64.zip | 75,421,328 | 38c23d3187893aa2791ca3675bc7feacb209cc87d976f9c4c30a10c3692a88aa | | logisim-evolution-5.0.0-aarch64.dmg | 82,128,932 | 94d2af5850565b76d87602e6908858175945f7f764111f0c8a357d882757b179 | | logisim-evolution-5.0.0-x86_64.dmg | 84,170,401 | 135fb814636850c1230b35603f703c031e140adfd47962c7e79a7dd2999876d3 | | logisim-evolution_5.0.0_amd64.deb | 71,670,978 | f6d8b72dd6e288400b52aa5841a559b0e437d6646fd731c10e14d8c778d65d51 | The .rpm (71,681,447 bytes per the release page) has not been hashed yet (T-INST-L04). Evidence: ci-…-run1/*/downloads.json.
Evidence: ci-…-run1/*/downloads.json.
F25 The Windows MSI is not digitally signed
(Authenticode status NotSigned). A silent install (msiexec /i … /qn) succeeded (exit 0) in 4.2 s on Windows Server 2025, using 128.0 MB (x64) and 125.0 MB (ARM64) in C:\Program Files\logisim-evolution\, with a Start-menu shortcut and a .circ file association. Evidence: ci-…-run1/windows-*/msi-*.txt|json, install-size.txt, start-menu.json, circ-association.txt.
Evidence: ci-…-run1/windows-*/msi-*.txt|json, install-size.txt, start-menu.json, circ-association.txt.
F26 Uninstalling the MSI (`msiexec /x`, exit 0) removes the program folder but leaves the preferences
in the registry at HKCU\Software\JavaSoft\Prefs\com\cburch\logisim (recent files, theme, appearance). On macOS the preferences file is ~/Library/Preferences/com.cburch.logisim.plist. Use --clear-prefs or delete these to reset. Evidence: ci-…-run1/windows-2025/prefs-registry.txt, ci-…-run1/macos-15/prefs-files.txt.
Evidence: ci-…-run1/windows-2025/prefs-registry.txt, ci-…-run1/macos-15/prefs-files.txt.
F27 Every installer carries its own Java runtime, and they differ:
Windows MSI (x64 and ARM64): Microsoft OpenJDK 21.0.4; Apple Silicon DMG: Oracle Java HotSpot 25.0.2; Linux .deb: Oracle Java HotSpot 26.0.1; Intel DMG: Eclipse Temurin 21.0.12.1. None of the bundled runtimes includes a java executable, so "use the bundled Java to run the jar" is not possible; users of the installers need no Java at all. Evidence: ci-…-run2/*/launcher-version.txt, runtime-bin*.txt, ci-…-run1/windows-*/install-tree.csv.
Evidence: ci-…-run2/*/launcher-version.txt, runtime-bin*.txt, ci-…-run1/windows-*/install-tree.csv.
F28 The app launchers accept the command-line options
logisim-evolution.exe --version (Windows), Logisim-evolution.app/Contents/MacOS/Logisim-evolution --tty table … (macOS) and /opt/logisim-evolution/bin/logisim-evolution --tty table … (Linux) all worked, so command-line use does not require a separate Java install. Evidence: ci-…-run2/*/launcher-*.txt.
Evidence: ci-…-run2/*/launcher-*.txt.
F29 macOS: both DMGs are ad-hoc signed with no Team ID and are not notarized
spctl --assess rejects the app (exit 3) with or without the quarantine flag; syspolicy_check distribution reports "Notary Ticket Missing" and an "Internal Xprotect Error" (both fatal for distribution). A downloaded copy therefore needs a manual override (right-click → Open, or System Settings → Privacy & Security → Open Anyway, or removing the quarantine attribute). The exact dialogs a user sees must be captured on a real Mac (T-INST-M01, T-INST-M02). Evidence: ci-…-run1/macos-*/codesign.txt, ci-…-run2/macos-*/spctl-*.txt, syspolicy-check.txt.
Evidence: ci-…-run1/macos-*/codesign.txt, ci-…-run2/macos-*/spctl-*.txt, syspolicy-check.txt.
F30 The Intel (x86_64) macOS DMG published as 5.0.0 actually contains a development build
Its jar is logisim-evolution-5.1.0dev-all.jar (manifest Implementation-Version 5.1.0-dev) and --version prints "Logisim-evolution v5.1.0dev, main/0315e02a (2026-09-13)". The Apple Silicon DMG, the MSIs and the .deb contain 5.0.0 (main/7c3343e1); the standalone -all.jar reports 5.0.0 built from main/7928a1c6. Seen on three separate runs (ci-install-2026-11-09-run3 again shows the 5.1.0dev jar), and visible to users: the main window's title bar reads "Logisim-evolution v5.1.0dev (ID:main/0315e02a, BUILT:2026-09-13T00:16:37+0000)" (ci-…-run2/macos-15-intel/gui-after-enter.png). Evidence: ci-…-run2/macos-15-intel/jar-inside.txt, launcher-version.txt, launcher-cfg.txt; ci-…-run1/macos-15-intel/bundled.txt. (Report upstream before publishing: see PRD §14.)
Evidence: ci-…-run2/macos-15-intel/jar-inside.txt, launcher-version.txt, launcher-cfg.txt; ci-…-run1/macos-15-intel/bundled.txt. (Report upstream before publishing: see PRD §14.)
F31 Homebrew: `brew install --cask logisim-evolution` fails
The cask is disabled ("does not pass the macOS Gatekeeper check", disabled 2026-09-01) and still points to 4.1.0. Evidence: ci-…-run1/macos-*/brew-*.txt.
Evidence: ci-…-run1/macos-*/brew-*.txt.
F32 Chocolatey lists `logisim-evolution 5.0.0 [Approved]`; winget resolves `logisim-evolution.logisim-evolution`
(winget output on the runner was cut by its progress bar; re-check on a real PC, T-INST-W05). Evidence: ci-…-run1/windows-2025/choco-search.txt, winget-show.txt.
Evidence: ci-…-run1/windows-2025/choco-search.txt, winget-show.txt.
F33 The official .deb installs to `/opt/logisim-evolution/`
(146 MB after install), launcher /opt/logisim-evolution/bin/logisim-evolution, a desktop entry (Categories=Utility, MimeType application/x-logisim-circuit), and removes cleanly with apt-get remove. Evidence: ci-…-run1/ubuntu-24.04/deb-*.txt, ci-…-run2/ubuntu-24.04/deb-files.txt, desktop-entry.txt.
Evidence: ci-…-run1/ubuntu-24.04/deb-*.txt, ci-…-run2/ubuntu-24.04/deb-files.txt, desktop-entry.txt.
F34 Snap: `logisim-evolution` latest/stable is 3.8.0 (2 Mar 2023, 215 MB)
Evidence: ci-…-run1/ubuntu-24.04/snap-info.txt.
Evidence: ci-…-run1/ubuntu-24.04/snap-info.txt.
F35 The app starts on Windows Server 2025, Windows 11 ARM64 and macOS 15 (arm64 and Intel) from the official packages
(process alive after 20 s; screenshots show the main window with the circuit). On macOS, opening a classic-format file with open -a left the splash screen saying "Loading file…" for 45 s because the compatibility dialog (F02) was hidden behind it; after pressing Return the main window appeared, with grey wires until a reset (F03 reproduced on macOS) and the orange "Incompatible widths" message. Evidence: ci-…-run*/windows-*/gui-*.png, ci-…-run2/macos-15/gui-wire-colours.png (splash) and ci-…-run2/macos-15*/gui-after-enter.png (main window).
Evidence: ci-…-run*/windows-*/gui-*.png, ci-…-run2/macos-15/gui-wire-colours.png (splash) and ci-…-run2/macos-15*/gui-after-enter.png (main window).
F36 Each of the 5.0.0 GitHub assets downloaded in 0.6–3 s on GitHub's runners;
sizes on disk after install: Windows 125–128 MB, macOS app 130 MB (arm64) / 134 MB (Intel), Linux 146 MB. Evidence: downloads.json, app-size.txt, install-size.txt, deb-install.txt.
Evidence: downloads.json, app-size.txt, install-size.txt, deb-install.txt.
F37 Combinational Analysis gives `+` (OR) and `*`/`&` (AND) equal precedence, left to right,
so a + b*c is read as (a + b)·c, not the textbook a + (b·c). Implicit AND by juxtaposition (a + b c) and | with & follow the textbook rule. Students who type a + b*c get a different circuit from the one they meant: use brackets or juxtaposition. Evidence: lab1…/logs/analysis-parser-precedence.txt (5.0.0 parser called directly by lab/probe/PrecTest.java, all 8 rows evaluated per expression). GUI confirmation: T-ANA-01.
Evidence: lab1…/logs/analysis-parser-precedence.txt (5.0.0 parser called directly by lab/probe/PrecTest.java, all 8 rows evaluated per expression). GUI confirmation: T-ANA-01.
F38 Test-vector parsing rules observed in 5.0.0:
column names must match pin labels exactly, including case ("Column a has no matching pin"); a decimal value must fit the column as a *signed* number (15 in a 4-bit column is rejected: "Too many bits in "15" expected 4 bits"); 0X1 with a capital X is rejected; an extra value on a row is rejected ("too many values"); a row with <set> 0 and <seq> 1 is rejected ("<Set> is 0 but <Seq> is 1, not 0"); a hex value containing a don't-care x on an input made that row fail with U outputs. Every load error still exits with code 0 (same cause as F17). Evidence: lab1…/logs/tv-parse-edge-cases.txt, files in lab1…/vectors/edge/.
Evidence: lab1…/logs/tv-parse-edge-cases.txt, files in lab1…/vectors/edge/.
F39 Multi-input XOR has two behaviours
With the default "Multiple-Input Behavior: When one input is on", a 3-input XOR is 1 only when exactly one input is 1 (inputs 111 give 0). With "When an odd number are on" it is a parity gate (111 gives 1). Evidence: lab2…/tables/xor3-one.txt, xor3-odd.txt.
Evidence: lab2…/tables/xor3-one.txt, xor3-odd.txt.
F40 Unconnected gate inputs are ignored
A 3-input AND or OR with one input left unconnected behaves exactly like a 2-input gate (no U or E on the output). Evidence: lab2…/tables/and3-one-floating.txt, or3-one-floating.txt.
Evidence: lab2…/tables/and3-one-floating.txt, or3-one-floating.txt.
F41 Plexer edge behaviour:
a Decoder whose Enable pin is left unconnected acts as enabled; a Decoder with three-state outputs drives the selected output 1 and leaves the others floating (U) when enabled, and drives all outputs 0 when disabled; a Multiplexer with Enable = 0 outputs 0; a Priority Encoder that is enabled with no input high outputs U on its address, 1 on Enable Output and 0 on Group Select. Evidence: lab2…/tables/decoder2*.txt, mux2-enable.txt, prienc4.txt.
Evidence: lab2…/tables/decoder2*.txt, mux2-enable.txt, prienc4.txt.
F42 The Comparator treats numbers as signed (two's complement) by default
With width 4, A = 1000 (−8) is *less* than B = 0001; switching "Numeric Type" to unsigned makes A greater. Evidence: lab2…/tables/comparator4-signed.txt, comparator4-unsigned.txt.
Evidence: lab2…/tables/comparator4-signed.txt, comparator4-unsigned.txt.
F43 Counter "Action On Overflow", measured (3-bit counter, maximum 5, 12 clock ticks):
*wrap* counts 0…5 then 0; *stay at value* stops at 5; *continue counting* ignores the maximum and runs 0…7 then 0 (the carry is still 1 at 5); *load next value* jumps to the Data input (2) after 5. Carry is 1 exactly while the value equals the maximum (counting down: while it is 0; down-counting wraps 0 → 5). Evidence: lab2…/counter-modes/*.txt (circuit files next to them).
Evidence: lab2…/counter-modes/*.txt (circuit files next to them).
F44 Every component's port names, measured from the 5.0.0 jar:
1,358 ports of the 178 placeable components with position, direction, width and the exact tooltip text Logisim shows (e.g. Counter "Up Down: when 1, counter increments, when 0, counter decrements"). Ports move with attributes (Counter data/output ports are at x = 180 for 3 bits but 190 for 4 and 8 bits), so generated circuits must re-probe. Evidence: lab2…/component-port-names-le500.tsv, lab/probe/Probe3.java.
Evidence: lab2…/component-port-names-le500.tsv, lab/probe/Probe3.java.
F45 Opening any circuit in the 5.0.0 GUI on the Linux lab showed grey wires and "0" on pins until the first click on the canvas or Simulate → Reset Simulation; moving the mouse alone did not update it
This also happens with a file saved by 5.0.0 itself (supersedes the "classic files only" wording of F03). Whether it happens on a normal desktop is checked on the Windows and macOS runners (round 3, F49). Evidence: lab3…/screenshots/lab-lnx-le500-native-v5-*.
Evidence: lab3…/screenshots/lab-lnx-le500-native-v5-*.
F46 5.0.0 menus and shortcuts (Linux/Windows key names), as shown in the menus:
File (New Ctrl+N, Merge… Ctrl+M, Open… Ctrl+O, Close Ctrl+Shift+W, Save Ctrl+S, Save As… Ctrl+Shift+S, Export project bundle… Ctrl+Shift+E, Export Image…, Print… Ctrl+P, Preferences…, Exit Ctrl+Q); Edit (Undo Ctrl+Z, Redo Ctrl+Shift+Z, Cut/Copy/Paste, Duplicate Ctrl+D, Select All Ctrl+A, Raise/Lower Ctrl+Up/Down, Raise To Top/Lower To Bottom Ctrl+Shift+Up/Down, Add/Remove Vertex); Project (Add Circuit…, Add/Import VHDL Entity…, Load Library, Move Circuit Up/Down Ctrl+Shift+U/D, Set As Main Circuit, Edit Circuit Layout/Appearance, Analyze Circuit, Get Circuit Statistics, Options…); Simulate (Auto-Propagate Ctrl+E, Single-Step Propagation Ctrl+I, Reset Simulation Ctrl+R, Manual Tick Half Cycle Ctrl+T, Manual Tick Full Cycle Ctrl+F9, Auto-Tick Enabled Ctrl+K, Auto-Tick Frequency, Timing diagram, Test Vector…, Assembly viewer); Window (Minimize Ctrl+Shift+M, Maximize, Close Ctrl+Shift+W, Show Toolbar, Show Navigation Pane, Combinational Analysis, Preferences); FPGA (FPGA Board Editor, Synthesize & Download…); Help (Find Action… Ctrl+Shift+A, Tutorial, User's Guide, Library Reference, About…). No menu item named "Export Circuit" appears in these menus; where 5.0.0's new selective circuit export is reached from is not verified yet (T-FILE-07). Evidence: lab3…/screenshots/lab-lnx-le500-menu-*.png. (macOS uses ⌘ for Ctrl: T-GUI-02 on ci-mac-arm.)
Evidence: lab3…/screenshots/lab-lnx-le500-menu-*.png. (macOS uses ⌘ for Ctrl: T-GUI-02 on ci-mac-arm.)
F47 Other 5.0.0 GUI facts seen in the lab:
Find Action lists 194 actions from 2 providers and opens with Ctrl+Shift+A; Preferences has the tabs Experimental, Software, FPGA Commander Settings, Hotkey settings, Autosave, Template, International, Window, Layout and Simulation, and the International tab offers 12 languages (German, Greek, English, Spanish, French, Portuguese, Russian, Italian, Dutch, Japanese, Polish, Chinese; plus gate shape ANSI/IEC); Export Image offers PNG, GIF, JPEG, TikZ and SVG with a scale factor and a "Printer View" option; the Timing diagram window has three logging modes (Stop-motion, Continuous real-time, Clocked), a time scale (default 5.0 µs) and keeps the last 400 values by default; Help → Library Reference opens a built-in "Logisim-evolution Documentation" window. Evidence: lab3…/screenshots/lab-lnx-le500-{find-action,preferences-international,export-image-dialog,timing-diagram-options}-01.png.
Evidence: lab3…/screenshots/lab-lnx-le500-{find-action,preferences-international,export-image-dialog,timing-diagram-options}-01.png.
F48 Analyze Circuit refuses to build expressions for a circuit that uses Tunnels:
a dialog "Expression Not Determined: Computing truth table instead of expression due to Tunnel." appears, and the window then shows the truth table, sum-of-products expressions and K-maps computed from the table (full adder: S and Cout correct). Evidence: lab3…/screenshots/lab-lnx-le500-analysis-*.png.
Evidence: lab3…/screenshots/lab-lnx-le500-analysis-*.png.
F49 Confirmed on a real Windows desktop (Windows Server 2025 runner):
a circuit saved by 5.0.0, opened with the official MSI install, showed grey wires and 0 on its pins; moving the mouse over the canvas changed nothing; one click on the canvas made the colours appear (green 1, red E, blue U). So F45 is real user-facing behaviour, not a lab artefact: tell readers to click the canvas or press Ctrl+R after opening a file. Evidence: ci-round3-2026-11-09/windows/gui-native-v5-{before-click,after-mousemove,after-click}.png.
Evidence: ci-round3-2026-11-09/windows/gui-native-v5-{before-click,after-mousemove,after-click}.png.
F50 logisim.app (checked 9 Nov 2026) runs classic Logisim in the browser through CheerpJ:
the window title reads "Logisim: main of Untitled" and the library list is the classic one (Wiring, Gates, Plexers, Arithmetic, Memory, Input/Output, Base). In desktop Chromium the page's load event fired after 1.4 s and the app was usable between 5 and 15 s, after 228 requests and about 28.7 MB of transfers; at phone size (390×844, emulated) it renders but the UI is too small to use comfortably. CircuitVerse's simulator loaded in 2.4 s (10 requests, about 0.56 MB). Evidence: lab3…/web/web-checks.json, lab-web-*.png, lab/web_checks.js.
Evidence: lab3…/web/web-checks.json, lab-web-*.png, lab/web_checks.js.
F51 FPGA without a board:
the 5.0.0 jar contains 31 board definitions (BASYS3, TERASIC_DE10_LITE, DE0_CV, ZYBO, …; list in lab2…/fpga/boards-in-5.0.0-jar.txt). --test-fpga full-adder-v5.circ main BASYS3 HDLONLY builds the netlist ("8 nets and 0 buses"), passes the DRC, lists the board's resources (51 pins, 21 buttons, 28 LEDs) and then stops with "Not all IO components have been mapped to the board "BASYS3"; please map all components to continue!" (exit code 255): HDL-only generation needs the I/O mapping saved in the file first. Evidence: lab2…/fpga/test-fpga-basys3-hdlonly.txt.
Evidence: lab2…/fpga/test-fpga-basys3-hdlonly.txt.
F52 Flathub `com.github.reds.LogisimEvolution` is 5.0.0
(stable branch updated 13 Sep 2026): 122.4 MB download, 262.4 MB installed (plus the freedesktop 25.08 runtime on first install; 47 s on the runner). It carries its own Java (OpenJDK 21.0.12.1, "Flathub"), runs through X11 (sockets=x11) and may only read and write files in your home folder (filesystems=home): files on other drives or in /tmp are not visible to it. --tty works from the command line. Evidence: ci-round3-2026-11-09/flatpak/*.txt.
Evidence: ci-round3-2026-11-09/flatpak/*.txt.
F53 Snap `logisim-evolution` installs version 3.8.0
(latest/stable, rev 4, 2 Mar 2023) with OpenJDK 17.0.6. It runs (--tty gave a correct table) but prints a GTK "symbol lookup error" on start, and it is two major versions behind. Evidence: ci-round3-2026-11-09/snap/*.txt (confirms F34).
Evidence: ci-round3-2026-11-09/snap/*.txt (confirms F34).
F54 The official RPM installs on Fedora 45
(dnf install ./logisim-evolution-5.0.0-1.x86_64.rpm, 139.3 MiB, pulls in desktop-file-utils, xdg-utils, which, emacs-filesystem) to /opt/logisim-evolution/ with a bundled Oracle Java 26.0.1, and runs. RPM SHA-256 9d3850149204d86a3beb7297a84210075c0fb604e6c21f3907b1fadf7b5ff699 (71,681,447 bytes). In our minimal container, dnf remove failed because the package's uninstall script (xdg-mime) found no writable system MIME directory; on a normal desktop this directory exists (container artefact, re-check on a VM before publishing removal steps). Fedora's own repositories have no logisim package. Evidence: ci-round3-2026-11-09/fedora/*.txt.
Evidence: ci-round3-2026-11-09/fedora/*.txt.
F55 AUR:
logisim-evolution-bin is at 5.0.0 but its PKGBUILD declares java-runtime>=16 (5.0.0 needs 21) and its build step calls unzip without declaring it, so makepkg failed on a clean Arch system ("unzip: command not found"); logisim-evolution (source build) is still at 4.1.0. Evidence: ci-round3-2026-11-09/arch/*.txt (round 4 re-tests with unzip installed).
Evidence: ci-round3-2026-11-09/arch/*.txt (round 4 re-tests with unzip installed).
F56 winget:
winget install --id logisim-evolution.logisim-evolution -e downloads the official x64 MSI from GitHub, reports "Successfully verified installer hash", and installs in 10.2 s; winget show lists version 5.0.0, publisher "logisim-evolution developers", licence GPL-3.0. Evidence: ci-round3-2026-11-09/windows/winget-*.txt (supersedes the truncated output in F32).
Evidence: ci-round3-2026-11-09/windows/winget-*.txt (supersedes the truncated output in F32).
F57 Chocolatey's `logisim-evolution` 5.0.0 package installs the `-all.jar`, not the MSI,
checks its hash, adds a Start-menu entry and warns that Java must be installed separately; Scoop's extras bucket also has 5.0.0 and suggests installing java/openjdk. With these two routes the user needs Java 21 (F20). Evidence: ci-round3-2026-11-09/windows/choco-*.txt, scoop-*.txt.
Evidence: ci-round3-2026-11-09/windows/choco-*.txt, scoop-*.txt.
F58 Classic 2.7.1 starts on Windows with Java 17
(Temurin 17.0.21 on the runner; process alive after 15 s, main window on screen). Evidence: ci-round3-2026-11-09/windows/l271-gui.{png,txt}, l271-java.txt.
Evidence: ci-round3-2026-11-09/windows/l271-gui.{png,txt}, l271-java.txt.
F59 The official .deb installs and runs in a Debian 12 (bookworm) container
(it pulls in about 100 desktop libraries; /opt/logisim-evolution/bin/logisim-evolution --version reports 5.0.0 with its bundled Oracle Java 26.0.1; --tty works). ChromeOS runs Linux apps in a Debian 12 container, so this is our evidence for the Chromebook route; it is not a test on a physical Chromebook. Evidence: ci-round4-2026-11-09/debian/*.txt.
Evidence: ci-round4-2026-11-09/debian/*.txt.
F60 With `unzip` installed, the AUR `logisim-evolution-bin` 5.0.0 package builds and installs
(13 s, 51.96 MiB, launcher /usr/bin/logisim-evolution) and runs on Arch's own Java (OpenJDK 27.0.1), giving a correct tty table. So the failure in F55 is only the undeclared unzip dependency. Evidence: ci-round4-2026-11-09/arch/*.txt.
Evidence: ci-round4-2026-11-09/arch/*.txt.
F61 The x64 MSI installs (exit 0) and runs on Windows Server 2022 (build 10.0.20348, the Windows 10-era platform)
; --version reports 5.0.0 with the bundled Microsoft OpenJDK 21.0.4. Evidence: ci-round4-2026-11-09/windows-2022/*.
Evidence: ci-round4-2026-11-09/windows-2022/*.
F62 macOS (15.8.2, arm64 runner):
the menu bar shows File, Edit, Project, Simulate, Window, Help and the shortcuts use ⌘ where Windows/Linux use Ctrl (File: New ⌘N, Merge… ⌘M, Open… ⌘O, Close ⇧⌘W, Save ⌘S, Save As… ⇧⌘S, Export project bundle… ⇧⌘E, Print… ⌘P); the File menu ends at Print… (no Preferences… or Exit, unlike F46). A native 5.0.0 file opened with the app showed grey wires before any click (as F45/F49; our click missed the small window, so the "after click" state on macOS is not captured). Opening a copy with the quarantine flag via open never returned and the step hit the 30-minute job timeout: consistent with Gatekeeper blocking the launch, but the dialog itself was captured in round 5 (F64). Evidence: ci-round4-2026-11-09/macos-15/menu-*.png, gui-native-v5-*.png, open-quarantined.txt (empty), spctl-status.txt ("assessments enabled").
Evidence: ci-round4-2026-11-09/macos-15/menu-*.png, gui-native-v5-*.png, open-quarantined.txt (empty), spctl-status.txt ("assessments enabled").
F63 Online simulators at phone/tablet size (emulated, 9 Nov 2026):
logisim.app and CircuitVerse both load in WebKit with iPad (gen 7) and iPhone 13 profiles and in Chromium with a Pixel 7 profile (load event 0.7–1.3 s; screenshots after 25 s show the classic Logisim window on logisim.app and the CircuitVerse editor). This proves they open in mobile browser engines at those sizes, not that they are comfortable to use with touch. Evidence: ci-round4-2026-11-09/web/web-emulation.json, *.png.
Evidence: ci-round4-2026-11-09/web/web-emulation.json, *.png.
F64 macOS 15.8.2 (arm64 runner), round 5:
- *Gatekeeper.* Opening a copy of the 5.0.0 app that carries the quarantine flag (as any browser download does) shows the dialog "“Logisim-evolution” Not Opened" with the text "Apple could not verify “Logisim-evolution” is free of malware that may harm your Mac or compromise your privacy." and the buttons Done and Move to Trash (plus a "?" help button). There is no "Open" button in this dialog. The system had started the app from a randomised AppTranslocation path while the dialog was up. Evidence: ci-round5-2026-11-09/macos-15/gatekeeper-dialog-01.png, -02.png, after-open-processes.txt. - *First paint on macOS.* The native 5.0.0 file showed grey wires before a click and the correct colours (green 1, red E, blue U) after one click inside the canvas: F49 holds on macOS too. Evidence: gui-native-v5-{before,after}-click.png. - *App menu.* The "Logisim-evolution" application menu holds About Logisim-evolution, Settings… (⌘,), Services, Hide Logisim-evolution, Hide Others, Show All and Quit Logisim-evolution (⌘Q): on macOS, Preferences is reached as Settings… here, not from the File menu (F62). Evidence: menu-app.png. - *Classic 2.7.1 on macOS.* java -jar logisim-generic-2.7.1.jar with Temurin 21.0.13 opens the classic window ("Logisim: main of Untitled", app menu "Main"). Evidence: l271-gui.png, l271-java.txt, l271-process.txt.
Evidence: ci-round5-2026-11-09/macos-15/gatekeeper-dialog-01.png, -02.png, after-open-processes.txt. - *First paint on macOS.* The native 5.0.0 file showed grey wires before a click and the correct colours (green 1, red E, blue U) after one click inside the canvas: F49 holds on macOS too. Evidence: gui-native-v5-{before,after}-click.png. - *App menu.* The "Logisim-evolution" application menu holds About Logisim-evolution, Settings… (⌘,), Services, Hide Logisim-evolution, Hide Others, Show All and Quit Logisim-evolution (⌘Q): on macOS, Preferences is reached as Settings… here, not from the File menu (F62). Evidence: menu-app.png. - *Classic 2.7.1 on macOS.* java -jar logisim-generic-2.7.1.jar with Temurin 21.0.13 opens the classic window ("Logisim: main of Untitled", app menu "Main"). Evidence: l271-gui.png, l271-java.txt, l271-process.txt.
F65 A test-vector row is combinational unless the file has `<set>` and `<seq>` columns: the circuit is reset before every row
Our 14-row flip-flop vector without those columns passed only 3 rows (a flip-flop forgot its state between rows; a clock held at 1 re-triggered on every row). With <set> 1 and <seq> 1…14 the same rows passed 14 of 14. The first step of a sequence starts with a reset; later steps start with a simulation tick. Evidence: lab5…/logs/vec-ff-without-seq.txt, logs/vec-ff.txt, vectors/ff.vec.txt. Upstream says the same in its test-vector guide (doc/en/html/guide/test_vector/test_vector_sequential.html in the jar).
Evidence: lab5…/logs/vec-ff-without-seq.txt, logs/vec-ff.txt, vectors/ff.vec.txt. Upstream says the same in its test-vector guide (doc/en/html/guide/test_vector/test_vector_sequential.html in the jar).
F66 Flip-flops in the Memory library (5.0.0), measured with a 14-step sequence plus read-outs
D, T, J-K and S-R flip-flops change only on the rising clock edge; changing inputs while the clock is 1, or the falling edge, changes nothing. The top pin (20,0) is Preset and the bottom pin (20,60) is Clear (tooltips: "When 1, pin state to 1/0 asynchronously"); both act at once and the state is kept after release. After a reset every flip-flop is 0. With Preset and Clear both 1, Clear wins and the state stays 0 after release. S-R with S = R = 1 on a clock edge leaves the state unchanged (from 0 and from 1). J-K with J = K = 1 toggles. Pin order: D and T have data at (-10,10), clock at (-10,50); J-K and S-R have J/S at (-10,10), K/R at (-10,30), clock at (-10,50); Q at (50,10), not-Q at (50,50). Evidence: lab5…/vectors/ff.vec.txt (14 of 14 pass), logs/ff-discover.txt, circuits/ff.circ.
Evidence: lab5…/vectors/ff.vec.txt (14 of 14 pass), logs/ff-discover.txt, circuits/ff.circ.
F67 RAM (Memory library, 5.0.0 defaults, separate Load and Store pins): a read needs Load = 1 and a rising clock edge; the output is floating until the first read
A write needs Store = 1 and a rising edge. The output holds its last value when Load goes back to 0 (it does not float again). An address that was never written reads 0. With Load and Store both 1 at the edge, the new value appears at the output. Evidence: lab5…/vectors/ram.vec.txt (15 of 15 pass, floating rows use <float>), logs/ram-discover.txt, circuits/ram.circ.
Evidence: lab5…/vectors/ram.vec.txt (15 of 15 pass, floating rows use <float>), logs/ram-discover.txt, circuits/ram.circ.
F68 Files saved by 5.0.0 open and compute correctly in 4.1.0 and 3.8.0 when they use only basic components
Four of our files (half adder, full adder, 4-bit ripple adder with a subcircuit, 1-bit ALU with a multiplexer) gave the complete, correct truth table in both older jars (--tty table, 4 + 8 + 512 + 64 rows each, 0 differences). Not shown: components new in 5.0.0, the GUI, or other attribute combinations. Evidence: lab5…/results.csv (8 cases file-5.0.0-in-…), logs/file-5.0.0-in-*.txt.
Evidence: lab5…/results.csv (8 cases file-5.0.0-in-…), logs/file-5.0.0-in-*.txt.
F69 Rotating a component is not always a plain 90° turn of its east-facing layout
Measured on the 5.0.0 jar for all 178 components in all four facings: 22 components differ from a pure rotation, among them splitters (facing west keeps bit 0 at the top: ports at (-20,10) … (-20,40), not reversed), gates facing west or south (same positions, input order reversed), multiplexers, demultiplexers, decoders and priority encoders (different positions), DIP switch, joystick and RGB LED. Our renderer and generated circuits therefore use the measured rows. Evidence: lab4-2026-11-11-port-matrix/ports-variants-le500.tsv (rows with facing=), README.md.
Evidence: lab4-2026-11-11-port-matrix/ports-variants-le500.tsv (rows with facing=), README.md.
F70 Opening a file in which a component's label equals the name of a circuit or component shows a modal dialog and removes the label
Text: "alu1 : One component in the circuit has the same label as the component name of the newly placed component. This label has been removed!" In a scripted --test-vector run (needs a display, F18) it blocks until OK is pressed, so the run hangs. The comparison ignores case (a RAM labelled ram triggered it too). Evidence: shot lab-lnx-le500-label-conflict-dialog-01.
Evidence: shot lab-lnx-le500-label-conflict-dialog-01.
F71 With `-Dsun.java2d.uiScale=2` the interface doubles but the circuit canvas does not
On the Xvfb screen, menus, tabs, icons and the circuit tree were drawn at twice the size while the circuit on the canvas stayed at its normal pixel scale, so it looked half as large next to the interface text. Use the zoom buttons or a higher zoom setting for the canvas. Lab observation only: a real HiDPI laptop screen was not tested (testing guide §0). Evidence: shot lab-lnx-le500-hidpi-uiscale2-01.
Evidence: shot lab-lnx-le500-hidpi-uiscale2-01.
F72 Test-vector special values: `<DC>` (don't care) and `<float>` (floating) are accepted for any width; a bare `x` is only a per-bit don't care in a binary value
x alone in an 8-bit column is rejected: "Test Vector data format error: Unexpected character 'x' in "x"" (exit code 0 as usual, F17). A 1-bit column accepts x. Evidence: lab5…/logs/tv-x-on-bus.txt, vectors/ram-x-on-bus.vec.txt, the 4-bit ALU vector (src/content/circuits/circ-alu-4bit.vec.txt, V column <DC>).
Evidence: lab5…/logs/tv-x-on-bus.txt, vectors/ram-x-on-bus.vec.txt, the 4-bit ALU vector (src/content/circuits/circ-alu-4bit.vec.txt, V column <DC>).
F73 Strings the 5.0.0 program is built to show (upstream source, not a behaviour test)
2,832 English UI strings and 477 error/warning candidates were extracted from the jar's resource bundles. Exact texts of the most searched ones: canvasOscillationError = "Oscillation apparent"; ttyHaltReasonOscillation = "halted due to detected oscillation"; simulateLimit = "Iterations until oscillation". Whether and where each message appears must be tested before it is shown as "we saw this" (T-ERR-08 stays open for the rest). Evidence: lab5…/strings-le500-en-all.tsv, strings-le500-en-messages.tsv, lab/extract_strings.py. Machine lab-lnx, official Logisim-evolution 5.0.0 -all.jar, run lab6-2026-11-11-oscillation/ (11 Nov 2026). Circuits are generated by lab/circgen/build_osc.py; vectors and logs are in the run folder.
Evidence: lab5…/strings-le500-en-all.tsv, strings-le500-en-messages.tsv, lab/extract_strings.py.
F74 A test-vector run prints the word "oscillating" next to the value E when a loop does not settle; `--tty table` prints only E
Example: Error on test vector 2: then Y = E (expected 0) oscillating. The word is the 5.0.0 string tveOscillating; the canvas message is canvasOscillationError = "Oscillation apparent" and the tty halt text is ttyHaltReasonOscillation (F73). Evidence: logs/osc-gate-feedback-tv.txt, osc-sr-latch-tv.txt, osc-level-ff-tv.txt, osc-rom-loop-tv.txt, osc-nand-sub-tv.txt.
Evidence: logs/osc-gate-feedback-tv.txt, osc-sr-latch-tv.txt, osc-level-ff-tv.txt, osc-rom-loop-tv.txt, osc-nand-sub-tv.txt.
F75 A single NOT gate wired to its own input does not oscillate: it settles at E, with no "oscillating" text
(tty table Q = E; test vector Q = E (expected 0)). The same holds for a NOT gate inside a subcircuit whose output is wired to its own input in the parent. A loop oscillates only when it has a defined value to start from: NAND(A, Y) is stable at Y = 1 for A = 0 and oscillates for A = 1. Refines F06. Evidence: logs/osc-not-loop-*.txt, osc-subcircuit-loop-*.txt, osc-gate-feedback-*.txt.
Evidence: logs/osc-not-loop-*.txt, osc-subcircuit-loop-*.txt, osc-gate-feedback-*.txt.
F76 Five loops oscillate in 5.0.0 and each has a fix that passes a test vector
(1) A NOR latch: set, hold, S = R = 1, then both released gives Q = E ... oscillating on the last row; at power-up with S = R = 0 the table already reads E E. Fixed with a D flip-flop. (2) NAND(A, Y) fed back, A = 1; fixed with a clocked D flip-flop in the loop. (3) A D flip-flop with Trigger = High Level and D = its own complement toggles while the clock is 1 (CLK 0 gives Q = 0, CLK 1 gives E); fixed with Rising Edge. (4) A ROM whose data output is wired to its own address through a start multiplexer: row 2 oscillates; fixed with a register in the address path (five rows pass). (5) A NAND cell in a subcircuit with its output wired to its own input in the parent; fixed with a flip-flop in the parent. Evidence: circuits/osc-*.circ, vectors/, logs/*-tv.txt; published as circ-oscillation-apparent-* with sidecars.
Evidence: circuits/osc-*.circ, vectors/, logs/*-tv.txt; published as circ-oscillation-apparent-* with sidecars.
F77 A D flip-flop clocked by its own inverted output did not oscillate:
with D = its own complement and the clock taken from the complement, --tty table gave Q = 0 and no E. We could not produce oscillation from a self-driven clock with this wiring. Evidence: logs/osc-clock-loop-tty.txt. We did not test a counter or register whose output feeds its own clear.
Evidence: logs/osc-clock-loop-tty.txt. We did not test a counter or register whose output feeds its own clear.
F78 The iteration limit can trip on a loop-free circuit
A line of NOT gates from a pin to an output settles with the default limit of 1,000 for 980 and 990 gates; with 1,000, 1,010 and 1,100 gates the output reads E for both input values. With the limit raised to 3,000 the 1,100-gate chain follows its input. Evidence: logs/osc-chain-*-tty.txt; published as circ-oscillation-apparent-long-chain and -limit-raised.
Evidence: logs/osc-chain-*-tty.txt; published as circ-oscillation-apparent-long-chain and -limit-raised.
F79 In the GUI, one tick (Ctrl+T) of a clock-driven NAND loop turned the wire red and the pin to E, but we saw no message text on the canvas
Before the tick the same file showed a grey wire and a pin reading 0 (the F45 behaviour). Capture: window 800 px wide on Xvfb, keys sent with lab/probe/Keys.java; the canvas bottom was empty. The on-canvas text is therefore not confirmed by us (T-ERR-07 stays open for a real machine). Evidence: screenshots/lab-lnx-le500-oscillation-clocked-nand-01.png, ...-before-tick-01.png.
Evidence: screenshots/lab-lnx-le500-oscillation-clocked-nand-01.png, ...-before-tick-01.png.
F80 A diagonal wire in a hand-written .circ file makes 5.0.0 hang while loading it:
--tty table and -w print nothing and do not return (killed after 20 s; the stack was in WireRepair.doOverlaps while reading the file). Only matters for generated or hand-edited files. Evidence: logs/osc-diagonal-wire-tty.txt.
Evidence: logs/osc-diagonal-wire-tty.txt.
F81 Clock behaviour in the 5.0.0 window (`lab7-2026-11-11-clock/`, Linux lab, keys sent with `lab/probe/Keys.java`)
A Clock feeding an 8-bit counter, opened and left alone for three seconds: the screenshot did not change (grey wires, Auto-Tick off by default). After Ctrl+T (Manual Tick Half Cycle) the circuit changed, and a second Ctrl+T changed it again. After Ctrl+K (Auto-Tick Enabled) the circuit kept changing without any further key or click, and the counter output read 00000011 four seconds later. We did not measure the achieved frequency of the window. Evidence: screenshots/01…06*.png (differences computed between consecutive shots).
Evidence: screenshots/01…06*.png (differences computed between consecutive shots).
F82 A rebuilt 16-bit counter with a halt pin (`circ-clock-and-simulation-benchmark`, counts to 65,535 = 131,069 ticks) ran `--tty speed` at 496,473 Hz on the Linux lab on 11 Nov 2026
Same design family and tick count as F19 (405–465 kHz earlier on the same machine); speed varies with the machine's load, so quote ranges, not single values.
F83 The finished half adder in the 5.0.0 window (`lab8-2026-11-11-tutorial/`, Linux lab, mouse and keys sent with `lab/probe/Keys.java`)
With the Poke tool selected (it is the active tool when a file opens), one click on input A gave A = 1, S = 1, C = 0, and a second click on B gave S = 0, C = 1; Logisim draws a magenta ring where you clicked. Project, Analyze Circuit opened a second window with the tabs Inputs & Outputs, Table, Expression and Minimized; the Table tab showed the four rows A B S C = 00 00, 01 10, 10 10, 11 01 and the Expression tab showed S = A⊕B and C = A·B. A project file with an empty <toolbar/> opens with no tool buttons at all; our generated files now carry the standard toolbar (Poke, Edit, Text, pins, gates, flip-flop, register). We did not build the circuit by hand with the mouse in this run (T-PROJ-tutorial is still to do on a developer machine).
F84 Splitter facts (lab, 5.0.0, `scripts/qa_splitter.mjs`)
A splitter file written without its bitN attributes can load with no bits mapped (F11), so generators write every one. Twenty generated configurations (default maps, right, centered and legacy appearance, empty ends, custom maps with None, descending, reversed, widths up to 64) gave the same per-end values in Logisim 5.0.0 as the Splitter Visualiser's rules. Bit Extender attributes in_width, out_width, type (zero, one, sign) gave, for 0x80, Zero 0x0080, One 0xff80, Sign 0xff80; for 0x70, Sign 0x0070. Classic-format twins of an 8-bit-in splitter read back as U in 5.0.0's tty reader, so only the 4-to-1 join has a 2.7.1 twin. Evidence: circ-splitter-* sidecars.
Evidence: circ-splitter-* sidecars.
F85 Twelve Gates-library parts match their boolean definitions in 5.0.0 (`circ-gates-gallery`, `--tty table`, 8 rows)
NOT, Buffer, AND, OR, NAND, NOR, XOR, XNOR, Odd Parity (equal to XOR for two inputs), Even Parity (equal to XNOR), Controlled Buffer and Controlled Inverter (output U when the control is 0). A 4-bit AND is bitwise. We did not test PLA, and our attempt to negate an input with a negate0 or negate1 attribute in a generated file did not give the expected AND-with-one-inverted-input table, so negation is not documented as tested.
F86 Plexers in 5.0.0 (`lab/circgen/build_plexers.py`, `--tty table`)
A 4:1 multiplexer (Select Bits 2, 64 rows), a 1:4 demultiplexer, 2-to-4 and 3-to-8 decoders and gate-level versions of a 2:1 multiplexer and a 2-to-4 decoder all matched their definitions. Two 1-bit pins wired straight to the 2-bit select gave U on all 64 rows; joined by a splitter (Fan Out 2, Bit Width In 2, facing west) the same circuit matched the 4:1 table. Evidence: circ-mux-*, circ-demux-*, circ-decoder-* sidecars.
Evidence: circ-mux-*, circ-demux-*, circ-decoder-* sidecars.
F87 Counter circuits in 5.0.0 (`lab/circgen/build_counter.py`, sequential test vectors)
A 4-bit counter with Maximum Value 0x9 and Wrap around counted 0 to 9 and back for 12 cycles with Carry 1 at 9 (up input and enable left unconnected). With the Up Down input at 0 it counted 9, 8, ... 0, 9. Two such counters (maximum 9 and 5), the units Carry wired to the tens count enable and one shared clock, counted 00 to 59 and wrapped over 62 cycles. Evidence: circ-counter-* sidecars (25, 25 and 125 steps, all passed).
Evidence: circ-counter-* sidecars (25, 25 and 125 steps, all passed).
F88 The Memory Image Generator's output loads in 5.0.0 (`scripts/qa_memimage.mjs`, 17 checks)
Three data sets (mixed words, runs, sparse) written as v2.0 raw, v3.0 hex words plain, v3.0 hex words addressed and v3.0 hex bytes plain and loaded with --load into our 16-word, 8-bit lab ROM gave the intended words (the lab table prints a row only when the value changes). ROM files made by the tool (contents embedded) read back correctly by test vector for 4×8, 6×16, 8×32, 5×2 and 4×64. A ROM with a 1-bit data width read back as U, and a ROM labelled rom raised the label-equals-name dialog (F70) and hung the headless test vector, so generated ROMs use the label memory.
F89 7-segment parts in 5.0.0 (`lab/circgen/build_7seg.py`, `lab9-2026-11-11-7seg/`)
The BFH BCD to seven segment decoder gave the standard patterns for 0 to 9 on outputs Segment A to G and floating (U) on all seven for inputs 10 to 15 (tty table, 16 rows). A 16-word ROM with bit 0 = a ... bit 6 = g, bit 7 = decimal point gave the intended words for 0 to F (test vector) and, through a splitter, drove a 7-Segment Display that showed 0 for N = 0 (screenshot). A Hex Digit Display showed b for 1011 (screenshot). Port positions of the display: a (20,0), b (30,0), c (20,60), d (10,60), e (0,60), f (10,0), g (0,0), decimal point (30,60) (F44). Not tested: Active On High?, multi-digit displays, the display's drawing for the other digits.
F90 Subcircuits in the 5.0.0 window (`lab10-2026-11-11-subcircuits/`, Linux lab, Keys.java)
In our 4-bit adder the circuit tree lists the subcircuit fa and main; the four placed copies are small boxes labelled with the instance names and showing fa's pin labels as ports; double-clicking fa in the tree opens its layout; with fa selected, Project, Edit Circuit Appearance opens an editor with a drawing toolbar and a box that has one port marker per pin (three on the left, two on the right). We did not save a custom appearance, reopen it, or test the pin-to-port placement rule. A label equal to the circuit name opened a modal dialog and hung our headless runs (F70).
F91 `--tty` formats on 5.0.0 (`lab11-2026-11-11-cli/logs/tty-*.txt`, Linux lab, 11 Nov 2026; T-CLI-02 in part)
On the full adder (no halt pin), table printed the 8-row truth table and exited 0. table,csv printed the same rows comma-separated, and table,hex printed output identical to table for 1-bit pins. The formats binary, hex, csv and tabs on their own printed nothing and kept running until we killed them at 12 s (exit 124). On the 200-count counter with a halt pin, halt printed halted due to halt pin through the logger at ERROR level and exited 0; speed printed 33250 Hz (399 ticks in 12 milliseconds); stats printed a component count table (Pin 2, Clock 1, Constant 1, Comparator 1, Counter 1; total 6 with and without subcircuits). Not run: tty with a TTY component, because we have no verified circuit for it yet.
F92 Command-line error behaviour on 5.0.0 (`lab11-2026-11-11-cli/logs/`; T-TV-05, T-CLI-04 and T-TV-06 in part)
-w main <pass vector> <full adder> printed Passed: 8, Failed: 0. The failing vector printed Error on test vector 8: with S = 1 (expected 0) and Passed: 7, Failed: 1; both exited 0 (this repeats F17). A circuit name that is not in the file (-w nosuch) printed Circuit 'nosuch' not found. and exited 0, so an autograder must look for the Passed: line and treat its absence as a failure. A missing file exited 255 with a Startup error line. --toplevel-circuit nosuch with --tty table threw a NullPointerException (stack in Analyze.getPinLabels) and exited 255. -n in.circ out.circ wrote a 4,241-byte file and exited 0. -b on a file with no test bench printed nothing and did not return within 20 s. --save <file> with a ROM-only circuit created no file (not tested with a RAM). Not run: -u, --substitute, --clear-prefs, -m.
F93 Classic 2.7.1 `-tty table` exits on its own when the file has an output pin labelled `halt` that reads 1 (`circ-l271-full-adder-halt`, Linux lab, 11 Nov 2026; T-CLI-03)
A full adder with all inputs 0 and a constant 1 on halt printed 0 0 (tab separated, one column per output pin other than halt) and returned exit code 0 in under a second. The same file generated without tristate = false on its input pins printed E E, because classic Pin components default to three-state, so unset inputs float. Evidence: lab/circgen/build_classic.py, scripts/verify_circuits.py (method classic-tty).
Evidence: lab/circgen/build_classic.py, scripts/verify_circuits.py (method classic-tty).
F94 Pressed shortcuts in the 5.0.0 window (`lab12-2026-11-11-shortcuts/`, Linux lab on Xvfb, keys and wheel sent with `lab/probe/Keys.java`; T-GUI-02 in part, Linux only)
On our half adder: Ctrl with the mouse wheel moved the zoom readout from ×1 to ×1.3 (three notches up) and back to ×1 (three notches down). With the Edit tool and the AND gate selected, the Up arrow turned the gate to face north (its wires no longer met it, and the output wire went red); Ctrl+Z put it back; Ctrl+Shift+Z turned it north again. Ctrl+D on the selected gate placed a copy on top of it, and Ctrl+Z removed the copy. The Right arrow on a gate already facing east changed nothing, as expected. Not pressed: every other shortcut (they are read from the menus, F46), anything on Windows or macOS, trackpad pinch and Shift+wheel panning.
F95 Combinational Analysis window in 5.0.0, full adder (`lab13-2026-11-11-analysis/`, Linux lab, mouse sent with `lab/probe/Keys.java`; T-GUI-08 in part)
Project, Analyze Circuit opened a window with the tabs Inputs & Outputs, Table, Expression and Minimized. Inputs & Outputs listed the input variables A, B, Cin and the output variables S, Cout, each list ending in "Click to add a new variable". The Table tab read "8 of 8 rows shown" and had the buttons "-", "1", "0", "Collapse Duplicated Rows", "Show All Rows" and two zoom buttons. The Expression tab had a Notation list (Mathematical) and gave S = A⊕B⊕Cin and Cout = A·B+(A⊕B)·Cin. The Minimized tab had Output, Format (Sum of products), Style (Numbered) and Notation lists above a Karnaugh map. Buttons along the bottom: Import Table, Build Circuit, Optimize minterms and Optimize maxterms (both greyed out here), Export Table and Export TeX. Build Circuit opened a dialog with Destination Project (the open project), Circuit Name (pre-filled with main, the name of the circuit being analysed), "Use Two-Input Gates Only" and "Use NAND Gates Only" (greyed out until the first is ticked). We named the circuit built, clicked OK, saved with Ctrl+S, and the saved file's built circuit passed an 8-row full-adder test vector (Passed: 8, Failed: 0). circ-combinational-analysis-built.circ is that file. Not tested: typing a table or expression, the NAND option, importing and exporting a table, the dialog when the name already exists, and the size limits.
F96 Circuits written by the Truth Table and K-Map tool (T8) compute exactly their tables in 5.0.0 (`scripts/qa_t8.mjs`, Linux lab, 11 Nov 2026; T-TOOL-8)
127 generated circuits, from 40 random functions (1 to 6 inputs, 1 to 3 outputs, some with don't-care rows) and 8 edge cases (constant 0 and 1, a single literal, parity of 6 and of 8 inputs with 128 terms and a two-level OR tree, a 10-input AND, shared products, multi-letter names), each as sum of products and product of sums and, for several outputs, with and without shared terms, all passed their full test vector with the official jar (-w main, Passed: n, Failed: 0). Don't-care outputs written as x in the vector passed. The files use wired gates (no tunnels). Opening a generated 3-input majority file in the window showed AND gates feeding an OR gate; Project, Analyze Circuit, Expression then gave F = A·B+A·C+B·C, so expressions are available (unlike a circuit with tunnels, F48). Gates are default-size, with inputs up to 10 per gate (the largest count we measured); more inputs use a tree. Not tested: the file in classic 2.7.1 (it cannot open 5.0.0 files, F04), and circuits above 10 inputs (the tool does not write them).
F97 Timing diagram in the 5.0.0 window (`lab14-2026-11-11-timing/`, Linux lab, mouse and keys sent with `lab/probe/Keys.java`; T-GUI-09 in part)
On circ-clock-and-simulation-counter (a clock driving an 8-bit counter), Simulate, Timing diagram opened a second window with the tabs Options and Timing diagram. Options had four boxes: Signals and Formats (one button, "Add or Remove"), Logging Mode (Stop-motion mode, Continuous real-time mode, Clocked mode; Clocked was selected), Timing Options (for Clocked mode: "Capture fine-grained details" unticked, Time scale 5.0 µs, Gate delay 200 ns greyed out, Clock Source CLK, Clock Discipline "capture on both edges", "Clock cycle: 2 ticks") and History ("Store unlimited history" unticked and a box "Number of recent values to store:"). A line at the bottom said that data is captured at each clock transition and that each clock cycle is recorded as 10.0 µs (5.0 µs per tick). "Add or Remove" opened the dialog "Drag signals to select or rearrange", listing CLK, Counter (300,100), halt and Q as available; all four were already in "Signals to be viewed". With the main window focused, eight presses of Ctrl+T (four clock cycles) filled the Timing diagram tab with the CLK waveform, the counter bus and the pin Q, and the counter read 0000 0100. File, Export Image… in the timing window listed the types PNG, GIF, JPEG, TikZpicture (*.tex), SVG and WaveDrom (*.json); all six wrote a file (PNG 488 × 140 px; SVG 19,316 bytes; WaveDrom 349 bytes, cnt-wave.json). The WaveDrom file named the signals CLK, Counter(300,100)[7..0], Q[7..0] and halt, with bus data 0000 0001 to 0000 0100. Our first export attempts printed "The image could not be created." because the file-name box still held our earlier text; clearing it fixed that. The window has no option to log to a file, and the Simulate menu has no Logging item (F46). The strings file also contains the old message "Add 'sysclk' signal in Simulate->Chronogram…", which we did not see. Not tested: the other two logging modes, the fine-grained option, a glitch, bus Expand and Format, zoom, and the cursor.
F98 Classic 2.7.1 logging window (`lab14-2026-11-11-timing/screenshots/classic-logging-*.png`, Linux lab, Java 21; T-GUI-09 in part)
On a classic-format counter file, Simulate, Logging… opened a window with the tabs Selection, Table and File. Selection listed the components Clock, Counter, halt and Q with the buttons Add >>, Change Radix, Move Up, Move Down, << Remove and Close Window. The File tab read "File output disabled.", with an Enable button (greyed out until a file is chosen), a File box, a Select… button and a ticked box "Include Header Line". Classic's Simulate menu also lists Simulation Enabled, Reset Simulation, Step Simulation, Tick Once (Ctrl+T), Ticks Enabled (Ctrl+K) and Tick Frequency. There is no timing diagram. Not tested: what a log file contains, or the Table tab with data.
F99 Tunnel rules in 5.0.0 (`lab15-2026-11-11-tunnels/`, `lab/circgen/lab_tunnel.py`, `--tty table`, Linux lab, 11 Nov 2026; T-COMP-03 in part)
An input pin with a tunnel on its port and an output pin with a tunnel on its port, both labelled x, gave Y = A. Labels Data and data did not connect: Y was U for both inputs, so labels are case-sensitive. Labels written into the file as x and x, or x and x, did connect (the file loader appeared to trim the label; we did not test typing a space in the window). Labels 2data, clk out and données connected to themselves, so a leading digit, a space inside and accented letters are accepted in a file. A tunnel in main and a tunnel of the same label inside a subcircuit did not connect: the subcircuit's output pin was U, so tunnels do not cross the subcircuit boundary. Passing the signal in through an input pin of the subcircuit gave the right value. Two input pins on one label gave E when they disagree and the common value when they agree (as F07). A 4-bit tunnel and a 1-bit tunnel on 1-bit pins gave Y = A in --tty table; we did not look at the window, so we say nothing about width warnings for tunnels. Published circuits: circ-tunnel-* (six, verified by test vector or exact table).
F100 Pins, probes and constants in 5.0.0 (`lab16-2026-11-11-pins/`, `lab/circgen/lab_pins.py`, `--tty table`, and the Properties panel in the window, Linux lab, 11 Nov 2026; T-COMP-04 in part)
Selecting an input pin showed these properties: FPGA supported, Facing, Type, Data Bits, Behavior (Simple), Label, Label Location, Label Font, Radix (Binary), Appearance (Classic Logisim) and Reset value (0x0). An output pin showed the same list without Behavior and Reset value. An output pin with nothing driving it read U, and writing Simple, Tri-state, Pull Down or Pull Up into its Behavior attribute in the file changed nothing (still U), which matches the output pin having no Behavior property. An input pin read through a NOT gate gave the same table (A = 0 gives Y = 1, A = 1 gives Y = 0) for all four Behavior values, because the table enumerates 0 and 1 only. A Probe wired to the same net did not add a column: the table had only the labelled pins A and Y. A 4-bit Constant with Value 0xA on a 4-bit output pin read 1010, Power read 1 and Ground read 0. A 4-bit pin wired to a 1-bit pin gave Y = U for every value of A (the window's orange wire and message are F09). Not tested: what Pull Down or Pull Up does to a floating bit on an input pin (the table cannot create one), Poke dialogs "Enter Decimal" and "Enter Float", and 4.0-era files opened in 5.0.0.
F101 Registers in 5.0.0 (`lab/circgen/build_register.py`, sequential test vectors, Linux lab, 11 Nov 2026; T-COMP-09 in part)
An 8-bit Register stored its input on a rising clock edge while Enable was 1 (0xA5). With Enable at 0, a full clock pulse left the value unchanged. With Enable back at 1 the next edge stored 0x3C. Clear at 1 set the output to 0 with no clock edge, so Clear is asynchronous. With the Enable input left unconnected (test-data/lab17-2026-11-11-registers/reg-floating-enable.circ), a rising edge still stored the input, so a floating Enable counts as 1. A 4 × 8 register file made of four Registers, a Decoder with Enable (select 2 bits, its Enable wired to the write-enable input, each output wired to one register's Enable), and two 4:1 Multiplexers for read addresses RA and RB, passed a 23-step sequential vector: write 0x11, 0x22, 0x33 and 0x44 to registers 0 to 3, a clock pulse with write enable 0 changed nothing, all four read back on both ports, and a later write of 0xAB to register 2 appeared on port A. The Clear input of each register was wired to a constant 0. Not tested: Shift Register, the State tab, Register with Load or other trigger types, and a register transfer over a tri-state bus.
F102 Autograder run on 30 student-style variants of the full adder (`lab17-2026-11-12-test-vectors/`, Linux lab, 5.0.0, T-TV-05)
Each file ran with -w main <8-row vector> <file> under Xvfb with a 30 s limit. Raw exit codes: 0 for 24 files, 124 (our timeout) for 5 files, 255 for the missing file; no failing test vector ever gave a non-zero code (F17). Outcome by class: 10 files gave Passed: 8, Failed: 0; 7 gave a summary with failures (wrong gate, swapped outputs, unconnected output or input, constant fighting an output, three-inverter ring); 8 printed no summary line (label case or spelling, missing pin, circuit not named main, a 2-bit output, a main circuit with no pins); 5 hung on a modal dialog until killed (classic 2.7.1 format file, empty file, plain text, truncated XML, unknown built-in library). Messages seen without a summary: Error preparing test vector: Column S has no matching pin, Column S has width 1 but pin has width 2, Circuit 'main' not found.. Passes a grader may not want: an output pin turned into an input pin (the vector drove it and passed 8 of 8), a label with a trailing space (S matched S), extra input or output pins, files with CRLF line endings or a byte-order mark, and files whose header says 3.8.0 or 9.9.9 (no dialog). The 3-inverter ring reported Passed: 0, Failed: 8, not an oscillation text. The script public/downloads/autograde-logisim.sh (parse Passed: N, Failed: 0, N equal to the row count, no Exception, timeout) gave the right verdict on all 30 after we fixed a bug in our own variant 03 (the first OR Gate text was in the toolbar). Not run: a file saved by 4.1.0, a cheating design (ROM lookup), a hang from an oscillating circuit. Evidence: datasets/autograder.csv, logs/autograder-raw/, circuits/variants/, screenshots/.
Evidence: datasets/autograder.csv, logs/autograder-raw/, circuits/variants/, screenshots/.
F103 `-b/--test-circuit` hangs on a Questa folder chooser in our lab (T-TV-06)
The 5.0.0 bytecode shows -b looks for a circuit named logisim_test_verif with output pins test_bench_done_o and test_bench_ok_o, starts the VHDL simulator, ticks until done and ok are both 1 (60 s limit), then prints Test bench pass and calls System.exit(0), or prints Test bench fail and calls System.exit(-1) (a shell sees 255). We built four such files (done and ok 1, ok 0, done 0, wrong pin names). All four, run with -b, sat with a folder chooser open (stack: VhdlSimulatorTop.enable to Softwares.setQuestaPath to JFileChooser.showOpenDialog) and had not printed anything after 100 s; the earlier run on a file with no bench (F92) hung the same way. So we have no measured pass or fail exit code for -b; the exit values are from the bytecode only. Evidence: logs/bench-*.txt, screenshots/bench-folder-chooser.png, lab/circgen/build_bench.py.
Evidence: logs/bench-*.txt, screenshots/bench-folder-chooser.png, lab/circgen/build_bench.py.
F104 Clock component and `<float>`/`<DC>` in vectors on 5.0.0 (T-TV-04, headless)
With a Clock component instead of a CLK pin, a vector with only the output column and <set> 1 and <seq> 1 to 6 passed 6 of 6 (0x0 0x1 0x1 0x2 0x2 0x3): each step after the first advances the clock by one half cycle. A CLK column on that file is rejected: Error preparing test vector: Column CLK has no matching pin. On our controlled buffer a row expecting 0 while the buffer floats failed with Y = U (expected 0); rows expecting <float> or <DC> passed. Evidence: lab17…/logs/tv-clock-component.txt, tv-tristate-wrong.txt, src/content/circuits/circ-test-vectors-tristate.json.
Evidence: lab17…/logs/tv-clock-component.txt, tv-tristate-wrong.txt, src/content/circuits/circ-test-vectors-tristate.json.
F105 The Test Vector window in 5.0.0 (Simulate → Test Vector…, Linux lab, T-TV-04 in part)
The window opens empty with "Passed: 0 Failed: 0" and "Selection is empty."; its buttons are Load Vector, Run, Stop, Reset and Close Window. Load Vector opens a file chooser filtered to "Logisim-evolution Test Vector (*.txt)". Choosing a file runs it at once: our passing vector gave "Passed: 8 Failed: 0"; our failing vector gave "Passed: 7 Failed: 1" with the failing row listed first and its S cell shaded red. Each row has Show and Set buttons, a Status (pass or fail), <set>, <seq> (shown as comb for a combinational row) and one column per pin. The 41-row counter vector gave "Passed: 41 Failed: 0" with <set> 1 and <seq> 1 to 41; pin values are shown in hex (d, e, f). Not tried: Show, Set, hover text on a red cell, Run and Reset buttons, the effect on the canvas. Evidence: lab17-2026-11-12-test-vectors/screenshots/test-vector-window-*.png.
Evidence: lab17-2026-11-12-test-vectors/screenshots/test-vector-window-*.png.
F106 Classic Logisim 2.7.1 has no test vector option (T-TV-04, headless)
java -jar logisim-generic-2.7.1.jar -help lists -accents, -clearprops, -empty, -gates, -help, -load, -locale, -nosplash, -plain, -sub, -template, -tty, -version and nothing for test vectors; the jar contains no class whose name includes TestVector (0 matches). Evidence: lab17…/logs/classic-help.txt.
Evidence: lab17…/logs/classic-help.txt.
F107 Test-vector parsing, measured on 140 + 21 single-purpose files (`lab17…/datasets/tv-battery.json`, `tv-battery2.json`, made by `lab/tv_probe.py` and `lab/tv_probe2.py`; 5.0.0, Linux lab; T-TV-04 and T-ERR-08 in part)
Each file went through -w main on a circuit with input pins A[4], C, W[8] and an output pin Y[4]. Load errors print Error loading test vector: plus the text; pin problems print Error preparing test vector: Column X has no matching pin or … has width 3 but pin has width 4. Rules we measured: a value with exactly as many characters as the column is binary (0101 in 4 bits; a 2 in a 1-bit column gives "Unexpected character '2'"); 0x, 0o and 0b prefixes are lower case only (0X5, 0B101, 0O7 give "Unexpected character"); a prefix with no digits gives "expected digits"; hex, octal and binary values are checked by value, so 0x00F and 0b101 fit a 4-bit column and 0x1F does not; any other value is signed decimal (4 bits: -8 to 7; 15, 8, 101 and +3 are rejected); underscores are ignored (01_01 is binary); x is a don't-care bit inside binary, hex and octal values (1x01, 0xx5, xxxx) and a lone x is accepted only in a 1-bit column; <DC> and <float> are accepted in any case on inputs and outputs. The "Too many bits" message ends did you mean A[5]?? (needed signed bits, or 4 per hex digit, 3 per octal digit) and, for hex and octal, adds "Remember that 0x means hex and each hex digit is 4 bits" (or the octal wording). Header: A[, [4], A [4] and A[4]x give "bad spec"; A[0], A[65], A[x], A[-1] give "bad width"; A[04] is width 4; two columns with the same name are accepted; a row with the wrong number of values gives "too many values" or "not enough values", except that a row may leave out trailing <set> and <seq> values. <set> and <seq> match in any case and any position; set 0 with seq 1, set 1 with seq 0, a decreasing set, a repeated seq in a set and a non-decimal set value are all rejected with the <Set>/<Seq> texts in src/lib/tv/index.ts. An empty file or one with only comments gives "TestVector format error: empty file"; a header and no rows runs and prints Passed: 0, Failed: 0; CRLF, tabs, comments after values, blank lines and a missing last newline are fine; a byte-order mark is NOT stripped and the first column then matches no pin. A Clock component with no label is named <clk> in the header (its width must be 1) or left out. The checker in src/lib/tv/index.ts agrees with all 161 cases (npm run test).
F108 Command-line errors and exit codes on 5.0.0 (`lab17-2026-11-12-test-vectors/logs/cli-*.txt`, Linux lab, official jar; T-CLI-04 in part)
--help and --version exit 0 (--version prints Logisim-evolution v5.0.0, the project URL, a build line and the Java VM line). An option value or option name that 5.0.0 rejects exits with code 10, after an ERROR line: --tty foo gives "“--tty” requires at least one of the following: halt, speed, stats, table, tty, binary, hex, csv, tabs"; --gates foo gives "Argument for --gates option must be “ANSI” or “IEC”."; --bogus gives "Unrecognized option: …" and "Use --help for more info."; -o xx prints "Specified locale is not supported." and lists the supported locales (de, el, en, es, fr, pt, ru, it, nl, pl, zh and others); --load before the circuit gives "Invalid arguments for “--load”. Auguments should be <file> [label]." (the typo is Logisim's). Runs that start but cannot do what was asked exit 255: --tty tty on a circuit with no TTY or Keyboard component prints "No TTY or Keyboard component was found."; --save on a circuit with no RAM, after the run halted, prints "No RAM was found for the “--save” option."; --toplevel-circuit nosuch throws a NullPointerException (F92). --toplevel-circuit fa on our 4-bit adder file printed the truth table of the subcircuit fa. The --help text of the official jar lists 18 options (the earlier count of 19 in F01 was a miscount) and matches the earlier lab log except for quote characters. Not run: -u, -s, -m, --clear-prefs, --save on a circuit with RAM.
F109 FPGA window and boards without hardware (`lab18-2026-11-12-fpga/`, Linux lab, 5.0.0; T-FPGA-01 and T-FPGA-04 in part)
The FPGA menu has two items: FPGA Board Editor and Synthesize & Download…. The Synthesize & Download window has Clock settings (Frequency 1.0 Hz, Divider value 1), Annotation method (default "Label only the components without a label or with an invalid label", Annotate button), Action method (Toplevel, an action list, Execute), a Target board list (BASYS2 first) with a board picture, a Settings button, a button "Select Xilinx's software" (for a Xilinx board), a progress bar (Idle) and tabs Infos, Warnings, Errors, Console. With no vendor software chosen, the action list held one entry: "Generate HDL only". Pressing Execute on the unmapped full adder ran the netlist and DRC steps (Infos 1 to 7, the board's pins, buttons and LEDs) and then opened a mapping window with lists "Unmapped Components" (/A#0, /B#0, /Cin#0, /Cout#0, /S#0) and "Mapped Components" and buttons including Load Map, Save Map, Cancel and Done; the window is larger than a 1280×800 screen. File → Preferences → FPGA Commander Settings has Workspace location, "Hardware description language used for FPGA Commander" (VHDL by default), "Use upper case for VHDL keywords", an External FPGA Board list with Add a board and Remove selected board, two DRC suppress boxes and colour settings; it has no folder fields for Vivado or Quartus. For all 31 boards in the jar, --test-fpga … HDLONLY on the unmapped full adder reached the same stop (exit 255); the resources each board lists are in boards.json (BASYS3: 51 pins, 21 buttons, 28 LEDs; TERASIC_DE10_LITE: 19 pins, 2 buttons, 7 port-IO groups, 1 DIP switch, 1 LED array, 6 seven-segment displays). Not run: a mapped file, the Software tab of Preferences (the tab did not repaint under Xvfb), the Board Editor, any vendor tool, any board.
F110 Hex Digit Display glyph shapes in 5.0.0 (`lab19-2026-11-12-7seg-tool/screenshots/hex-digit-glyphs.png`, `lab/circgen/build_hexglyphs.py`, Linux lab)
Driven by constants 6, 7, 9 and 1, the display drew 6 with its top bar (segments a, c, d, e, f, g), 7 as a, b, c only (no f), 9 as a, b, c, f, g only (no bottom segment d) and 1 as b, c. These are the shapes the 7-segment decoder tool uses by default. The tool's generated files were run in 5.0.0: the ROM decoder by word and the gate decoder by segment, for eight settings (hex, BCD blank, BCD don't care, with tails, active low inverted, active low kept, reversed bit order, a custom list), all 16 rows each, 0 failures (scripts/qa_seg.mjs). Not checked: the active attribute's effect on the drawn display (the file loads; no shot), multi-digit displays.
F111 LDV-8, an 8-bit single-cycle CPU, built and run in 5.0.0 (`lab/circgen/build_cpu.py`, `lab/ldv8.py` reference model, `scripts/qa_cpu.py`, `lab20-2026-11-12-cpu/logs/`; Linux lab; T-PROJ-cpu)
The CPU has a program counter, a 256 by 12 program ROM labelled prog, a 16 by 12 control ROM labelled ctrl, an 8-bit ALU (add, subtract, and, or, xor, shift left, shift right, pass B), accumulator, 4-bit flags register, output register and a 256-byte RAM. Four milestone circuits passed sequential or combinational test vectors (program counter 39 rows, fetch 28, datapath 55, control unit 22). The whole CPU run with --tty table printed one row per clock cycle (columns out, pc, acc) and stopped by itself at the halt pin; the output equalled the reference model's on every row for the countdown (24 rows, 23 instructions), sum (86 rows, 85 instructions, final output 55) and Fibonacci (118 rows, 117 instructions, final output 144) programs, with each program loaded by --tty table circ-8-bit-cpu-ldv8.circ --load <image> prog. A --load placed before the circuit printed "Invalid arguments for “--load”. Auguments should be <file> [label]." and exited 10. A RAM left at its default (synchronous read) gave an old value on the cycle after a store: in the datapath test LDA read 0 instead of the stored 4; setting the RAM attribute asyncread to true (the XML name; "Asynchronous read:" in the window) fixed it. --tty speed on the countdown circuit printed 5000 Hz (45 ticks in 9 milliseconds); that run is too short to call a speed. Not tested: the circuit in the GUI (no step shots), a gated-clock mistake, timing diagram capture, FPGA export, performance on other machines.
F112 Exporting VHDL and Verilog from a circuit in 5.0.0 (`lab21-2026-11-12-hdl/`, Linux lab; T-HDL-02 in part)
HDL export is part of the FPGA window: with the action "Generate HDL only" nothing needs a vendor tool, but every top-level pin, button and LED has to be mapped to a board resource first. In the mapping window the circuit's components are listed under Unmapped Components; selecting one and double-clicking a highlighted spot on the board picture moves it to Mapped Components (the picture is larger than a 1600 px screen: the lab needed a 4200 x 3200 virtual display to reach the Done button). Saving the project stores the map as a <boardmap boardname="BASYS2"> element with one <mc key="/A" map="168,286"/> line per pin (key = pin label with a slash, map = x,y of the board spot). With a saved map --test-fpga file.circ main BASYS2 HDLONLY runs headless and exits 0; the same command without a map exits 255 (F51). Output goes to ~/logisim_evolution_workspace/<project name>/<circuit name>/: VHDL gives vhdl/circuit/main_entity.vhd and main_behavior.vhd, vhdl/gates/ (AND_GATE, OR_GATE, XOR_GATE_ONEHOT as entity and behavior pairs), vhdl/toplevel/logisimTopLevelShell_*.vhd, plus for a Xilinx board ucf/XilinxConstraints.ucf and scripts/ (XilinxScript.cmd, XilinxVHDLList.prj, XilinxDownload); Verilog gives one .v per module under verilog/circuit, verilog/gates, verilog/toplevel. The language comes from the Java preference hdlType (VHDL by default, set in File > Preferences > FPGA Commander Settings in the window). The full adder's entity is main with ports A, B, Cin in and Cout, S out (std_logic); a 4-bit counter driven by a Clock component gets an extra input logisimClockTree0 : std_logic_vector(4 downto 0) and support files vhdl/base/ (LogisimClockComponent, logisimTickGenerator, synthesizedClockGenerator) and vhdl/memory/LogisimCounter_*.vhd; the four one-bit output pins Q0 to Q3 became four one-bit entity ports. Not run: compiling or simulating the generated files (no tool in the lab), the Windows GUI path.
F113 TTL chips behave like their datasheet function tables in 5.0.0 (`lab22-2026-11-12-ttl/`, Linux lab; T-COMP-14 in part)
Each chip has the standard DIP pin numbering as its port layout (pins 1 to N/2 along the bottom row, N down to N/2+1 along the top; the Vcc and Gnd pins are not ports by default). 7400: all 256 input combinations give the four NAND outputs. 74161: 70 clocked rows pass (asynchronous clear, synchronous load with LOAD low, hold when ENP or ENT is low, carry output RCO high only at 15 with ENT high, wrap 15 to 0). 7447: digits 0 to 9 draw 6 without the top segment, 7 as a, b, c and 9 without the bottom segment, outputs are active low, lamp test (LT low) lights all seven, BI low blanks all, RBI low blanks only a zero. Two 7447s in a ripple-blanking cascade (RBO of the high digit on RBI of the low digit) blank a leading zero and show it when the high digit is not zero; 4 of 4 rows pass in 5.0.0 and 0 of 4 in 4.1.0, where pin 4 (BI/RBO) reads U (undefined) and never drives the next chip. The 7447 BI/RBO pin is a bidirectional port. Not run: the other chips.
F114 74181 ALU in 5.0.0 uses active-high data and gives all 32 documented function-table results (`lab22-2026-11-12-ttl/`, Linux lab; T-COMP-14 in part)
Across all 16,384 combinations of S (16), M (2), Cn (2), A (16) and B (16) the four function outputs match the active-high function table in every row: with M high they are the 16 logic functions, with M low arithmetic with the carry added when Cn is low (S = 1001 gives A + B, S = 0110 gives A - B - 1 plus the carry). The A=B output is open collector: it floats (reads U) when the result is 15 and is 0 otherwise. The ripple carry output Cn+4 (pin 16) is high when there is no carry out, for both the addition and the subtraction modes (512 of 512 rows each). Chip pins named with an overbar on a datasheet (A0 to B3, Cn) are used as plain active-high inputs here.
F115 TTL chips with the attribute "Enable Vcc and Gnd ports" need power (`lab22-2026-11-12-ttl/`, Linux lab; T-COMP-14 in part)
The attribute is stored as VccGndPorts. Turning it on adds two input ports to the chip, Gnd (the last bottom-row pin) and Vcc (pin 1 of the top row, the first pin at the top left). On a 7400 with both driven from input pins, Vcc = 1 and Gnd = 0 gives the normal NAND outputs; Vcc = 0, or Gnd = 1, or both swapped, make all four outputs U (undefined). With the attribute off (the default) no power connection exists and the chip works as is.
F116 Keyboard, TTY and LED matrix in 5.0.0 (`lab23-2026-11-12-io/`, Linux lab; T-COMP-13 in part)
The TTY has four ports, in this order in the measured list: clear (an input at the bottom right), clock, write enable and a 7-bit data input; its attributes are Rows (8), Columns (32), Trigger (rising edge or falling edge), Color and Background. The Keyboard has clear, clock, read enable, an "available" output and a 7-bit data output (buffer length 32 by default, trigger rising or falling edge). In a ROM-driven test (Clock, 4-bit counter, 16 x 7-bit ROM holding Hello, newline Logisim, TTY data input, write enable tied high, halt pin on the counter's carry) --tty tty,halt prints the characters on standard output one per rising clock edge, in ROM order: Hello,, a line break, Logisim and then the ROM's zero word as a NUL byte, and ends with the halt message; the word at address 15 is not written because the halt pin fires first (address 0 to 14 are printed). With the Keyboard's "available" output wired to the TTY write enable and to its own read enable, and both clocks on one Clock component, ticks switched on (Ctrl+K), clicking the keyboard in the GUI and typing the three characters h, i and an exclamation mark printed the same three characters in the TTY. The LED matrix (DotMatrix, defaults 5 columns by 7 rows, input format Columns, on colour green, light persistence 0 ticks) takes one 7-bit input per column when the format is Columns; with the five constants 0x7e, 0x11, 0x11, 0x11, 0x7e bit 0 is the bottom row and bit 6 the top row. The RGB Video component's colour models are 888 RGB (24 bit, default), 555, 565, 444, 8-colour RGB, Atari 2600, XTerm16, XTerm256, Grayscale (4 bit) and VGA256; its resolutions include 128x128 (default), 256x256, 320x240, 640x480, 960x540, 1024x768, 1280x720, 1920x1080 and Custom; its six ports are three 1-bit inputs, two 7-bit inputs and one 24-bit input. The Joystick has two 4-bit outputs (bit width 2 to 5), the Button has one 1-bit output (logic level "active on press" or "passive") and the DIP switch has 8 one-bit outputs by default (attribute "Number of Switch"). A wire that is not horizontal or vertical (a diagonal wire in a generated file) made the 5.0.0 window spin at about 240 % CPU while loading and never paint; it is not a case that arises from drawing in the window. Not run: pixels on RGB Video, poking the joystick, button and DIP switch, the 2.7.1 comparison.
F117 Export Image in 5.0.0 (`lab24-2026-11-12-export/`, Linux lab; T-GUI-10 in part)
File > Export Image… opens a dialog with a Circuits list (the open circuits), Image Format (PNG, GIF, JPEG, TikZ, SVG), a Scale Factor slider and a Printer View check box (on by default), then OK opens a file chooser titled by the format's file type (PNG Files (*.png), JPEG Files (*.jpeg, *.jpg), and so on) with an Export button. The scale slider runs from 13 % to 800 % on a logarithmic track (100 % in the middle). On the full adder: PNG at 100 % is 658 x 436 px (9,390 bytes) and at 200 % 1316 x 872 px (24,007 bytes); GIF 4,329 and 11,802 bytes at the same sizes; JPEG 22,202 and 57,804 bytes. SVG (viewBox 0 0 658 436) and TikZ files are identical at 100 % and 200 %: the scale factor only affects the bitmap formats. With Printer View on the PNG has two colours (black on white; each pin shows its bit width, x1, instead of its value, and labels are black); with it off it has five (blue labels and the green pin value 0 are drawn). File > Print… first opens Print Parameters (Circuits, Header with the default %n (%p of %P), Rotate To Fit and Printer View, the last two ticked by default); pressing OK in the lab container showed "No print service found." because no printer or PDF service exists there. Dark theme (File > Preferences > Window > Look and feel, list: Metal, Nimbus, CDE/Motif, GTK+, FlatLaf Light, FlatLaf Dark, FlatLaf IntelliJ (default), FlatLaf Darcula, FlatLaf macOS Light, FlatLaf macOS Dark; choosing FlatLaf Dark also set the Editor theme to Dark and darkened the canvas at once): a PNG exported with Printer View on was unchanged (white and black only, same as the light theme); with Printer View off the PNG had the dark canvas colour (43, 43, 43) behind white lines and a blue label colour, so dark-theme colours do leak into exports when Printer View is off. Classic 2.7.1 (Export Image dialog: Circuits, Image Format PNG, GIF and JPEG only, Scale Factor 13 % to 800 % on the same logarithmic slider, Printer View ticked by default; on the classic version of the full adder: PNG 611 x 431 px 8,159 bytes at 100 % and 1222 x 862 px 20,707 bytes at 200 %, GIF 3,617 and 9,611 bytes, JPEG 19,404 and 50,060 bytes). Not run: printing to a real PDF printer.
F118 Loading, merging and exporting circuits in 5.0.0 (`lab25-2026-11-12-libraries/`, Linux lab; T-FILE-07 in part)
Project > Load Library has three items: Built-in Library… (a submenu), Logisim-evolution Library… and JAR Library…. Choosing Logisim-evolution Library… opens a file chooser for Logisim project (*.circ) files; the chosen file appears in the explorer tree as a folder named after the file (here components) holding its circuits (fadd), the project is marked modified, and saving writes a relative path, <lib desc="file#components.circ" name="8"/>, with no copy of the circuit. If that file is moved, opening the project shows "The required library file 'components.circ' is missing. Please select the file from the following dialog." followed by a file chooser; a --tty table run of such a file printed nothing and was still waiting when our 60-second timeout killed it. File > Merge… (Ctrl+M) opens a file chooser (the current file name is pre-filled), then a dialog "Select circuit(s) to merge into the project:" with the circuits of the chosen file in a list, a checked box "Include dependencies" and the line "Total to merge: 1 selected circuit(s)". While a library with a circuit of the same name was loaded, OK gave the error "Circuit 'fadd' cannot be merged as the original project already contains a tool/circuit with the same name in loaded library 'components'" with the advice to unload the library or rename the sheet. After Project > Unload Libraries… (a list dialog, select the library, OK) the same merge put fadd into the project as an ordinary circuit; the saved file has <circuit name="fadd"> and no file# library line. Export Circuit is in the right-click menu of a circuit in the explorer (Edit Circuit Layout, Edit Circuit Appearance, Analyze Circuit, Get Circuit Statistics, Export Circuit, Set As Main Circuit, Remove Circuit), not in the Project menu: it opens a save chooser (default name <circuit>.circ), writes a file whose main circuit is that circuit, and shows "Circuit successfully exported to <file>"; for a circuit without dependencies no dependency dialog appeared. Not run: copy and paste between windows, JAR libraries, the project bundle, automatic loading.
F119 A VHDL Entity component in 5.0.0, without an external simulator (`lab21-2026-11-12-hdl/`, Linux lab; T-HDL-01 in part)
Project > Add VHDL Entity… asks "VHDL Entity Name:" and opens an editor in the main pane. The new entity starts from a template with the ports clock and val (std_logic_vector(3 DOWNTO 0)) in, max and cpt (4 bits) out, and an ARCHITECTURE TypeArchitecture; the editor has three buttons above the text, the first of which opens a file chooser filtered to VHDL files (*.vhd, *.vhdl). We replaced the template by importing a 2-input XOR entity (ports a, b, y). The third button (a check mark) stayed greyed out and did nothing when clicked. In the explorer the entity has its own icon; placed in a circuit its Properties show "FPGA supported: Supported" (green), VHDL Entity Name, Label ("Required for HDL", amber), Label Font, Label Visible and Facing. The placed block kept the template's four ports until the project was saved and reopened, after which it showed a, b and y. The saved file holds the code in a <vhdl appearance="logisim_evolution" name="xor2"> element. The Simulate menu has "VHDL Simulation Enabled" (unticked) and "Restart VHDL simulator". Ticking the first opened a folder chooser ("Folder name:", start folder the home directory), which we cancelled; afterwards a "VHDL simulator log" panel (empty) appeared, the canvas showed the red message "VHDL simulation is not running. Enable it and check Qu…" (the text is cut off at the edge of the pane) and the component output stayed undefined. So without a simulator the entity is placed and saved but not simulated. Not run: pointing the folder chooser at Questa or ModelSim, simulating, the validate button with a simulator.
F120 A traffic light controller as a Moore state machine, verified by sequential test vectors (`lab/circgen/build_fsm.py`, `src/content/circuits/circ-traffic-light-*`, Linux lab, 5.0.0; T-PROJ-fsm in part)
Two D flip-flops (S1, S0) with Clear tied to reset, a 3-bit Counter (Maximum Value 7, Action On Overflow set to Stay at value, Load driven by the state-change signal with data 0, Clear tied to reset), D1 = S1 XOR (S0 AND T2) and D0 = (S0 AND NOT T2) OR (NOT S0 AND T5 AND (S1 OR car)), where T2 is the timer at least 1 and T5 the timer at least 4. The 77-row vector (set 1: reset, 8 idle cycles, one car, S1 for 2, S2 for 5, S3 for 2, S0 held for 6 more; set 2: car from reset, S0 for exactly 5 cycles) passed in full (Passed: 77, Failed: 0), and so did a 31-row vector for the timer alone (count, synchronous load, saturation at 7). The same controller with the timer's asynchronous Clear input driven by the state-change signal and its Load unused passed 43 rows and failed 34: from vector row 20, the first clock edge after the car arrives, the state stayed at 00 where 01 was expected. A 3-bit Counter has its output and carry ports at x+180, not x+190 (F44): a generated file that used the 4-bit geometry showed UUU on the output. Not run: the intersection panel with lights and a button, a tick frequency for it, a recording.
F121 A 24-hour digital clock from three Counters and a ROM decoder, run for a full day (`lab/circgen/build_dclock.py`, `src/content/circuits/circ-digital-clock-*`, Linux lab, 5.0.0; T-PROJ-clock in part)
Seconds and minutes are 6-bit Counters (Maximum Value 59), hours a 5-bit Counter (Maximum Value 23), all with Action On Overflow set to wrap, one Clock component, and enables chained: minutes count when the seconds carry output is 1, hours when the seconds and minutes carry outputs are both 1 (the carry output is 1 while the value equals the maximum, F43). With a halt pin on the AND of the three carry outputs, --tty table printed 86,400 lines in about 2 seconds and stopped by itself, from 0 0000, 00 0000, 00 0000 to 1 0111, 11 1011, 11 1011 (hours, minutes, seconds in binary), and the output matched a reference model line for line (same SHA-256). A 64-word, 16-bit ROM holding the seven-segment patterns of two decimal digits (units in bits 0 to 6, tens in bits 8 to 14; 0 = 3F, 1 = 06, 2 = 5B, 3 = 4F, 4 = 66, 5 = 6D, 6 = 7D, 7 = 07, 8 = 7F, 9 = 6F) passed a 64-row vector (address 0 gives 0x3f3f, 23 gives 0x5b4f, 59 gives 0x6d6f). The whole clock (counters, three ROMs, splitters and six 7-segment displays, with the three ROM words as output pins) printed 86,400 lines whose ROM-word columns matched the model on every line. A ripple clock, with the minutes counter clocked from the seconds carry output and the hours counter from the minutes carry, differed from the model at line 60: the minutes advanced one tick early (00 0001 with seconds still 11 1011), and the run ended after 82,740 lines instead of 86,400. Counters of 4 bits and wider have their output port at x+190; 2 and 3 bits at x+180 (measured). Not run: the clock in the GUI at a real tick rate, the set buttons, the stopwatch, the blinking colon, the Real-Time Clock component.
F122 A minimal single-cycle RV32I core in 5.0.0, run on two programs (`lab/circgen/build_rv.py`, `src/content/circuits/circ-mips-risc-v-cpu-rv32mini-*`, Linux lab; T-PROJ-riscv in part)
The core supports add, sub, and, or, slt, addi, lw, sw and beq. It has a 32-bit PC Register, an Adder for PC + 4, a 256-word by 32-bit instruction ROM labelled imem (address = PC bits 9 to 2), a Splitter that cuts the instruction into fields, three immediate formats (I, S and B) built with Splitters and sign-extended with a Bit Extender, a 128-word control ROM addressed by the opcode (reg_we, alu_src, mem_we, mem_to_reg, branch, is_r, store), a 64-word ALU-control ROM addressed by {is_r, branch, funct3, funct7 bit 30}, 31 Registers for x1 to x31 (x0 is a constant 0) with a 5-bit Decoder (Include Enable?) for the write enables and two 32-input Multiplexers for the read ports, a 32-bit Adder, Subtractor, AND, OR and a signed Comparator for slt feeding an 8-input Multiplexer, a 256-word RAM with asynchronous read, a Comparator for beq and a Multiplexer for the next PC. The run ends when the instruction at the PC is 0x00000063 (beq x0, x0, 0) or 0x00000000 (halt pin). Program sum (1 + ... + 10 in a0, stored and loaded into a1) printed 12 rows of a0 and a1 with --tty table and ended with 55 and 55; program logic printed 5 rows and ended with a0 = 9 and a1 = 0xFFFFFFFE (and, or, sub, slt both ways, sw, lw); both outputs equal the Python reference model line for line (--tty table prints a row only when a printed value changes). --tty table <file> --load <image> imem with the logic image on the sum file printed the logic rows, so a v3.0 hex words plain image loads into the ROM labelled imem. A Register created without its Data Bits attribute is 8 bits wide and silently turns a 32-bit design into U values; with the clock placed on top of a constant the registers never saw an edge and --tty table printed one row and then ran without printing. No reset pin: registers and the PC start at 0. The repository survey (T-K-233/RISC-V-Single-Cycle-CPU, meiniKi/RV32I_SC_Logisim, RayZh-hs/Logisim-RISCV, yuxincs/MIPS-CPU: all MIT) is metadata from the GitHub search API only; we did not download or open any of their files. Not run: the built-in RV32IM component and assembler, any community project in 5.0.0, a pipelined design.
F123 74138, 74194 and 74245 chips in 5.0.0 (`lab22-2026-11-12-ttl/`, Linux lab; T-COMP-14 in part)
74138: all 64 combinations of the three address pins (1 to 3), the two active-low enables (4, 5) and the active-high enable (6) gave the active-low decoder table on pins 15 to 9 and 7 (Y0 to Y7). 74194: 15 clocked rows passed (parallel load with S1 S0 = 11, hold with 00, shift right with 01 taking pin 2 into QA, shift left with 10 taking pin 7 into QD, and an asynchronous clear on pin 1 while the clock was high). 74245: with DIR (pin 1) high and OE (pin 19) low the B pins (18 to 11) followed the A pins (2 to 9), and with DIR low the A pins followed the B pins, for four byte values each; with OE high the receiving side floated, in both directions. The A and B sides of the chip are bidirectional ports, driven in the tests by input pins on the sending side only.
F124 JAR libraries, project bundles and paste between windows in 5.0.0 (`lab25-2026-11-12-libraries/`, Linux lab; T-FILE-07 in part)
JAR library: Project > Load Library > JAR Library… opens a chooser filtered to Java Archive (*.jar). We built a one-class library (jar/DemoLib.java, a Library subclass with one tool, manifest line Library-Class: DemoLib): it loaded and appeared as a folder with the library's own display name, and saving wrote <lib desc="jar#demolib.jar#DemoLib" name="8"/> (relative path, then class). A first version whose only tool was the built-in Constant was refused with "Library contains following tool present in the workspace: CONSTANT.". A JAR without the manifest line made Logisim ask "Class Name:"; our attempt to type the name (lowercase only, because our key driver cannot send capitals) loaded nothing and showed no error. When the project had been opened from a relative path on the command line (logisim-evolution jj.circ) and a JAR library was loaded, saving raised a NullPointerException ("currentDirectory is null") in the library manager and left a 0-byte file; with an absolute path the save worked. Project bundle: File > Export project bundle… (Ctrl+Shift+E) asks for a .lsebdl file name and then a metadata form (project name, authors, keywords, description). The bundle is a zip holding the main circuit, a library/ folder with the library .circ files it uses, and manifest.xml (Logisim-evolution version, the main file); the library line inside was rewritten to file#./library/components.circ. File > Extract and open project bundle… asks for the bundle and then a destination folder, writes the files there and opens the project with the library loaded in a new window. Paste between windows: after File > Extract and open the session had two windows; selecting both pins in one (Ctrl+A, Ctrl+C) and pasting (Ctrl+V) into the other produced "Pin x 2" attached to the pointer and marked the target project modified. --substitute: with -s components.circ alt.circ before or after the --tty table file arguments, relative or absolute, our run stayed at the missing-library prompt and never produced output. Not run: pasting a circuit that contains subcircuit instances, the paste conflict dialog, automatic library loading at start-up.
F125 Poking the Button, Joystick and DIP switch and writing a pixel on RGB Video in 5.0.0 (`lab23-2026-11-12-io/`, Linux lab, mouse held with a Robot class; T-COMP-13 in part)
Button: the output is 0; pressing and holding the mouse on it with the Poke tool made the output 1 (wire turned green), and releasing returned it to 0 (momentary, with the default Logic level "active on press"). Joystick: both outputs are 4 bits wide and read 1000 (8) at rest; pressing toward the top left gave small values on both (about 2) and pressing left of the centre gave a small x (about 3) with y near the middle (about 7); the stick returned to the centre on release. DIP switch: clicking a switch toggled it and it stayed in position (output 1 until clicked again); the component showed the numbers 1 to 8. RGB Video (888 RGB, 128 x 128, scale 2): with reset 0, write enable 1, X = 10, Y = 10, colour 0xFF0000 and a Clock with ticks on (Ctrl+K), a single red pixel appeared near the top left of the screen; the six ports in order are reset (0,0), clock, write enable, X (7 bits), Y (7 bits) and colour (24 bits). Not run: the other colour models, Custom resolution, the cursor, the Matrix Keypad, the classic 2.7.1 versions of Button and Joystick.
F126 "Show the internal structure" on a TTL chip in 5.0.0 (`lab22-2026-11-12-ttl/screenshots/`, Linux lab; T-COMP-14 in part)
In the Properties panel the 7400 lists FPGA supported (Supported), Facing, Enable Vcc and Gnd ports, Show the internal structure and Label; the structure attribute is a Yes or No choice (default No) stored as ShowInternalStructure. With it on, the DIP outline is drawn open: the four NAND gates appear inside with the Vcc and GND corners labelled and a pin marker at each of the 14 pins; with it off the chip is a plain black body. The pin markers are drawn in different colours that follow the signal values.
F127 Four open-source CPU projects opened in 5.0.0 (`src/content/projects/cpu-survey.json`, Linux lab, shallow clones on 12 Nov 2026; T-PROJ-riscv in part)
All four repositories state the MIT licence and none of their .circ files references a JAR library. meiniKi/RV32I_SC_Logisim (file saved by 3.7.2, last commit 2023-05-17), T-K-233/RISC-V-Single-Cycle-CPU (file saved by 2.14.6, last commit 2025-02-05), yuxincs/MIPS-CPU (2.7.1 format, last commit 2022-07-17, README: Evolution not supported) and RayZh-hs/Logisim-RISCV (3.9.0 format, last commit 2025-01-04, README: experimental subset). Each main circuit loaded without a crash in --tty table mode in 5.0.0; the 2.7.1-format MIPS file printed the compatibility-mode warning and, in the window, a compatibility prompt before the sheet appeared; the other three opened without one. Opened in the window, the RISC-V single-cycle projects (meiniKi, T-K-233) changed state when ticks were switched on (Ctrl+K); the RayZh files opened as separate ALU and control-unit circuits and we did not run them. We loaded no program and checked no result, so none is verified to run its program in 5.0.0. The meiniKi README builds its demo with a RISC-V toolchain and loads the image through the ROM's context menu; we did not.
F128 Exported HDL checked with free tools (`lab21-2026-11-12-hdl/logs/`, Linux lab; T-HDL-01 in part)
Verilog: Yosys elaborated the full adder export and an eight-row evaluation matched the truth table; the 4-bit counter synthesised without errors (yosys-*.txt). VHDL: vhdl_lang 0.88.0 with the standard libraries analysed the full adder (mapped to BASYS2) and the XOR2 entity with no diagnostics, and the counter with four warnings (unused signals s_logisimNet0 to 3) and no errors (vhdl_lang-*.txt). Not covered: simulation of the VHDL, Vivado, Quartus, GHDL, Icarus.
F129 The intersection panel, headless and in the window (`lab26-2026-11-12-panel/`, `src/content/circuits/circ-traffic-light-panel*.circ`, Linux lab, 5.0.0; T-PROJ-fsm in part)
The panel is the traffic_fsm controller used as a subcircuit, a Clock, reset and car pins, six LEDs with matching output pins and a 4-bit tick counter whose carry is the halt pin. --tty table prints a row only when the outputs change: with the car pin at 0 one row (main green) and then halt after 16 ticks; with the car fixed at 1 five rows, main green, main yellow, side green, side yellow, main green (both pass in verify_circuits.py). In the window, with Ticks Enabled at the default tick frequency, one Clock cycle took about 2 s (Clock high for one tick, low for one). With car 0 the lamps stayed in S0 for the 8 s watched. After a click on the car pin the lamps stepped S1 3.7 s, S2 9.9 to 10.1 s, S3 4.6 s (4 s expected within the sample spacing), S0 10.0 s, S1 3.8 s, S2 10.1 s, which is 2, 5, 2 and 5 clock cycles as in F120 (logs/gui-run.txt, sampled from screen captures about once a second). A label with a space on a LED was renamed by the window to a name with a hash suffix, so the file uses labels with underscores. Not covered: tick frequencies other than the default, a recording, a second car arriving during S1 to S3.
F130 The 24-hour clock in the window at two tick frequencies (`lab27-2026-11-12-clock-window/logs/window-ss-samples.txt`, Linux lab, 5.0.0; T-PROJ-clock in part)
Simulate > Auto-Tick Frequency lists 0.25 Hz up to 2048 kHz, and 1.0 Hz is checked on a fresh start. With Auto-Tick Enabled (Ctrl+K) at 1.0 Hz the seconds Counter gained one count about every 2 s (0x15 to 0x20 in 21 s), because the Clock component needs two ticks, high then low, for one rising edge. After choosing 2.0 Hz it gained one count about every second (0x30 to 0x39 in 9.7 s) and wrapped from 0x3B to 0x00. So the Clock component's own period is two ticks, and a clock circuit that counts rising edges needs a tick frequency of 2 Hz for real-time seconds. Not covered: the displays were not read as digits in the window (the verification layout has tunnel labels over the displays), the minutes and hours at tick rate, tick frequencies above 2 Hz.
F131 A clock with run, reset, set buttons and a colon, and a stopwatch, verified by sequential test vectors (`lab/circgen/build_dclock_ctrl.py`, `src/content/circuits/circ-digital-clock-{controls,stopwatch}.*`, Linux lab, 5.0.0; T-PROJ-clock in part)
Controls: Counter Enable pins carry the run input, the minutes and hours enables are the carry gated by run ORed with a set button, reset drives Clear, and colon is clk AND run. 425 rows pass, covering reset, three seconds, a pause, set minutes twice and set hours once while paused, 120 ticks across a minute boundary, 23 hour presses to a day wrap, 60 minute presses to a wrap, and an asynchronous reset. Stopwatch: mod-100, mod-60, mod-60 Counters chained by gated carries; 12,219 rows pass (205 ticks, pause, 5,900 ticks across the minute carry, reset). A test vector column named like a Counter's own label (here hh, mm, ss) gave "Column hh has no matching pin", so the Counters were labelled cnt_* and the output pins kept the short names. Changing one expected value in the vector made the run report one failure. Not covered: a lap register, displays for the stopwatch, hours in the stopwatch.
F132 Poking the Matrix Keypad in 5.0.0 (`lab23-2026-11-12-io/circuits/keypad-poke-panel.circ`, `lab/circgen/build_keypad.py`, Linux lab, mouse held with a Robot class; T-COMP-13 in part)
The component has four inputs on its bottom edge and four outputs on its right edge. With the mouse held on a key, the input of that key's row is connected to the output of its column: the bottom inputs are the keypad rows (left to right = top to bottom) and the right outputs are the columns (top to bottom = left to right). Measured: key 1, input 1 = 1 gave output 1 = 1 (0 with all inputs 0); key 2 gave output 2 = 1; key A gave output 4 = 1; key 4 with input 1 = 1 and input 2 = 0 gave output 1 = 0; with only input 2 = 1, key 4 gave output 1 = 1, key 5 gave output 2 = 1 and key 1 gave output 1 = 0. With no key held all four outputs read U (undefined). Not covered: Pmod KYPD mode, two keys at once.
F133 Poking the Button and Joystick in classic 2.7.1 (`lab23-2026-11-12-io/circuits/classic-io-poke-panel.circ`, `lab/circgen/build_classic_io.py`, Linux lab, official `logisim-generic-2.7.1.jar`; T-COMP-13 in part)
The file saved as 2.7.1 opens in 2.7.1. Button: output 0 at rest, 1 while the mouse is held on it, 0 after release. Joystick, 4-bit outputs: 1000 and 1000 at rest; with the knob dragged diagonally about 8 pixels toward the top left, 0100 and 0100; toward the bottom right, 1100 and 1100; back to 1000 and 1000 on release. Only diagonal pulls were tried, so the two axes were not separated. Not covered: other Bit Width values, the Button's Logic Level attribute, the TTY and Keyboard in the window (the classic -tty tty run hung earlier).
F134 The built-in RISC V IM component, and our two programs checked against an assembler (`lab28-2026-11-12-riscv/`, Linux lab, 5.0.0; T-PROJ-riscv in part)
Library "System On a Chip": Risc V IM simulator, SoC bus simulator and Memory simulator placed in one circuit show a register file x0 to x31 with ABI names, a pc field, an execution trace panel, and for the CPU a Reset vector (default 0x0), Number of IRQ lines (0), PLIC base address (0xc000000), a Sim state field (Halted) with a Start control. The CPU and the memory both show a red "Not connected to a bus" until their Connected bus attribute is set (click, choose the bus by its label in a dialog); then the label turns green and shows the bus name. The file stores this as SocBusIdentifier on the bus and SocBusSelection on the CPU and memory (same value). The memory defaults to start address 0x0 and byte address width 10 (1 kB). The jar's own text lists the processor menu items Read ELF file, Open assembler, Show loaded program and Show CPU state; with Xvfb and Robot right-clicks (which opened the project tree menu) the canvas menu never appeared, so we did not load a program or run the CPU. Simulate > Assembly viewer opens an empty "Register" window (no labelled registers). Separately, the nine and eleven instruction words of our rv32mini sum and logic programs were reproduced exactly by LLVM 18 llvm-mc (riscv32, +m) from the same assembly, so the hand encodings are correct (logs/llvm-mc-check.txt). Not covered: running any program on the built-in core, ELF loading, the M instructions, the memory contents window.
F135 `--substitute` works when the first name is written as the file stores it (`lab25-2026-11-12-libraries/substitute/`, `logs/substitute.txt`, Linux lab, 5.0.0; T-FILE-07 in part)
A main file that uses a library file#libA.circ (circuit adder, Y = NOT A) with a constant 1 printed Y = 0 in --tty table. With --substitute libA.circ libB.circ (or -s, before or after the file name), where libB.circ holds an adder with Y = A, it printed Y = 1. The second name can be a path (sub/libB.circ worked). An absolute first name (/tmp/subst/libA.circ) did nothing: the first name must match the library name written in the file. With libA.circ moved away, the run waited at the missing-library prompt and printed nothing, which explains the earlier failures in F124, where the original library had been moved. Not covered: a substitution for a library inside a library, more than one --substitute pair, the GUI.
F136 Why we did not run a program on the T-K-233 RV32I project (Linux lab, 5.0.0, shallow clone of 12 Nov 2026)
Its main circuit has no Pin components (the two "Pin" entries in the file are toolbar tools), so --tty table ran, exited 0 and printed nothing. The instruction memory is a RAM labelled IMEM, 24 address bits by 32 data bits, with no stored contents, so a program has to be loaded into it. The repository also ships a Logisim JAR; we did not use it. LLVM 18 llvm-mc can build RV32I images, but we did not load one into IMEM or read the registers in the window. No result is claimed for any community project.
Test cases (135)
| Test | What | Machines | Status | Findings |
|---|---|---|---|---|
| T-LAB-01 | Local scripted lab (lab/run_local.py, 40 cases) | lab-lnx | done | F01–F23 |
| T-LAB-02 | CI install lab (lab/ci/install-lab.yml), all official assets | ci-* | done (2 runs) | F24–F36 |
| T-LAB-03 | Re-run T-LAB-01 + T-LAB-02 on every new release, diff with previous run | lab-lnx, ci-* | todo (per release) | none |
| T-LAB-04 | Evidence integrity on every build: each evidence row and finding shown on P62 links to an existing file under /evidence/ | build CI | todo | none |
| T-LAB-05 | Privacy audit on every build: headless browser uses each tool with a sample file; no network request may carry input; localStorage keys listed (automated form of T-TOOL-9) | build CI | todo | none |
| T-INST-W01 | MSI install on Windows 11, default options, record every screen (SmartScreen, UAC, wizard pages) | ci-w25 / dev | todo | (F25 lab) |
| T-INST-W02 | SmartScreen "Windows protected your PC" on the unsigned MSI after a browser download: exact text, "More info → Run anyway" | ci-w25 / dev, ci-w22 | todo | none |
| T-INST-W03 | Portable ZIP: extract, run, where preferences go, run from USB stick | ci-w25 / dev | todo | none |
| T-INST-W04 | Windows on ARM: aarch64 MSI vs x64 MSI under emulation | ci-warm (optional) | done (CI) | F25, F27 |
| T-INST-W05 | winget install/upgrade/uninstall logisim-evolution.logisim-evolution; Chocolatey and Scoop install | ci-w25 / dev | done (CI) | F56, F57 |
| T-INST-W06 | Jar route on Windows: install Temurin 21, double-click jar, "open with" problems (WinRAR/7-Zip association), java -jar | ci-w25 / dev | partial (jar route via Chocolatey/Scoop needs Java) | F57, F20 |
| T-INST-W07 | Upgrade 4.1.0 → 5.0.0 over the top: settings kept? two entries in Apps? | ci-w25 / dev | todo | none |
| T-INST-W08 | Uninstall: Apps & features, leftovers (registry prefs, recent files), --clear-prefs | ci-w25 / dev | done (CI) | F26 |
| T-INST-W09 | .circ association: double-click a .circ, browser downloads saved as .circ (U46) | ci-w25 / dev | todo | (F25) |
| T-INST-W10 | Windows 10 smoke test (install, open, simulate) | ci-w22 | done (Windows Server 2022 stand-in) | F61 |
| T-INST-M01 | DMG install on Apple Silicon: drag to Applications, first launch, every Gatekeeper dialog (macOS 15 and current) | ci-mac-arm | done (Gatekeeper dialog captured, macOS 15.8) | F29, F62, F64 |
| T-INST-M02 | Gatekeeper overrides: right-click → Open, Privacy & Security → Open Anyway, xattr -dr com.apple.quarantine; which works on which macOS | ci-mac-arm | partial: dialog has only Done/Move to Trash (F64); override steps cite Apple | F64 |
| T-INST-M03 | Intel DMG on an Intel Mac and the arm64 DMG under Rosetta; confirm the 5.1.0dev jar in the Intel DMG (F30) | ci-mac-x64 (or ci-ci-mac-x64) | done (CI, 3 runs) | F30 |
| T-INST-M04 | MacPorts install; Homebrew cask state | ci-mac-arm | done for Homebrew (CI); MacPorts not tested | F31 |
| T-INST-M05 | Jar route on macOS: Temurin 21 .pkg, double-click jar, file access to Desktop/Documents (U06) | ci-mac-arm | todo | none |
| T-INST-M06 | Classic 2.7.1 on current macOS: "legacy Java SE 6" prompt from the old .app, the jar on Java 21 | ci-mac-arm | done (2.7.1 jar on Java 17 Windows, Java 21 macOS) | F58, F64 |
| T-INST-L01 | Official .deb on Ubuntu 24.04 desktop: install, menu entry, .circ double-click, remove | ci-ubu | done (CI) | F33 |
| T-INST-L02 | Flatpak com.github.reds.LogisimEvolution (version, sandbox file access, HiDPI) | ci-ubu, ci-fedora | done (CI) | F52 |
| T-INST-L03 | apt install logisim (classic 2.7.1) and running both side by side | ci-ubu | done (lab + CI) | F22 |
| T-INST-L04 | RPM on Fedora (Wayland); hash the .rpm | ci-fedora | done (CI; removal in container failed) | F54 |
| T-INST-L05 | AUR logisim-evolution-bin on Arch/Manjaro | ci-arch | done (CI) | F55, F60 |
| T-INST-L06 | Snap 3.8.0: install and show what is outdated | ci-ubu | done (CI) | F34, F53 |
| T-INST-L07 | Tiling WM / Wayland blank window (_JAVA_AWT_WM_NONREPARENTING=1), HiDPI (GDK_SCALE, -Dsun.java2d.uiScale) | ci-arch, ci-fedora | todo | none |
| T-INST-L08 | Jar on Linux with distro Java 21 and with Java 8 (AtkWrapper, F21) | ci-ubu | re-run | F21 |
| T-ONL-01 | Chromebook: enable Linux (Crostini), install .deb, open/save files, performance | ci-debian + web-emu | done (Debian 12 container stand-in) | F59 |
| T-ONL-02 | logisim.app in Chrome/Edge/Safari: load time, open a 2.7.1 file, open a 5.0.0 file (expected to fail), save | ci-w25 / dev, ci-debian + web-emu, web-emu | partial (desktop Chromium) | F50 |
| T-ONL-03 | iPad and Android phone: what works (logisim.app, CircuitVerse, remote desktop) | web-emu, web-emu | done (emulated) | F50, F63 |
| T-JAVA-01 | 5.0.0 jar on Java 8/17/21: exact errors | lab-lnx | done | F20 |
| T-JAVA-02 | 2.7.1 on Java 8/17/21, AtkWrapper and fix | lab-lnx | done | F21 |
| T-JAVA-03 | Windows: jar with no Java installed (what happens on double-click), with Java 8 from java.com | ci-w25 / dev | todo | none |
| T-JAVA-04 | Which Java each installer bundles (re-check per release) | ci-* | done | F27 |
| T-FILE-01 | 2.7.1-format file in 5.0.0: warning, label conversion | lab-lnx | done | F02 |
| T-FILE-02 | 5.0.0 file in 2.7.1: FPArithmetic error | lab-lnx | done | F04 |
| T-FILE-03 | Round-trip corpus: 20 real course files (CS61C, CS3410, Harvard, Toronto…) from 2.7.1, 3.8, 4.1 opened in 5.0.0: what breaks (pins, RAM, appearance) | lab-lnx + ci-w25 / dev | todo | none |
| T-FILE-04 | 5.0.0 file in 4.1.0 and 3.8.0 (backward compatibility inside Evolution) | lab-lnx | done (lab, tty): 4 files in 4.1.0 and 3.8.0; GUI and new 5.0 components not tested | F68 |
| T-FILE-05 | Holy Cross Edition and Logisim-ITA files in 5.0.0 | lab-lnx | todo | none |
| T-FILE-06 | --new-file-format conversion (needs display, dialog, does not exit) | lab-lnx | done | F18 |
| T-FILE-07 | Merge/export circuits between files (5.0.0 merge dialog), copy-paste between projects | ci-w25 / dev | partial: load library, merge, export circuit, missing library (lab25); no paste between windows, JAR, bundle | F118 |
| T-FILE-08 | Autosave/recovery: kill the app with unsaved changes, what is recoverable | ci-w25 / dev | todo | none |
| T-FILE-09 | Holy Cross Edition 5.3.1 opening files from 2.7.1, 4.1.0 and 5.0.0, and 5.0.0 opening HC files | lab-lnx | todo | none |
| T-GUI-01 | Interface tour screenshots (light and dark), Find Action (Ctrl+Shift+A / double Shift) | ci-w25 / dev, ci-mac-arm | done (lab); re-run on ci-w25/ci-mac-arm | F46, F47 |
| T-GUI-02 | Keyboard shortcuts table: verify every shortcut on Windows and macOS | ci-w25 / dev, ci-mac-arm | done (Ctrl in lab, ⌘ on macOS runner) | F46, F62 |
| T-GUI-03 | Grey wires until Reset Simulation: with classic files (F03) and with a file saved by 5.0.0 | lab-lnx, ci-w25 / dev | done (lab, Windows and macOS desktops) | F45, F49, F64 |
| T-GUI-04 | HiDPI: 150 %/200 % Windows scaling, 4K, macOS Retina; fixes (-Dsun.java2d.uiScale, Preferences → Window) | ci-w25 / dev, ci-fedora | partial (lab): -Dsun.java2d.uiScale=2 observed on Xvfb; real HiDPI screens not tested | F71 |
| T-GUI-05 | Dark mode / FlatLaf themes in 5.0.0, how circuits look, export in dark mode | ci-w25 / dev | todo | none |
| T-GUI-06 | Language switch (-o and Preferences), gate shapes ANSI/IEC (-g) | ci-w25 / dev | partial (languages, gate shape) | F47 |
| T-GUI-07 | Subcircuits: create, pin order/facing, Edit Circuit Appearance, main circuit, naming rules, nested depth | ci-w25 / dev | todo | none |
| T-GUI-08 | Combinational Analysis: build from table/expression, limits (inputs/outputs), K-map view, Build Circuit options (2-input gates, NAND only) | ci-w25 / dev | partial (analysis window, tunnel message) | F48 |
| T-ANA-01 | Combinational Analysis expression syntax in 5.0.0 and 2.7.1: accepted operators (~ ! ' * & && + \ | \ | \ | ^`, implicit AND, NOT/AND/OR/XOR words, Unicode), name rules, input/output limits (20/256 from source), K-map limit (6), every analyser error text with screenshot |
| T-GUI-09 | Timing diagram (chronogram) and Logging: select signals, clock-driven capture, export (image/file), log file format | ci-w25 / dev | partial (options panel) | F47 |
| T-GUI-10 | Export Image (PNG/GIF/SVG/TikZ) and Print: options, scale, dark theme, what is included | ci-w25 / dev | partial: export formats and scales (lab24); no print, no dark theme | F117 |
| T-SIM-01 | Clock: Auto-Tick on/off, frequency menu, half vs full tick, Ctrl+K/Ctrl+T, measured achieved frequency in the GUI | ci-w25 / dev | todo | none |
| T-SIM-02 | Simulation stuck: auto-propagate off, Ctrl+E/Ctrl+I, reset; what users see | ci-w25 / dev | todo | none |
| T-SIM-03 | Poke tool vs edit tool on pins; pull-down/pull-up pin behaviour change in 4.0 | ci-w25 / dev | todo | none |
| T-ERR-01 | Oscillation: NOT loop in tty | lab-lnx | done | F06 |
| T-ERR-02 | Conflict (two drivers) | lab-lnx | done | F07 |
| T-ERR-03 | Floating net (U/X, blue) | lab-lnx | done | F08 |
| T-ERR-04 | Width mismatch (orange, "Incompatible widths") | lab-lnx | done | F09 |
| T-ERR-05 | Wired showcase screenshots of all colours | lab-lnx | re-run | F03, F07–F09 |
| T-ERR-06 | Tri-state bus behaviour | lab-lnx | done | F10 |
| T-ERR-07 | "Oscillation apparent" in the GUI: exact message, where shown, what auto-propagate does; 6 real oscillation causes (SR latch without clocking, feedback through gates, clock wired to itself, RAM loops, counter feedback, subcircuit loop) with the fix for each | ci-w25 / dev | todo | none |
| T-ERR-08 | Every error/message string we can trigger (file, memory, FPGA, simulation): collect text + screenshot | lab-lnx, ci-w25 / dev | partial: source strings extracted (F73); triggered messages so far: Oscillation, Incompatible widths, label conflict dialog, compatibility dialog, FPArithmetic file error | F73, F70 |
| T-COMP-01 | Splitter 8→4+4 bit mapping | lab-lnx | done | F11 |
| T-COMP-02 | Splitter attributes (fan out, bit width in, appearance, spacing), bit extender vs splitter | ci-w25 / dev | todo | none |
| T-COMP-03 | Tunnels: labels, case sensitivity, widths, across subcircuits (they do not cross) | lab-lnx, ci-w25 / dev | todo | none |
| T-COMP-04 | Pins: input/output, three-state, pull behaviour, probe radix, constants | lab-lnx, ci-w25 / dev | todo | none |
| T-COMP-05 | Gates: input count, negation bubbles, unconnected inputs, XOR "one vs odd", controlled buffer, PLA | lab-lnx | done | F39, F40 |
| T-COMP-06 | Plexers: mux/demux/decoder/encoder/priority encoder/bit selector, select widths, enable, three-state outputs (truth tables via tty) | lab-lnx | done | F41 |
| T-COMP-07 | Arithmetic: adder/subtractor carry/borrow, multiplier signed/unsigned (new in 5.0), comparator signed vs unsigned, shifter modes | lab-lnx | done | F42 |
| T-COMP-08 | Flip-flops: D/JK/T/SR edge vs level trigger, async set/reset, initial state, latch from gates | lab-lnx, ci-w25 / dev | done (lab, 11 Nov): D/T/J-K/S-R, async preset/clear; sequences need <set>/<seq> | F65, F66 |
| T-COMP-09 | Register, shift register, register file built from registers + decoder | lab-lnx | todo | none |
| T-COMP-10 | Counter: max value, action on overflow (wrap/stay/continue/load), up/down, load, carry; mod-10 counter | lab-lnx | done (overflow modes) | F43 |
| T-COMP-11 | RAM: data interface options, separate load/store, the 5.0 opt-in output-enable mode, clear, initial content | lab-lnx, ci-w25 / dev | done (lab): load/store/clock, output hold, floating until first read; the 5.0 output-enable option not yet tested | F67 |
| T-COMP-12 | 7-segment display, hex digit display: pin order, common anode/cathode option, decimal point; driving from a ROM | ci-w25 / dev | todo | none |
| T-COMP-13 | Keyboard, TTY, LED matrix, RGB video, joystick, buttons/DIP switches | ci-w25 / dev | partial: TTY, keyboard echo, LED matrix, attributes (lab23) | F116 |
| T-COMP-14 | TTL library: 7400, 7447 cascading (5.0 fix), 74181 ALU, 74161 counter; power pins | ci-w25 / dev | partial: 7400, 7447 (+cascade), 74161, 74181, Vcc/Gnd attribute (lab22) | F113-F115 |
| T-COMP-15 | Component inventory (port probe) per version | lab-lnx | done | F23 |
| T-COMP-16 | Which components export to VHDL/Verilog and FPGA (HDL generator present), checked by exporting one instance of each | lab-lnx | todo | none |
| T-COMP-17 | Classic 2.7.1 component instances opened in 5.0.0: what each converts to (appearance, removed pins such as flip-flop Enable and RAM/ROM sel) | lab-lnx | todo | none |
| T-COMP-18 | Port names and tooltips for every component (for PinDiagram labels), extracted with the probe | lab-lnx | done | F44 |
| T-MEM-01 | ROM contents in the .circ | lab-lnx | done | F12 |
| T-MEM-02 | --load ignored by --tty table without halt | lab-lnx | done | F13 |
| T-MEM-03 | Memory image formats and failure modes via --load | lab-lnx | done | F14–F16 |
| T-MEM-04 | GUI: right-click → Load Image / Save Image / Edit Contents; which formats the dialog offers; binary and "escaped ASCII" formats; endianness | ci-w25 / dev | todo | none |
| T-MEM-05 | Every T3 output preset loads in 5.0.0 and (where the format exists) in 2.7.1 | lab-lnx | todo | none |
| T-TV-01 | Test vector pass | lab-lnx | done | F17 |
| T-TV-02 | Test vector fail, exit code 0 | lab-lnx, ci-* | done | F17 |
| T-TV-03 | Test vector headless crash | lab-lnx, ci-mac-* | done | F18 |
| T-TV-04 | GUI Test Vector window: load, red cells, Show/Set buttons, sequential <seq> columns, don't-care x, multi-bit formats | ci-w25 / dev | partial (lab, no GUI window): `<set>`/`<seq>`, `<DC>`, `<float>` verified headless | F65, F72 |
| T-TV-05 | Autograder recipe: Xvfb + -w + parse "Failed: 0"; run 30 student-style files | lab-lnx | done (30 variants; no 4.1.0-saved file) | F102 |
| T-TV-06 | -b/--test-circuit test bench: what it expects in the file, output and exit codes | lab-lnx | partial (file rules from bytecode; run hangs on Questa chooser) | F103 |
| T-CLI-01 | --help/--version | lab-lnx | done | F01 |
| T-CLI-02 | --tty formats: table, binary, hex, csv, tabs, halt, speed, stats, tty (TTY component output) | lab-lnx | todo (table/speed done) | F05, F19 |
| T-CLI-03 | Classic 2.7.1 -tty behaviour | lab-lnx | done | F05 |
| T-CLI-04 | --save RAM image, --toplevel-circuit, --substitute, -u template, --clear-prefs | lab-lnx | todo | none |
| T-CLI-05 | Launchers accept CLI options on all OSes | ci-* | done | F28 |
| T-PERF-01 | Synthetic counter benchmark 5.0.0 vs 2.7.1 | lab-lnx, ci-w25, ci-warm | done | F19 |
| T-PERF-02 | Real CPU design (our P47 CPU running a program): ticks/s per version and per OS; GUI auto-tick ceiling | ci-w25 / dev, ci-mac-arm, lab-lnx | todo | none |
| T-PERF-03 | Startup time to usable window per OS/package (cold and warm) | ci-w25 / dev, ci-mac-arm, ci-ubu | todo | none |
| T-FPGA-01 | Toolchain setup: Vivado (Basys 3) and Quartus Prime Lite (DE10-Lite) paths in Logisim preferences | ci-w25 / dev | lab-only: settings screenshot | none |
| T-FPGA-02 | Synthesize & download a counter + 7-segment design to Basys 3; record each dialog, timing, errors | lab-lnx (no board) | not possible (no board) | none |
| T-FPGA-03 | Same on DE10-Lite | lab-lnx (no board) | not possible (no board) | none |
| T-FPGA-04 | --test-fpga ... HDLONLY headless HDL generation | lab-lnx | done (needs I/O map) | F51 |
| T-HDL-01 | VHDL entity component: write, compile, simulate (VHDL simulation via Questa is optional; record what works without it) | ci-w25 / dev | partial: entity added, imported, placed, saved; not simulated (no Questa) | F119 |
| T-HDL-02 | Export VHDL/Verilog of a circuit; read the generated files | lab-lnx | partial: VHDL and Verilog export of full adder and counter (lab21); not compiled | F112 |
| T-PROJ-adder | Half adder, full adder, 4-bit ripple adder, adder-subtractor; verify with test vectors | lab-lnx + ci-w25 / dev | partial: half adder, full adder, 4-bit ripple verified (5.0.0 and classic); adder-subtractor, 8-bit, BCD, subtractors, broken-bit-order to build with P45 | F68 |
| T-PROJ-alu | 1-bit and 4-bit/8-bit ALU with flags; test vectors | lab-lnx + ci-w25 / dev | partial: 1-bit cell (64 rows), 4-bit from four cells (2,048 rows) verified, both formats; 8-bit/16-bit whole-word ALU and calculator to build with P46 | none |
| T-PROJ-cpu | 8-bit CPU (accumulator, 16 instructions), assembler output via T3, program runs (halt) | lab-lnx + ci-w25 / dev | todo | none |
| T-PROJ-fsm | Traffic light Moore FSM with counters; test vectors with sequential steps | ci-w25 / dev | partial: controller 77 rows and timer 31 rows pass, broken twin fails at row 20 (headless); no GUI run | F120 |
| T-PROJ-clock | Digital clock: mod-60/mod-24 counters, 7-segment via ROM decoder | ci-w25 / dev | partial: 86,400-line self-test (counters and full clock), 64-row decoder vector, ripple twin differs at line 60 (headless); no GUI run | F121 |
| T-PROJ-riscv | Survey and run 3 open-source RISC-V/MIPS Logisim CPUs (licence, version they need) | ci-w25 / dev | partial: own RV32I core on 2 programs (headless); 4 community repos listed from metadata, not opened | F122 |
| T-PROJ-tutorial | First-circuit tutorial followed by a non-technical tester on a fresh PC and a Mac (timed) | ci-w25 / dev, ci-mac-arm | partial: half adder and full adder built by script and verified (4 + 8 rows, 5.0.0 and classic format); non-technical-tester timing not possible (no human tester) | F68 |
| T-PROJ-classic | Every 2.7.1 variant of a project file opens and passes its built-in self-test circuit in classic 2.7.1 | lab-lnx | todo | none |
| T-PROJ-hub | Each project page's frontmatter (circuits, sizes, hashes, versions) matches its files | build CI | todo | none |
| T-SAFE-01 | Hash and VirusTotal check of every official asset and of the copies on FileHippo/Softonic/Uptodown | ci-w25 / dev | todo | (F24 hashes) |
| T-SAFE-02 | Lookalike/parasite download page audit (list in research/demand/search-landscape.md §2.5), monthly | any | todo | none |
| T-CMP-01 | Build the same 4-bit counter + 7-segment circuit in Logisim-evolution, Digital and CircuitVerse: time, features, export | ci-w25 / dev | todo | none |
| T-CMP-02 | Open a Logisim .circ in Digital (import) and CircuitVerse (import): what survives | ci-w25 / dev | todo | none |
| T-CMP-03 | Simulation speed of the same counter design in Logisim-evolution, Digital and CircuitVerse (only if P56 adds a speed column) | ci-w25 / dev | todo | none |
| T-CMP-04 | Digital's command-line test cases: command, output, exit code on failure (compare with F17) | ci-w25 / dev, lab-lnx | todo | none |
| T-CMP-05 | CircuitVerse on Chromebook and iPad: load, build, save, offline behaviour | ci-debian + web-emu, web-emu | todo | none |
| T-TOOL-1 | Version and Download Picker | browser matrix | todo | none |
| T-TOOL-2 | .circ Viewer and Inspector (corpus of 40 files from 2.7.1 to 5.0.0) | browser matrix | todo | none |
| T-TOOL-3 | Memory Image Generator (outputs load in Logisim: T-MEM-05) | browser matrix + lab-lnx | todo | none |
| T-TOOL-4 | Wire Colour Explainer | browser matrix | todo | none |
| T-TOOL-5 | 7-Segment Decoder Generator (ROM image + truth table + .circ load and display digits) | browser matrix + ci-w25 / dev | todo | none |
| T-TOOL-6 | Test Vector Builder and Checker (generated vectors pass in Logisim) | browser matrix + lab-lnx | todo | none |
| T-TOOL-7 | Splitter Visualiser (matches Logisim's mapping for 20 configurations) | browser matrix + lab-lnx | todo | none |
| T-TOOL-8 | Truth Table to Circuit (generated .circ opens and its tty table equals the input table, 50 random functions) | browser matrix + lab-lnx | todo | none |
| T-TOOL-9 | Privacy check for every tool page: no network requests while using it (HAR in Chrome and Safari), localStorage keys listed, CSP blocks a forced fetch | browser matrix | todo | none |
The status column is copied from our test catalog as it was planned. Findings F65 onward record later runs, including the circuit and tool checks, which the catalog does not yet mark as done.
Report a wrong result
If a finding or a page is wrong, tell us on the contact page. We list changes on the corrections page. Read about us on About logisim.dev.