NEWVectors or files. Pick a path.Start →
    Models/Robotics/notstrober/can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed
    Roboticslerobotapache-2.0

    can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed

    by notstrober

    Identifier
    Model ID
    notstrober/can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed

    Deploy can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed

    Single-tenant

    Mixpeek has no managed extractor for this model. On a single-tenant deployment you upload the weights and a custom plugin serves them next to the rest of your pipeline.

    Tags

    lerobotsafetensorsactroboticsdataset:notstrober/can-drink-to-cupholder-right-arm-single-armarxiv:2304.13705license:apache-2.0region:us

    Use can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed on Mixpeek

    Build multimodal processing pipelines with this model and others. Extract features, run inference, and set up retrieval in Mixpeek Studio.

    Open Studio

    How It Runs on Mixpeek

    On Mixpeek, can-drink-to-cupholder-right-arm-single-arm-ft-rightonly-r34-chunk60-120k-renamed runs as a managed extractor inside a processing pipeline. Point a bucket of robotics data at it, and Mixpeek handles GPU provisioning, batching, retries, and writing the outputs into a vector store you can query.

    Extractor outputs land in the Mixpeek Vector Store (MVS), where you can combine them with retrieval, reranking, and filter stages to build end-to-end search and agent-perception pipelines, no model-serving infrastructure to maintain.