Lab Plan Overview

The Lab plan is designed for research groups: a PI and their students, a shared lab, or a small multi-disciplinary team working on the same study. It adds a full team workspace with shared studies, files, dataset manifests, tasks, pages, and activity records.

What Is Included

The Lab plan includes everything in the Researcher plan plus:

Model Export & Edge Deployment

• BCILattice formats on every plan, pipelines, workflows and trained models (.bltm) export on Free, Researcher and Lab alike
• Open-format export is Enterprise, a PyTorch .pt2 program that takes raw signal, with the study's filters and Analysis steps built in, is part of the Enterprise contract, not the Lab plan
• Edge deployment is the BCINexus Edge add-on, priced per device, and is not part of the Lab plan either

Team Workspace

• Dataset manifests, register shared dataset metadata and local verification details for team members
• Shared studies, create studies that multiple team members can contribute to
• Shared pipeline library, your lab's private collection of pipelines and paradigms
• Shared study visibility, review team studies and assigned work in one place
• Activity feed, timestamped log of all dataset uploads, study changes, and experiment completions

Data Integrity

Data integrity is critical for reproducible BCI research. The Lab plan adds SHA-256 checksum verification for all shared datasets:

1. When a dataset is registered or shared, store checksum or manifest details where available
2. When a team member uses a shared dataset, verify the local copy against the recorded manifest
3. If verification differs, treat the local copy as changed or invalid until reviewed
4. Keep dataset details visible for manual review and reproducibility checks

This helps teams confirm that experiments are run against the intended dataset version.

Collaboration Features

• Team activity, review workspace events and assigned work
• Pipeline sharing, share compiled MLFlow pipelines directly with team members
• Study sharing, move selected study artifacts into the team workspace
• Tasks and pages, coordinate follow-up work and lab notes inside the team workspace
• Notifications, track invitations, requests, and relevant team activity

Two People, One Study, Different Places

A lab does not take turns with a study, it divides it: someone curates the recordings while someone else builds the classifier, often in different cities. A shared study is therefore synced in parts rather than as one file, and the parts are the ones you already work in.

What this means in practice:

• Edits to different parts never collide. If you change preprocessing while a colleague changes the ML pipeline, both syncs succeed and neither of you is asked to choose.
• Only a genuine overlap is raised, and only for the parts that actually overlap. You can take your colleague's version of the one part that clashed while keeping everything else you did.
• Claim a part to say it's yours. Open Who's doing what on a team study to see which parts are taken, by whom, and which are still unclaimed. Claims are advisory: they warn, they never lock anyone out, and an owner or admin can release one when somebody is away.
• Presence shows where people are, not just that they are online, so “editing” only interrupts you when it means the part you are in.
• Tasks are filed against the same parts. Assigning the ML pipeline to someone can claim it for them in the same action, and a task can be moved through assigned → in progress → blocked → done so the rest of the team can see work is under way.

Recorded data still stays on the machine that recorded it unless you explicitly sync or publish it. Section syncing changes how a shared study's configuration is merged, not what leaves your computer.

Lab vs. Researcher vs. Free

Setting Up Your Lab Workspace

1. Upgrade to the Lab plan at bcinexus.xyz/pricing
2. In BCILattice, go to Teams in the left sidebar
3. Click Create Workspace, give it a name (e.g., "Neural Plasticity Lab")
4. Click Invite Members, enter email addresses of up to 4 additional team members
5. Invited members accept via email and connect to the workspace from their own BCILattice installation
6. Register or share team data from the Teams workspace using the available dataset/file actions
7. Team members can now access the shared dataset from their own machines

Team Roles & Permissions

Roles are assigned per member in Teams → Workspace Settings → Members. Owners can change any member's role at any time.

Upgrading from Researcher

Upgrading from Researcher to Lab takes effect immediately:

• You are charged the pro-rated difference for the current billing cycle
• Existing personal studies and cloud artifacts remain under their original workspace unless you explicitly move or share them
• You can start inviting team members right away
• Move or share selected work into the team workspace when it should use team quota and permissions

Downgrading from Lab to Researcher: takes effect at the end of the current billing cycle. Export or move team data before downgrade according to the active billing and workspace policy.

Questions & Contact