<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ForceIQ Knowledge Base</title>
    <link>https://forceiq.app/learn</link>
    <description>The reference for isometric dynamometry: rate of force development, force steadiness, limb symmetry, and the judgment calls behind each number.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 02:45:22 GMT</lastBuildDate>
    <atom:link href="https://forceiq.app/learn/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing a classic IsoForge game mode</title>
      <link>https://forceiq.app/learn/isoforge/choosing-a-classic-game-mode</link>
      <guid isPermaLink="true">https://forceiq.app/learn/isoforge/choosing-a-classic-game-mode</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <description>The four classic IsoForge modes (Hold Steady, Make Waves, Take Flight, Rapid Fire) are still available and are still the most direct way to run a single, isolated force-tracking task. This covers what each one probes, when to pick it over an Arcade game, and why the published evidence treats them as distinct rather than interchangeable.</description>
    </item>
    <item>
      <title>Choosing an IsoForge Arcade game</title>
      <link>https://forceiq.app/learn/isoforge/choosing-an-arcade-game</link>
      <guid isPermaLink="true">https://forceiq.app/learn/isoforge/choosing-an-arcade-game</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <description>The IsoForge Arcade has four games (Ember Drift, Forge Runner, Spark Pulse, Cinder Updraft). Each one asks for a different shape of force over time, reports a different outcome, and adapts its own difficulty to keep the patient in a productive success band. This covers what each game trains, which assessment deficit points to which game, and what the adaptive difficulty costs you.</description>
    </item>
    <item>
      <title>The Athletic Shoulder (ASH) Test</title>
      <link>https://forceiq.app/learn/getting-started/ash-test</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/ash-test</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <description>Isometric shoulder strength in three prone positions — I, Y and T — profiling force across the range rather than at a single angle. What the positions are, why the range matters, and how the preset runs.</description>
    </item>
    <item>
      <title>The Focal Joint Cooling Test (FJCT)</title>
      <link>https://forceiq.app/learn/getting-started/focal-joint-cooling-test</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/focal-joint-cooling-test</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <description>Maximal trials, focal cooling applied to the joint, then a reassessment of the same limb. Force rising afterwards is consistent with arthrogenic muscle inhibition releasing. What the test asks, and how ForceIQ reports it.</description>
    </item>
    <item>
      <title>Sampling rate, RTD reliability, and what the badge actually means</title>
      <link>https://forceiq.app/learn/data-quality/sampling-rate-considerations</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/sampling-rate-considerations</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Sample rate matters for RTD and almost nothing else. The platform flags low, moderate, and high RTD reliability based on how many samples actually land inside the 0 to 75 ms window. This walks through what the three tiers look like on real signals, which devices land in which tier, and when a low-confidence badge should change your read.</description>
    </item>
    <item>
      <title>When a device won't pair or stays disconnected</title>
      <link>https://forceiq.app/learn/getting-started/device-pairing-troubleshooting</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/device-pairing-troubleshooting</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Troubleshooting flow for the most common BLE pairing problems (device-on-but-not-discovered, pairs-then-drops, auto-shutoff between sets). Device-agnostic guidance organized around what the symptom actually is, not which dynamometer you have.</description>
    </item>
    <item>
      <title>Taring the dynamometer and what a good baseline looks like</title>
      <link>https://forceiq.app/learn/getting-started/tare-and-baseline</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/tare-and-baseline</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Taring the device and the platform's baseline-correction step are two different operations on the same problem. This walks through what each does, why a small amount of resting pretension is actually favorable on tension-gauge dynamometers (it makes countermovement visible), and when to retare mid-session.</description>
    </item>
    <item>
      <title>Your first session</title>
      <link>https://forceiq.app/learn/getting-started/your-first-session</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/your-first-session</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Most ForceIQ sessions are captured live over Bluetooth, not uploaded from a file. Pair your device once, set up the protocol, and the metric suite is on screen the moment the contraction ends. File upload still works for offline data, but Capture is the path that produces the cleanest result with the least friction.</description>
    </item>
    <item>
      <title>Running an MVIC, and choosing the knee angle for your device</title>
      <link>https://forceiq.app/learn/getting-started/how-to-mvic</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/how-to-mvic</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
      <description>A maximal isometric contraction is only as good as its baseline. Which knee angle you test at depends on whether your dynamometer can account for limb weight. This article explains why 90 degrees is the pragmatic default on hand-held and tension-gauge devices.</description>
    </item>
    <item>
      <title>Setting up a reliable isometric knee extension assessment</title>
      <link>https://forceiq.app/learn/getting-started/isometric-knee-extension-practices</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/isometric-knee-extension-practices</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
      <description>The clinically validated protocol for measuring isometric knee extensor strength, from positioning to cueing to what the curve should look like, including why RTD wants 90 degrees on a tension-gauge device even though peak torque is anchored at 60. Get the setup right and ForceIQ inherits the rigor; get it wrong and the metrics inherit the slop.</description>
    </item>
    <item>
      <title>Inspecting and editing trials</title>
      <link>https://forceiq.app/learn/data-quality/inspecting-and-editing-trials</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/inspecting-and-editing-trials</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>How to read a captured trial, move through the trials in a session, and decide what each one needs. This is the map that ties the onset-override and exclude-or-delete workflows together, so you know which tool a given curve calls for before you reach for it.</description>
    </item>
    <item>
      <title>Browser and device support for live Capture</title>
      <link>https://forceiq.app/learn/getting-started/browser-and-device-support</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/browser-and-device-support</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>Capturing directly from a dynamometer uses Web Bluetooth, which only runs in Chromium-based browsers on desktop or Android. This article covers what works, what does not, and why, so you can set up a machine that pairs on the first try.</description>
    </item>
    <item>
      <title>Custom metrics, the outcome measures the force curve can't capture</title>
      <link>https://forceiq.app/learn/metrics/custom-metrics-and-clinical-outcomes</link>
      <guid isPermaLink="true">https://forceiq.app/learn/metrics/custom-metrics-and-clinical-outcomes</guid>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <description>Force and torque describe one slice of recovery. Hop tests, range of motion, and patient-reported outcomes describe the rest, and return-to-sport decisions hold up better when all of them sit on one timeline. How to use the Clinical Outcomes panel, which hop tests carry the most information, and where the evidence says outcome measures help and where it says they don't.</description>
    </item>
    <item>
      <title>Reading drift warnings</title>
      <link>https://forceiq.app/learn/data-quality/reading-drift-warnings</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/reading-drift-warnings</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>Two warning banners can appear on a session after the metrics compute. Pre-loaded tare warns that the strap was already loaded before the contraction began (which biases peak and shifts onset). Post-release rebound warns that the trace did not return to baseline after the release (which usually means the strap migrated under load). This walks what each banner is detecting, what it means clinically, and whether to act on it.</description>
    </item>
    <item>
      <title>Pre-test checklist</title>
      <link>https://forceiq.app/learn/getting-started/pre-test-checklist</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/pre-test-checklist</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>A condensed printable companion to the full isometric knee extension protocol. One page, scannable, what to do before the patient sits down, while you're setting up, in the cueing minute, during the trial, and between trials. Print it, post it next to the testing station, and use it as a reference rather than a memory aid.</description>
    </item>
    <item>
      <title>Translating published metrics to what ForceIQ shows</title>
      <link>https://forceiq.app/learn/getting-started/translating-published-metrics</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/translating-published-metrics</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>When a paper reports RFD at 50 ms or CV at 20% MVC or Yank in N/s, how does that map to what the platform shows on the metric tile? A practical bridge for clinicians reading the literature, with the most common units, window conventions, and normalization differences spelled out.</description>
    </item>
    <item>
      <title>Choosing the contraction type, MVIC vs RTD vs submaximal hold</title>
      <link>https://forceiq.app/learn/data-quality/choosing-a-contraction-type</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/choosing-a-contraction-type</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <description>The contraction-intent setting tells the analysis layer which metrics belong on the screen. An RTD or ballistic set has no plateau, so steadiness metrics are correctly hidden. A submaximal hold has no explosive rise, so the RTD windows are hidden. This is how to pick and why the choice changes what you see.</description>
    </item>
    <item>
      <title>Correcting the auto-detected onset</title>
      <link>https://forceiq.app/learn/data-quality/correcting-the-onset</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/correcting-the-onset</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <description>The platform's onset detection is good but not infallible. When the auto-detected onset is wrong, a single click on the chart sets it where it actually belongs and every downstream metric recomputes from the override. The original index is preserved on the session for audit.</description>
    </item>
    <item>
      <title>The steadiness reliability flag</title>
      <link>https://forceiq.app/learn/data-quality/steadiness-reliability</link>
      <guid isPermaLink="true">https://forceiq.app/learn/data-quality/steadiness-reliability</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <description>The steadiness badge fires when the platform detects that hardware quantization or transition rate is limiting how much of nRMSE / CV / Yank reflects real motor control versus the device's own resolution floor. Device-agnostic by design, and what to do when it appears.</description>
    </item>
    <item>
      <title>Preparing the patient for their first MVIC</title>
      <link>https://forceiq.app/learn/getting-started/preparing-the-patient</link>
      <guid isPermaLink="true">https://forceiq.app/learn/getting-started/preparing-the-patient</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <description>A short, plain-language script for the minute before the test starts. What the strap will feel like, what pre-loading means, what the cue is and why it matters, what happens between trials. Most first-session quality issues are explainable here, not on the chart.</description>
    </item>
  </channel>
</rss>
