<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to fix the error on INVALID_PARAMETER_VALUE when using mlflow for tracking a yolo model training? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5268#M1731</link>
    <description>&lt;P&gt;@Yosef Hdi​&amp;nbsp;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error message you received suggests that the path parameter in the log_artifact function call expects a relative path, rather than an absolute path. To fix this issue, you can try using a relative path to the requirements.txt file instead of an absolute path. Assuming that your requirements.txt file is located in the /Shared/YOLOv8 directory, you can try using the following code to log the requirements.txt file as an artifact using a relative path:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;import os
import mlflow
&amp;nbsp;
# get the absolute path to the current working directory
cwd = os.getcwd()
&amp;nbsp;
# define the relative path to the requirements.txt file
requirements_path = os.path.relpath('/dbfs/Shared/YOLOv8/requirements.txt', start=cwd)
&amp;nbsp;
# log the requirements.txt file as an artifact
mlflow.log_artifact(requirements_path)&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;In this code, os.getcwd() returns the absolute path to the current working directory. The  os.path.relpath() function is then used to convert the absolute path to the requirements.txt file to a relative path based on the current working directory. Finally, mlflow.log_artifact() is called with the relative path to the requirements.txt file as the argument.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps! Let me know if you have any other questions.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Apr 2023 04:54:08 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2023-04-27T04:54:08Z</dc:date>
    <item>
      <title>How to fix the error on INVALID_PARAMETER_VALUE when using mlflow for tracking a yolo model training?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5267#M1730</link>
      <description>&lt;P&gt;I'm new to databricks, and I'm trying to train yolo model and use mlflow to track the parameters and log the models. I keep getting this error related to the requirements.txt file path: INVALID_PARAMETER_VALUE: Invalid value '/Shared/YOLOv8/requirements.txt' for parameter: 'path'. Path must be relative.&lt;/P&gt;&lt;P&gt;I've tried to use the mlflow.log_artifact(requirements_path) with requirements_path being a relative path to the requirements.txt (/dbfs/FileStore/...), but it did not help. I'd appreciateany help to solve this problem. Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 22:07:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5267#M1730</guid>
      <dc:creator>Joey</dc:creator>
      <dc:date>2023-04-25T22:07:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix the error on INVALID_PARAMETER_VALUE when using mlflow for tracking a yolo model training?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5268#M1731</link>
      <description>&lt;P&gt;@Yosef Hdi​&amp;nbsp;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error message you received suggests that the path parameter in the log_artifact function call expects a relative path, rather than an absolute path. To fix this issue, you can try using a relative path to the requirements.txt file instead of an absolute path. Assuming that your requirements.txt file is located in the /Shared/YOLOv8 directory, you can try using the following code to log the requirements.txt file as an artifact using a relative path:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;import os
import mlflow
&amp;nbsp;
# get the absolute path to the current working directory
cwd = os.getcwd()
&amp;nbsp;
# define the relative path to the requirements.txt file
requirements_path = os.path.relpath('/dbfs/Shared/YOLOv8/requirements.txt', start=cwd)
&amp;nbsp;
# log the requirements.txt file as an artifact
mlflow.log_artifact(requirements_path)&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;In this code, os.getcwd() returns the absolute path to the current working directory. The  os.path.relpath() function is then used to convert the absolute path to the requirements.txt file to a relative path based on the current working directory. Finally, mlflow.log_artifact() is called with the relative path to the requirements.txt file as the argument.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps! Let me know if you have any other questions.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Apr 2023 04:54:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5268#M1731</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-04-27T04:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix the error on INVALID_PARAMETER_VALUE when using mlflow for tracking a yolo model training?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5269#M1732</link>
      <description>&lt;P&gt;Hi @Yosef Hdi​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for posting your question in our community! We are happy to assist you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To help us provide you with the most accurate information, could you please take a moment to review the responses and select the one that best answers your question?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will also help other community members who may have similar questions in the future. Thank you for your participation and let us know if you need any further assistance!&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2023 06:37:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5269#M1732</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-02T06:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix the error on INVALID_PARAMETER_VALUE when using mlflow for tracking a yolo model training?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5270#M1733</link>
      <description>&lt;P&gt;Thanks for the reply, @Suteja Kanuri​&amp;nbsp;. I tried the proposed solution. This time got this message:&lt;/P&gt;&lt;P&gt;Invalid artifact path: '/Shared/YOLOv8'. Names may be treated as files in certain cases, and must not resolve to other names when treated as such. This name would resolve to '/Shared/YOLOv8'&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 21:08:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-fix-the-error-on-invalid-parameter-value-when-using/m-p/5270#M1733</guid>
      <dc:creator>Joey</dc:creator>
      <dc:date>2023-05-03T21:08:56Z</dc:date>
    </item>
  </channel>
</rss>

