molmospaces-resources 0.0.1__tar.gz

molmospaces_resources-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Allen Institute for AI (Ai2)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

molmospaces_resources-0.0.1/PKG-INFO

@@ -0,0 +1,139 @@
+Metadata-Version: 2.4
+Name: molmospaces_resources
+Version: 0.0.1
+Summary: Resource manager for MolmoSpaces
+Author: Allen Institute for AI (Ai2)
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/allenai/molmospaces-resources
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: datasets
+Requires-Dist: filelock
+Requires-Dist: huggingface_hub
+Requires-Dist: lmdb~=1.7.5
+Requires-Dist: requests
+Requires-Dist: tqdm>=4.65.0
+Requires-Dist: tyro
+Requires-Dist: zstandard~=0.25.0
+Dynamic: license-file
+
+# <img src="https://raw.githubusercontent.com/allenai/molmospaces-resources/main/molmospaces_resources/images/ai2_logo.png" width=22> MolmoSpaces-resources
+
+Resource manager for [MolmoSpaces](https://github.com/allenai/molmospaces). Downloads, caches, and symlinks versioned data archives from remote buckets.
+
+- Versioned, read-only download cache with symlink-based install directories
+- Eager or on-demand archive extraction with parallel downloads
+- Pluggable archive indexing for fast asset lookup
+- Fork-resilient: safe to use across multiprocessing workers
+
+## Installation
+
+```bash
+pip install molmospaces-resources
+```
+
+## Setup example
+
+Data is assumed to be served from a gated Hugging Face dataset repo, so we typically need to pass a valid token:
+
+```python
+import os
+from molmospaces_resources import HFRemoteStorage, setup_resource_manager
+
+source = HFRemoteStorage("allenai/molmospaces", repo_prefix="mujoco", token=os.environ["HF_TOKEN"])
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+)
+```
+
+Alternatively, we can use `R2RemoteStorage` for direct bucket access, including `"mujoco-thor-resources"`, `"isaac-thor-resources"`, and `"mujoco-thor-training-data"` (also available for Google Cloud Storage via `GCRemoteStorage` with `"molmospaces-isaac"`, `"molmospaces-mujoco"`, and `"molmobot-data"` buckets):
+
+```python
+from molmospaces_resources import R2RemoteStorage, setup_resource_manager
+
+source = R2RemoteStorage("mujoco-thor-resources")  # known bucket name or full URL
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+)
+```
+
+Optionally, run project-specific logic after setup via `post_setup`:
+
+```python
+def my_post_setup(manager):
+  ## Install all scenes (while skipping per-file symlinking):
+  # manager.install_all_for_data_type("scenes", skip_linking=True)
+  
+  ## Install all objects (with per-dataset symlinking):
+  # manager.install_all_for_data_type("objects")
+  pass
+
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+  post_setup=my_post_setup,
+  force_post_setup=True,  # run post_setup even if all data sources are configured
+)
+```
+
+## Logging
+
+By default, Python's logging shows `WARNING` and above, so the library will be quiet. To see detailed progress messages, either configure the root logger:
+
+```python
+import logging
+logging.basicConfig(level=logging.DEBUG)
+```
+
+or set the `molmospaces_resources` logger level explicitly:
+
+```python
+import logging
+logger = logging.getLogger("molmospaces_resources")
+logger.setLevel(logging.DEBUG)
+if not logger.handlers:
+    logger.addHandler(logging.StreamHandler())
+```
+
+## FAQ
+
+**FAQ 0\. I'm getting hard to parse errors when using the ResourceManager and I cannot resolve the issue by just erasing the involved subdirectories and the corresponding entries in the installed data manifests (`mjthor_data_type_to_source_to_versions.json`) under both install and cache dirs.**
+
+Chances are it might be easiest to just fully erase both cache and symlink dirs (see the differences between both below) and then start populating new cache and symlink dirs by just setting up the resource manager with the desired data sources and versions (e.g. as described above). Note that some data sources, like thor objects or robots, will get fully extracted during the initial setup, which takes longer than usual to complete.
+
+**FAQ 1\. What is the difference between `cache_dir` and `symlink_dir`?**
+
+The resource manager uses two separate directory trees that must not overlap:
+
+- **`cache_dir`** is the versioned download cache. Archives are extracted into a `<data_type>/<source>/<version>/` hierarchy, and multiple versions can coexist side by side. Files here are set read-only to prevent accidental modification. This directory can be safely shared across containers or workers.
+
+- **`symlink_dir`** is the user-facing install directory. It presents a flat `<data_type>/<source>/` layout with no version in the path — the version is hidden behind symlinks that point into `cache_dir`. This allows application code to use stable, version-agnostic paths while the underlying data can be upgraded by simply re-pointing the symlinks.
+
+These two directories **must resolve to different physical locations** and neither can be nested inside the other. The manager validates this at construction time and raises an error if the paths overlap.
+
+**FAQ 2\. A process hangs waiting for a lock on a shared filesystem (e.g. WekaFS, NFS).**
+
+The resource manager uses file-based locks (`.lock` files) to coordinate concurrent access to the cache and symlink directories. On local filesystems, the OS automatically releases these locks when a process dies. On shared/networked filesystems like WekaFS or NFS, if a container is destroyed without a clean shutdown (e.g. killed by the orchestrator, node crash), the lock may not be released immediately. The filesystem will typically detect the dead client eventually, but this can take a varying amount of time.
+
+If setup appears stuck, you can manually remove the stale lock file (typically in the shared cache directory):
+
+```bash
+rm /path/to/cache_dir/.lock
+```
+
+If the interrupted process was mid-install, the cache may contain partially extracted archives. The safest recovery is to delete the entire affected `<data_type>/<source>/<version>/` directory under `cache_dir`, remove the corresponding entry from the local manifest files, and re-run setup. Partial cleanup (e.g. removing individual archives) is possible but requires checking the `.complete_extract` / `.complete_links` flag files as well.
+
+In shared-cache scenarios with sufficient storage, we recommend installing all data eagerly with a single leader process and letting workers use the pre-populated cache without locks via `cache_lock=False`.
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.

molmospaces_resources-0.0.1/README.md

@@ -0,0 +1,119 @@
+# <img src="https://raw.githubusercontent.com/allenai/molmospaces-resources/main/molmospaces_resources/images/ai2_logo.png" width=22> MolmoSpaces-resources
+
+Resource manager for [MolmoSpaces](https://github.com/allenai/molmospaces). Downloads, caches, and symlinks versioned data archives from remote buckets.
+
+- Versioned, read-only download cache with symlink-based install directories
+- Eager or on-demand archive extraction with parallel downloads
+- Pluggable archive indexing for fast asset lookup
+- Fork-resilient: safe to use across multiprocessing workers
+
+## Installation
+
+```bash
+pip install molmospaces-resources
+```
+
+## Setup example
+
+Data is assumed to be served from a gated Hugging Face dataset repo, so we typically need to pass a valid token:
+
+```python
+import os
+from molmospaces_resources import HFRemoteStorage, setup_resource_manager
+
+source = HFRemoteStorage("allenai/molmospaces", repo_prefix="mujoco", token=os.environ["HF_TOKEN"])
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+)
+```
+
+Alternatively, we can use `R2RemoteStorage` for direct bucket access, including `"mujoco-thor-resources"`, `"isaac-thor-resources"`, and `"mujoco-thor-training-data"` (also available for Google Cloud Storage via `GCRemoteStorage` with `"molmospaces-isaac"`, `"molmospaces-mujoco"`, and `"molmobot-data"` buckets):
+
+```python
+from molmospaces_resources import R2RemoteStorage, setup_resource_manager
+
+source = R2RemoteStorage("mujoco-thor-resources")  # known bucket name or full URL
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+)
+```
+
+Optionally, run project-specific logic after setup via `post_setup`:
+
+```python
+def my_post_setup(manager):
+  ## Install all scenes (while skipping per-file symlinking):
+  # manager.install_all_for_data_type("scenes", skip_linking=True)
+  
+  ## Install all objects (with per-dataset symlinking):
+  # manager.install_all_for_data_type("objects")
+  pass
+
+mgr = setup_resource_manager(
+  source,
+  symlink_dir=SYMLINK_DIR,
+  versions=ASSETS_VERSIONS,
+  cache_dir=CACHE_DIR,
+  post_setup=my_post_setup,
+  force_post_setup=True,  # run post_setup even if all data sources are configured
+)
+```
+
+## Logging
+
+By default, Python's logging shows `WARNING` and above, so the library will be quiet. To see detailed progress messages, either configure the root logger:
+
+```python
+import logging
+logging.basicConfig(level=logging.DEBUG)
+```
+
+or set the `molmospaces_resources` logger level explicitly:
+
+```python
+import logging
+logger = logging.getLogger("molmospaces_resources")
+logger.setLevel(logging.DEBUG)
+if not logger.handlers:
+    logger.addHandler(logging.StreamHandler())
+```
+
+## FAQ
+
+**FAQ 0\. I'm getting hard to parse errors when using the ResourceManager and I cannot resolve the issue by just erasing the involved subdirectories and the corresponding entries in the installed data manifests (`mjthor_data_type_to_source_to_versions.json`) under both install and cache dirs.**
+
+Chances are it might be easiest to just fully erase both cache and symlink dirs (see the differences between both below) and then start populating new cache and symlink dirs by just setting up the resource manager with the desired data sources and versions (e.g. as described above). Note that some data sources, like thor objects or robots, will get fully extracted during the initial setup, which takes longer than usual to complete.
+
+**FAQ 1\. What is the difference between `cache_dir` and `symlink_dir`?**
+
+The resource manager uses two separate directory trees that must not overlap:
+
+- **`cache_dir`** is the versioned download cache. Archives are extracted into a `<data_type>/<source>/<version>/` hierarchy, and multiple versions can coexist side by side. Files here are set read-only to prevent accidental modification. This directory can be safely shared across containers or workers.
+
+- **`symlink_dir`** is the user-facing install directory. It presents a flat `<data_type>/<source>/` layout with no version in the path — the version is hidden behind symlinks that point into `cache_dir`. This allows application code to use stable, version-agnostic paths while the underlying data can be upgraded by simply re-pointing the symlinks.
+
+These two directories **must resolve to different physical locations** and neither can be nested inside the other. The manager validates this at construction time and raises an error if the paths overlap.
+
+**FAQ 2\. A process hangs waiting for a lock on a shared filesystem (e.g. WekaFS, NFS).**
+
+The resource manager uses file-based locks (`.lock` files) to coordinate concurrent access to the cache and symlink directories. On local filesystems, the OS automatically releases these locks when a process dies. On shared/networked filesystems like WekaFS or NFS, if a container is destroyed without a clean shutdown (e.g. killed by the orchestrator, node crash), the lock may not be released immediately. The filesystem will typically detect the dead client eventually, but this can take a varying amount of time.
+
+If setup appears stuck, you can manually remove the stale lock file (typically in the shared cache directory):
+
+```bash
+rm /path/to/cache_dir/.lock
+```
+
+If the interrupted process was mid-install, the cache may contain partially extracted archives. The safest recovery is to delete the entire affected `<data_type>/<source>/<version>/` directory under `cache_dir`, remove the corresponding entry from the local manifest files, and re-run setup. Partial cleanup (e.g. removing individual archives) is possible but requires checking the `.complete_extract` / `.complete_links` flag files as well.
+
+In shared-cache scenarios with sufficient storage, we recommend installing all data eagerly with a single leader process and letting workers use the pre-populated cache without locks via `cache_lock=False`.
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.

molmospaces_resources-0.0.1/molmospaces_resources/__init__.py

@@ -0,0 +1,12 @@
+from molmospaces_resources.manager import ResourceManager, SourceInfo
+from molmospaces_resources.setup_utils import setup_resource_manager, str2bool
+from molmospaces_resources.compact_trie import CompactPathTrie
+from molmospaces_resources.remote_storage import (
+    RemoteStorage,
+    R2RemoteStorage,
+    HFRemoteStorage,
+    GCRemoteStorage,
+)
+from molmospaces_resources.lmdb_data import GenericLMDBMap, JSonLMDBMap, PickleLMDBMap
+from molmospaces_resources.constants import LOCAL_MANIFEST_NAME, COMBINED_TRIES_NAME
+from molmospaces_resources.indexing import split_query_tokens

molmospaces_resources-0.0.1/molmospaces_resources/behaviors.py

@@ -0,0 +1,114 @@
+from __future__ import annotations
+
+import dataclasses
+from dataclasses import dataclass
+from enum import Enum
+from typing import Any
+
+from molmospaces_resources.indexing import ArchiveIndex, NumericIndex, SubstringIndex
+
+
+class LinkStrategy(Enum):
+    """How a source is exposed under ``symlink_dir``.
+
+    **Why two strategies?**
+
+    Scene XML files contain relative paths to sibling directories
+    (e.g. ``../objects/thor/Bowl.xml``).  MuJoCo's XML loader resolves
+    these relative to the *physical* file location, following symlinks.
+    If scenes used a ``GLOBAL`` directory symlink, the physical location
+    would be deep inside ``cache_dir``, and ``../objects/`` would resolve
+    to a nonexistent cache path instead of ``symlink_dir/objects/``.
+
+    ``PER_FILE`` avoids this: each scene file is an individual symlink
+    *inside* a real directory under ``symlink_dir``, so relative paths
+    resolve within the symlink tree where sibling data types are visible.
+
+    Data types that are leaf data (objects, grasps, etc.) don't reference
+    siblings via relative paths, so a single ``GLOBAL`` directory symlink
+    is safe and simpler.
+    """
+
+    PER_FILE = "per_file"
+    """Real directory with individual file symlinks into the cache."""
+
+    GLOBAL = "global"
+    """Single directory-level symlink pointing at the versioned cache dir."""
+
+
+class InstallMode(Enum):
+    """When archive contents are extracted."""
+
+    EAGER = "eager"
+    """Extract all archives at setup time."""
+
+    ON_DEMAND = "on_demand"
+    """Only fetch manifests at setup; extract archives on first use."""
+
+
+@dataclass
+class SourceBehavior:
+    """Per-source behaviour configuration.
+
+    ``archive_index`` may be a *class* (instantiated per source in
+    ``_resolve_behavior``) or an *instance* (used as-is).  Storing the
+    class in ``DATA_TYPE_DEFAULTS`` ensures each source gets its own
+    index instance with independent ``build()`` state.
+    """
+
+    link_strategy: LinkStrategy
+    install_mode: InstallMode
+    archive_index: type | ArchiveIndex | None = None
+
+
+DATA_TYPE_DEFAULTS: dict[str, SourceBehavior] = {
+    "robots": SourceBehavior(LinkStrategy.PER_FILE, InstallMode.EAGER),
+    "scenes": SourceBehavior(
+        LinkStrategy.PER_FILE, InstallMode.ON_DEMAND, NumericIndex
+    ),
+    "objects": SourceBehavior(
+        LinkStrategy.GLOBAL, InstallMode.ON_DEMAND, SubstringIndex
+    ),
+    "grasps": SourceBehavior(
+        LinkStrategy.GLOBAL, InstallMode.ON_DEMAND, SubstringIndex
+    ),
+    "test_data": SourceBehavior(LinkStrategy.GLOBAL, InstallMode.EAGER),
+    "benchmarks": SourceBehavior(LinkStrategy.GLOBAL, InstallMode.EAGER),
+    "franka-rby1-training-data": SourceBehavior(
+        LinkStrategy.GLOBAL, InstallMode.ON_DEMAND, NumericIndex
+    ),
+}
+
+SOURCE_OVERRIDES: dict[tuple[str, str], dict[str, Any]] = {
+    ("objects", "thor"): {"install_mode": InstallMode.EAGER},
+    ("objects", "objathor_metadata"): {"install_mode": InstallMode.EAGER},
+    ("grasps", "droid"): {"install_mode": InstallMode.EAGER},
+    ("grasps", "rum"): {"install_mode": InstallMode.EAGER},
+}
+
+
+def _resolve_behavior(
+    data_type: str,
+    source: str,
+    defaults: dict[str, SourceBehavior],
+    overrides: dict[tuple[str, str], dict[str, Any]],
+) -> SourceBehavior:
+    """Return the effective ``SourceBehavior`` for *(data_type, source)*.
+
+    If ``archive_index`` is a class (type), it is instantiated so each
+    source gets its own index with independent ``build()`` state.
+    Instantiation happens *after* applying overrides, so an override can
+    replace the index class/instance.
+    """
+    base = defaults.get(data_type)
+    if base is None:
+        raise ValueError(
+            f"No default SourceBehavior for data_type={data_type!r}. "
+            f"Known types: {sorted(defaults)}"
+        )
+    patch = overrides.get((data_type, source))
+    result = dataclasses.replace(base, **patch) if patch else base
+    # Instantiate if archive_index is a class rather than an instance
+    if isinstance(result.archive_index, type):
+        result = dataclasses.replace(result, archive_index=result.archive_index())
+    return result