GUI to register recordings in the automatic pipeline
See the instructions here. Ensure that all the information under the "System Configuration" tab is entered correctly otherwise your behavior data may not show up.
git clone git@github.com:BrainCOGS/RecordingProcessJobGUI.git --recurse-submodulesThat is the whole install. There is no conda environment to build: the app locates uv at startup, installing it if it is missing, and every python tool it shells out to declares its own dependencies.
- The parameter helpers (
read_params.py,upload_params.py) run against the repo'spyproject.toml. - The external GUIs — phy, suite2p and the IBL atlas — are standalone launchers
in
PythonScripts/carrying inline PEP 723 dependency blocks, so uv provisions each one into its own cached environment the first time that button is pressed. Expect that first launch to be slow while the environment is built; later launches reuse the cache.
If uv cannot be found or installed, the GUI still runs — the parameter helpers fall back to a MATLAB-only path, and the external GUI buttons report that uv is missing instead of failing obscurely.
The python suites declare their own dependencies inline (PEP 723), so they need no environment set up first:
uv run --script tests/test_matlab_export.py
uv run --script tests/test_open_phy_dat_path.pyThe MATLAB suites are matlab.unittest classes and run through runtests:
matlab -batch "addpath(pwd); runtests({'tests/TestBuildUvScriptCall.m','tests/TestOutputDirMatch.m'})"tests/test_jsonencodepretty.m is a plain script with bare asserts rather than
a test class, so runtests cannot collect it. Call it by name:
matlab -batch "addpath(pwd); addpath([pwd filesep 'tests']); test_jsonencodepretty"