[MaximeBICMTL]

Summary

This PR modernizes the electrophysiology browser in preparation for MEG support in LORIS. This PR is purely focused on front-end changes in the electrophysiology browser and can be reviewed and tested as a standalone. Changes that depend on changes to the LORIS backend or imaging pipelines are submitted separatedly in the appropriate repositories.

Scope

This PR aims to only touch the modules/electrophysiology_browser/jsx directory. Changes outside of this directory are few and easy to review, due to renames and (desirable) changes in the test or build system.

First commit is #11211, see that PR (now closed in favor of this one) for more details.

Testing

Before testing that PR, you need to regerate the chunk_pb.js file since protobuf has been updated, do so with npm install or make dev. protoc needs to be installed to generate the file (just as before).

As before, building the full electrophysiology browser (npm run build) front-end can be done with either the EEG_VIS_ENABLED=true environment or database configuration.

Known issues

This PR has a few known issues, which I believe are minor and outside of the scope of this PR.

This PR reuses the Panel from the LORIS jsx, which has two issues:

• Titles can only be string rather than any ReactNode, which creates a propTypes warning.
• The initCollapsed prop does not work, which makes panels always uncollapsed originally.

The HED Dataset Manager is still a weird button that looks like it is in the navbar but actually is not and is tied to an acquisition with absolute positioning. This looks even weirder with the new navbar but is a bug that is already present and can be fixed separately.

The navbar does not go to the real bottom of the page, this is due to the LORIS footer, which has weird CSS. The principled fix would be to fix the footer CSS or implement a reusable sidebar architecture in LORIS, not something that can be done without extending the scope of this (massive) PR.

Features

General

• Add Three.js, React Three Fiber, and Drei dependencies (see details in montage section).
• Extend the content security policy for Three.js blob scripts and workers.
• Move some of the state management from Redux to React contexts.
• Add reusable low-pass and high-pass filter controls.
• Add reusable multi-select dropdown and mutable dependency-cache components.

Series Viewer

• Add adaptive channel scaling based on visible samples.
• Store signals as Float32Array rather than vanilla Javascript arrays.

Navbar

• This PR adds an actually usable navbar to the module, which allows to easily navigate a session acquisition and the electrophysiology browser main features.

(3D) Montage

• Isolate the Montage into its own directory.
• Extract the Channels Editor and 3D Montage into their own files.
• Add sensor categories (this PR only fetches EEG electrodes, fetching of MEG sensors will come in other PRs)
• Refactor the 3D Sensor Map to use Three,js+Three.js Fiber (Canvas) rather than VisX (SVG) for display.
• Use Three.js Drei orbital controls rather than homemade solution for 3D controls.
• Add dropdown to select which types of sensors to visualize.

Architecture

State management

State management has been completely revamped, dropping the old overengineered Redux/Ramba-based Frankensteinish abomination that no one actually understood (sorry not mincing my words lol, no hard feelings though). State management now uses standard React state and context hooks.

File organization has been revamped to group files by feature rather than layer~ish organization.

Dependencies

Removed: redux, react-redux, redux-actions, redux-logger,
redux-observable, redux-thunk, rxjs, ramda, react-compound-slider,
d3-3d, resize-observer-polyfill, tslib, @types/react-redux.

Added: three, @react-three/fiber and @react-three/drei (the 3D sensor map
is now rendered with WebGL instead of d3-3d SVG projections).

Upgraded: google-protobuf 3 → 4.

Static tests

This PR enables full strict type checking for the electrophysiology browser.
It also removes the ESLint ignore that was used for much of the module files. The only override that is kept for the module is a 100-character line limit.

Other notes

The translation updates have been AI-generated.