Skip to content

FARIS 0.2.0

Latest

Choose a tag to compare

@Connoravila1 Connoravila1 released this 08 Oct 18:33
· 361 commits to main since this release

Replacement outages computed from activation. FARIS can now work out how long
each replacement takes from the decay heat of the parts around the replaced
component, rerun the 30-year history with those outages, and compare every
design's downtime, availability and lifetime electricity with the fixed-duration
model. The demo study and its recorded results are otherwise the same as 0.1.1.

Added

  • faris maintenance run computes replacement outages for every design in a
    designs file (faris-maintenance-designs/v0.1) from a maintenance
    assumptions file (faris-maintenance-assumptions/v0.1): per replacement
    class, the governing components, the work time and a threshold q*, either
    calibrated on one design's first replacement or given in W/m³. Each outage is
    the cooldown until the governing components' decay heat per volume falls
    below q*, plus the work time; the history is rerun until no outage changes by
    more than a day. It needs ACTINV, its data and Python, and writes
    faris-maintenance-result/v0.1. faris maintenance report prints a result as
    tables.
  • A Maintenance window in the desktop (top bar). It opens a result and
    shows each design's downtime, availability and lifetime net electricity under
    both models, a chart of every replacement's fixed and computed outage, and
    for each replacement which components held the cooldown up and how long they
    had been in the machine. Run… computes a result from the desktop with
    progress and cancel. --maintenance FILE opens a result at launch.
  • The package carries a recorded maintenance result for the four arrangements,
    opened from the Maintenance window, and the activation-input builder
    (tools/build_activation_inputs.py) for computing results from your own
    transport runs.

Limits

  • Decay heat governs the cooldown. Contact dose is refused as the governing
    quantity: with a threshold fixed at the first outage, the never-replaced first
    wall kept dose above it for more than a year at later replacements.
  • With a calibrated threshold, outages are relative to the calibration outage:
    FARIS shows how they differ between designs and grow over the plant's life,
    not how long they are in absolute terms.
  • Running the calculation needs your own transport runs with a 709-group
    spectrum; the packaged arrangements' spectrum runs are not in the download.

Installing

What to do. Download the app archive for your platform and, if you want the
Core receipts, the evidence pack, as for 0.1.1. A 0.1.1 package keeps working;
a .faris file made with 0.1.x opens in 0.2.0 unchanged.

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.2.0 once in Terminal,
or open bin/faris-app and allow it under System Settings, Privacy & Security,
Open Anyway. 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.

Downloads

  • FARIS-0.2.0-linux-x86_64.tar.gz: the app for Linux x86_64. Unpack it and run FARIS-0.2.0/bin/faris-app; it opens the whole study.
  • FARIS-0.2.0-macos-aarch64.tar.gz: the app for macOS on Apple silicon. Unpack it and run FARIS-0.2.0/bin/faris-app; it opens the whole study.
  • FARIS-0.2.0-macos-x86_64.tar.gz: the app for macOS on an Intel Mac. Unpack it and run FARIS-0.2.0/bin/faris-app; it opens the whole study.
  • FARIS-0.2.0-windows-x86_64.zip: the app for Windows x86_64. Unpack it and run FARIS-0.2.0\bin\faris-app.exe; it opens the whole study.
  • FARIS-0.2.0-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.2.0/. 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.2.0-windows-x86_64.zip must print the SHA-256 on that file's line.

SHA-256 of FARIS-0.2.0-linux-x86_64.tar.gz: 44f86159b0de988bd9f4ae33c75bdefbb2ca4a82b92ee1b5620e073de03692f3

SHA-256 of FARIS-0.2.0-evidence.tar.gz: f406d6329179eccdfd95fddaf7f2064413a20a32e3e3b464f30f6f1f70b5ea69

SHA-256 of FARIS-0.2.0-macos-aarch64.tar.gz: 871e1df5cf6547de576a6b7709f73c2bf946f8ef98eb132251de78600cd6e14e

SHA-256 of FARIS-0.2.0-macos-x86_64.tar.gz: 3f5809f680e5a364a53fac38a34d9ffd4d5822df2a8b764b0bc4720a53d24843

SHA-256 of FARIS-0.2.0-windows-x86_64.zip: 98b67418aaa9208fbc391837bc370d936ecdc847f0886fa57170b17e61daa3e6