Skip to content

Fix device override in from_pretrained, add MPS support#9

Open
yajur-khanna wants to merge 1 commit intofacebookresearch:mainfrom
yajur-khanna:fix/cpu-mps-device-support
Open

Fix device override in from_pretrained, add MPS support#9
yajur-khanna wants to merge 1 commit intofacebookresearch:mainfrom
yajur-khanna:fix/cpu-mps-device-support

Conversation

@yajur-khanna
Copy link
Copy Markdown

Bug Fix

The extractor device overrides in from_pretrained were applied to config
before yaml.load() reassigned it to a fresh ConfDict on line 211,
silently discarding all overrides. This caused:

AssertionError: Torch not compiled with CUDA enabled

on CPU-only systems (e.g. macOS), even when the config hardcodes device: cuda.

MPS Support

Adds MPS auto-detection for Apple Silicon. The FmriEncoder brain model
runs on MPS; neuralset feature extractors fall back to CPU since their
device field is Literal["auto", "cpu", "cuda", "accelerate"].

Changes

  • demo_utils.py: move extractor device overrides to after config YAML load
  • demo_utils.py: add torch.backends.mps.is_available() to auto-detection
  • demo_utils.py: extend extractor CPU override to cover device="mps"
  • Update docstring to document CPU extractor fallback behavior

- Move extractor device overrides to after config YAML is loaded;
  previously they were applied before yaml.load() reassigned config,
  silently discarding all overrides and causing AssertionError on
  CPU-only systems ("Torch not compiled with CUDA enabled").
- Add MPS auto-detection via torch.backends.mps.is_available() so
  Apple Silicon users get GPU acceleration on the FmriEncoder.
- Force neuralset feature extractors to CPU when device is mps,
  since their device field is Literal["auto","cpu","cuda","accelerate"].
- Update docstring to document the CPU extractor fallback behavior.
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Mar 29, 2026

Hi @yajur-khanna!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Mar 29, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Meta Open Source bot. label Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant