Skip to content

FARIS 0.1.1

Choose a tag to compare

@Connoravila1 Connoravila1 released this 06 Oct 13:33

The same demo study and results as 0.1.0. What changes is how it is
distributed: a smaller download split in two, a launcher with no Python, and
Windows and macOS downloads.

Changed

  • The download is split in two. The app download, one per platform
    (FARIS-0.1.1-linux-x86_64.tar.gz, FARIS-0.1.1-windows-x86_64.zip,
    FARIS-0.1.1-macos-aarch64.tar.gz for Apple silicon and
    FARIS-0.1.1-macos-x86_64.tar.gz for Intel Macs), holds everything the app
    needs to open the whole study. The Linux app download is about 35 MB. The
    optional FARIS-0.1.1-evidence.tar.gz, about 78 MB and the same for every
    platform, adds the Avila Core receipts and is what verify.sh checks. 0.1.0
    was one 112 MB archive. SHA256SUMS covers every file. Each archive unpacks
    to a folder FARIS-0.1.1/; unpack the evidence pack into the same place so
    its files merge.
  • Python is no longer needed to open the study, and launch.sh is gone. Double-click
    bin/faris-app (bin\faris-app.exe on Windows), or run it from a terminal.
    It finds the study beside its bin folder, checks the SHA-256 of every file
    it needs and opens the four recorded arrangements and the sweep.
    faris-app --package DIR opens a package elsewhere. If a check fails, the app
    opens with nothing loaded and says why and what to do (download again and
    check SHA256SUMS).
  • Windows and macOS downloads. The programs are not signed. Windows SmartScreen
    may warn: choose More info, then Run anyway. On macOS the programs are neither
    signed nor notarized: after unpacking, run
    xattr -dr com.apple.quarantine FARIS-0.1.1 once in Terminal, or open
    bin/faris-app and allow it under System Settings, Privacy & Security, Open
    Anyway. Windows and macOS builds are new in 0.1.1; report problems on GitHub
    issues. Every platform's programs are built by CI from the release commit;
    the study evidence was recorded on Linux on the reference laptop. The Linux
    programs need glibc 2.35 or newer: Ubuntu 22.04 or later, Debian 12 or later. The app also needs a desktop session (X11 or Wayland) with libxkbcommon and a Vulkan or OpenGL driver, which desktop installs include. On a minimal install, add libxkbcommon-x11-0 (Debian, Ubuntu) or libxkbcommon-x11 (Fedora); without it the app stops at launch with a panic in xkbcommon-dl.
  • With the evidence pack, the app unpacks the Core evidence (823 MB) into a
    private temporary folder while it runs and deletes it on exit, so it needs
    about 0.9 GB of free temporary space. Without it, everything works except
    the saved receipts: the Evidence step says "Core receipts not included", why,
    and the next step.
  • verify.sh needs Linux, python3 and the evidence pack, and about 2 GB of
    temporary space; it checks the exact amount first. The Windows and macOS
    downloads are checked by the app itself at launch.
  • Generated runs go to a per-user folder outside the package:
    $XDG_STATE_HOME/faris/recorded-demo-runs/<folder> on Linux (~/.local/state
    if unset), ~/Library/Application Support/FARIS/recorded-demo-runs/<folder>
    on macOS and %LOCALAPPDATA%\FARIS\recorded-demo-runs\<folder> on Windows.
    --runs-directory overrides it and must be outside the package. The tour
    marker tour-completed is in $XDG_CONFIG_HOME/faris or ~/.config/faris on
    Linux, ~/Library/Application Support/FARIS on macOS and %APPDATA%\FARIS
    on Windows.

What to do. Nothing, if you stay on 0.1.0: a 0.1.0 package keeps its own
launch.sh and verifier and still works as before. To use 0.1.1, download the
app archive for your platform and, if you want the Core receipts, the evidence
pack. A .faris file made with 0.1.0 opens in 0.1.1 unchanged.

Added

These are for development and for the maintenance study that follows 0.1.1.
They change nothing in the recorded study.

  • faris reactor run --activation-spectra fispact-709 also tallies each
    component's neutron spectrum in the 709 groups ACTINV uses. Without the
    option, requests, tallies and recorded results are unchanged, and recorded
    0.1 runs still inspect and load.
  • Operating assumptions accept replacement_durations_s on a service limit:
    the k-th replacement of that component takes the k-th duration, and later
    ones fall back to replacement_duration_s.
  • faris-app --check-package REPORT.json opens a package without a window,
    reopens its saved studies, loads its inputs and writes a JSON report. The
    release checks use it on each platform.

Fixed

  • The 0.1.0 Linux programs needed glibc 2.43, so they ran only on the newest
    distributions. 0.1.1's are built on Ubuntu 22.04 and need 2.35 or newer.
  • The tour states the real history counts: 10 million per port case and 30
    million per port-free control.
  • The export button's hover no longer gives a page count.
  • Saved Core evidence now waits up to 10 minutes for unpacking, and says why if
    it gives up.
  • On Windows the app opens without a console window.
  • On Windows the faris history commands no longer refuse to run.

Downloads

  • FARIS-0.1.1-linux-x86_64.tar.gz: the app for Linux x86_64. Unpack it and run FARIS-0.1.1/bin/faris-app; it opens the whole study.
  • FARIS-0.1.1-macos-aarch64.tar.gz: the app for macOS on Apple silicon. Unpack it and run FARIS-0.1.1/bin/faris-app; it opens the whole study.
  • FARIS-0.1.1-macos-x86_64.tar.gz: the app for macOS on an Intel Mac. Unpack it and run FARIS-0.1.1/bin/faris-app; it opens the whole study.
  • FARIS-0.1.1-windows-x86_64.zip: the app for Windows x86_64. Unpack it and run FARIS-0.1.1\bin\faris-app.exe; it opens the whole study.
  • FARIS-0.1.1-evidence.tar.gz: the Core receipts the app's Evidence step shows, and the files verify.sh checks (the same bytes for every platform). Optional: unpack it into the same place as the app archive, so both fill FARIS-0.1.1/. The app needs temporary space for the receipts while it runs; the package README gives the amount.
  • SHA256SUMS: check the downloads before unpacking. Linux: sha256sum -c SHA256SUMS --ignore-missing. macOS: shasum -a 256 -c SHA256SUMS --ignore-missing. Windows: in PowerShell, Get-FileHash FARIS-0.1.1-windows-x86_64.zip must print the SHA-256 on that file's line.

SHA-256 of FARIS-0.1.1-linux-x86_64.tar.gz: f0914ebf55632c6b495c32eab42eb8b5848ce2af256da3be15d6985a2ea22e6e

SHA-256 of FARIS-0.1.1-evidence.tar.gz: 3deed8eec56313cd2ee99538e149702ebcfd88d1be02bac753e7128739f6be38

SHA-256 of FARIS-0.1.1-windows-x86_64.zip: 4fb0be3d9355bfef917aa1a0e8deef7e44e94910018d53e8a1dd4cb38c8d941c

SHA-256 of FARIS-0.1.1-macos-aarch64.tar.gz: d0fb3364f9e327103e4878b5c92325d1cfd80a7cbdb78a28f165770613d8cd9b

SHA-256 of FARIS-0.1.1-macos-x86_64.tar.gz: e17b9356bb9e86121f4a012e673dfd2c01f2e1b71e91ca21b740810f88184c33