Troubleshooting & Compatibility
Review supported FCS inputs, browser requirements, limitations, and common recovery steps.
12. Tips, Limitations, and Troubleshooting
| Topic | Notes |
|---|---|
| Supported FCS input | PhaseFinder supports FCS 2.0/3.0/3.1 list-mode files with numeric F, D, or byte-aligned exact-range I DATA in declared little- or big-endian order. DNA modeling requires linear $PnE=0,0, unit/absent $PnG, one dataset, primary TEXT only, and no declared spillover involving the DNA channel. The channel selector shows this status; parser errors link to this supported-input summary, while unsupported transforms, compensation, modes, widths, supplemental TEXT, and chained datasets are blocked with a specific error. |
| Parameter labels | Channels shown in PhaseFinder are extracted from each parameter's $PnS label when present, falling back to $PnN, and ultimately to a generated P<n> label when needed. |
| No backend | Files are read entirely by browser APIs; nothing is uploaded anywhere. |
| State lives in memory | Reloading the page clears everything that isn't saved to a session file first. |
| Network dependency | None at runtime: D3 is vendored locally, and the DJF numeric implementation is repository-native. |
| Folder re-linking on session load | Chromium browsers remember the FCS folder between sessions; Firefox and Safari will ask you to pick it again each time. |
| Supported browsers | Chrome/Edge 111+, Firefox 121+, Safari 16.2+, Chrome for Android 111+, and iOS Safari 16.2+. Current stable releases are recommended. OPFS and persistent folder access are optional; without them, analysis still works in memory and session reconnect uses manual file selection. |