# Tune.run works but TuneGridSearchCV.fit does not work for me

**URL:** <https://discuss.ray.io/t/tune-run-works-but-tunegridsearchcv-fit-does-not-work-for-me/6519>\
**Category:** Ray Tune\
**Created:** [June 15, 2022, 10:01pm UTC](https://discuss.ray.io/t/tune-run-works-but-tunegridsearchcv-fit-does-not-work-for-me/6519 "2022-06-15T22:01:27Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![matthewdeng](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/matthewdeng/32/1446_2.png) [@matthewdeng](https://discuss.ray.io/u/matthewdeng)\
**Post date:** [July 3, 2022, 9:32pm UTC](https://discuss.ray.io/t/tune-run-works-but-tunegridsearchcv-fit-does-not-work-for-me/6519/14 "2022-07-03T21:32:10Z")

</div>

Hey looks like you were able to create a new topic [here](https://discuss.ray.io/t/local-object-store-on-worker-nodes-not-working-worker-plasma-stays-at-0/6676), makes sense as this is more of a Core issue.

Depending on the nature of the problem, you may be able to simplify the repro even further. In the example below, we force `f` to be executed on a worker node, and try to access the results (from object store) on the head node.

```auto
import ray
import numpy as np

@ray.remote
def f():
    return np.arange(100_000)

ip_resource = "node:<WORKER_NODE_IP>"
result = ray.get(f.options(resources={ip_resource: 0.01}).remote())

```

---

_[View the full topic](https://discuss.ray.io/t/tune-run-works-but-tunegridsearchcv-fit-does-not-work-for-me/6519)._