<?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: Optimizing for Recall in Azure AutoML UI in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/optimizing-for-recall-in-azure-automl-ui/m-p/64301#M3820</link>
    <description>&lt;P&gt;On the databricks notebook itself, I can see that databricks.automl supports using recall as a primary metric&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Help on function classify in module databricks.automl:

    :param primary_metric:  primary metric to select the best model. Each trial will compute several metrics, but this one determines which model is selected from all the trials. One of "f1" (default), "log_loss", "accuracy", "precision", "recall", "roc_auc".&lt;/LI-CODE&gt;&lt;P&gt;But &lt;A href="https://docs.databricks.com/en/machine-learning/automl/train-ml-model-automl-api.html#classification-and-regression-parameters:~:text=binary%20classification%20problems.-,primary_metric,-str" target="_self"&gt;this blog&lt;/A&gt; didn't state that in the list of primary metrics&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mesh_0-1711030625724.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/6744i249589DD3C904857/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Mesh_0-1711030625724.png" alt="Mesh_0-1711030625724.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Mar 2024 14:18:35 GMT</pubDate>
    <dc:creator>Mesh</dc:creator>
    <dc:date>2024-03-21T14:18:35Z</dc:date>
    <item>
      <title>Optimizing for Recall in Azure AutoML UI</title>
      <link>https://community.databricks.com/t5/machine-learning/optimizing-for-recall-in-azure-automl-ui/m-p/64227#M3818</link>
      <description>&lt;P&gt;Hi all, I've been using Azure AutoML and noticed that I can choose &lt;STRONG&gt;'recall'&lt;/STRONG&gt; as my optimization metric in the notebook but not in the Azure AutoML UI. The &lt;A href="https://docs.databricks.com/en/machine-learning/automl/train-ml-model-automl-api.html#classification-and-regression-parameters:~:text=binary%20classification%20problems.-,primary_metric,-str" target="_new"&gt;Databricks documentation&lt;/A&gt; also doesn't list &lt;STRONG&gt;'recall'&lt;/STRONG&gt; as an optimization metric.&lt;/P&gt;&lt;P&gt;Is there a reason why &lt;STRONG&gt;recall&amp;nbsp;&lt;/STRONG&gt;isn't an option in the UI, or am I missing something? Any workaround or explanation would be helpful!&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 05:15:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/optimizing-for-recall-in-azure-automl-ui/m-p/64227#M3818</guid>
      <dc:creator>Mesh</dc:creator>
      <dc:date>2024-03-21T05:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: Optimizing for Recall in Azure AutoML UI</title>
      <link>https://community.databricks.com/t5/machine-learning/optimizing-for-recall-in-azure-automl-ui/m-p/64301#M3820</link>
      <description>&lt;P&gt;On the databricks notebook itself, I can see that databricks.automl supports using recall as a primary metric&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Help on function classify in module databricks.automl:

    :param primary_metric:  primary metric to select the best model. Each trial will compute several metrics, but this one determines which model is selected from all the trials. One of "f1" (default), "log_loss", "accuracy", "precision", "recall", "roc_auc".&lt;/LI-CODE&gt;&lt;P&gt;But &lt;A href="https://docs.databricks.com/en/machine-learning/automl/train-ml-model-automl-api.html#classification-and-regression-parameters:~:text=binary%20classification%20problems.-,primary_metric,-str" target="_self"&gt;this blog&lt;/A&gt; didn't state that in the list of primary metrics&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mesh_0-1711030625724.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/6744i249589DD3C904857/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Mesh_0-1711030625724.png" alt="Mesh_0-1711030625724.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 14:18:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/optimizing-for-recall-in-azure-automl-ui/m-p/64301#M3820</guid>
      <dc:creator>Mesh</dc:creator>
      <dc:date>2024-03-21T14:18:35Z</dc:date>
    </item>
  </channel>
</rss>

