# Config tune variables aren't matching the training types

**URL:** <https://discuss.ray.io/t/config-tune-variables-arent-matching-the-training-types/8450>\
**Category:** Ray Tune\
**Created:** [November 28, 2022, 7:23am UTC](https://discuss.ray.io/t/config-tune-variables-arent-matching-the-training-types/8450 "2022-11-28T07:23:32Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Yard1](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yard1/32/508_2.png) [@Yard1](https://discuss.ray.io/u/Yard1)\
**Post date:** [November 29, 2022, 11:13pm UTC](https://discuss.ray.io/t/config-tune-variables-arent-matching-the-training-types/8450/9 "2022-11-29T23:13:07Z")

</div>

The issue with the second way is expected, as Ray cannot access modules that are not in PYTHONPATH (see [TorchTrain fails if train\_func imports functions from a different file](https://discuss.ray.io/t/torchtrain-fails-if-train-func-imports-functions-from-a-different-file/8409) for more details).

Would it be possible for you to provide a simple reproducible example that we can run on our side without external dependencies?

---

_[View the full topic](https://discuss.ray.io/t/config-tune-variables-arent-matching-the-training-types/8450)._