<?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 PROC GRADBOOST AUTOTUNE: Partition-level Gini for all evaluated configs without refitting? in SAS Data Science</title>
    <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-GRADBOOST-AUTOTUNE-Partition-level-Gini-for-all-evaluated/m-p/982878#M11114</link>
    <description>&lt;P&gt;I’m tuning a binary model with PROC GRADBOOST + AUTOTUNE and PARTITION (train/validation/test). The HISTORYTABLE= captures one objective per evaluation (Gini on validation or the k-fold average), but I need Gini per partition (train/valid/test) for every evaluated configuration. Right now, my workaround is to refit each configuration, score, and run PROC ASSESS BY _PartInd_ to compute AUC → Gini, which is costly.&lt;BR /&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is there a built-in way to get partition-level metrics (train/valid/test) for all evaluated configurations without refitting each one?&lt;/LI&gt;&lt;LI&gt;Is there a supported pattern to persist each candidate model during tuning (not just the champion) so I can score later and compute partition metrics without retraining?&lt;/LI&gt;&lt;LI&gt;Any roadmap to add partition-level metrics (or an option to save all intermediate models) to AUTOTUNE outputs?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;From the docs, AUTOTUNE records a single objective per evaluation (validation/k-fold) in the history and doesn’t expose per-partition metrics by default.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Feb 2026 19:58:31 GMT</pubDate>
    <dc:creator>Zaid_Sanchez</dc:creator>
    <dc:date>2026-02-02T19:58:31Z</dc:date>
    <item>
      <title>PROC GRADBOOST AUTOTUNE: Partition-level Gini for all evaluated configs without refitting?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-GRADBOOST-AUTOTUNE-Partition-level-Gini-for-all-evaluated/m-p/982878#M11114</link>
      <description>&lt;P&gt;I’m tuning a binary model with PROC GRADBOOST + AUTOTUNE and PARTITION (train/validation/test). The HISTORYTABLE= captures one objective per evaluation (Gini on validation or the k-fold average), but I need Gini per partition (train/valid/test) for every evaluated configuration. Right now, my workaround is to refit each configuration, score, and run PROC ASSESS BY _PartInd_ to compute AUC → Gini, which is costly.&lt;BR /&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is there a built-in way to get partition-level metrics (train/valid/test) for all evaluated configurations without refitting each one?&lt;/LI&gt;&lt;LI&gt;Is there a supported pattern to persist each candidate model during tuning (not just the champion) so I can score later and compute partition metrics without retraining?&lt;/LI&gt;&lt;LI&gt;Any roadmap to add partition-level metrics (or an option to save all intermediate models) to AUTOTUNE outputs?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;From the docs, AUTOTUNE records a single objective per evaluation (validation/k-fold) in the history and doesn’t expose per-partition metrics by default.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Feb 2026 19:58:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/PROC-GRADBOOST-AUTOTUNE-Partition-level-Gini-for-all-evaluated/m-p/982878#M11114</guid>
      <dc:creator>Zaid_Sanchez</dc:creator>
      <dc:date>2026-02-02T19:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: PROC GRADBOOST AUTOTUNE: Partition-level Gini for all evaluated configs without refitting?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-GRADBOOST-AUTOTUNE-Partition-level-Gini-for-all-evaluated/m-p/983106#M11115</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As far as I know, it's indeed not possible to get the tuner objective function (&lt;SPAN class="xisCas-equals"&gt;GINI for example or Misclassification Error Percentage) for all partitions. The objective metric you see (in autotune&amp;nbsp;historytable=&lt;/SPAN&gt;&lt;SPAN class="xisCas-equals"&gt;) is the one coming from validation calculations.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;Remark that a partition is always used by Autotune, specifically to avoid overfitting. This partition (separate table for scoring/validation) is either supplied by the user or created internally by Autotune.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL class="lia-list-style-type-disc"&gt;
&lt;LI&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;Here's where you can make product-suggestions for the roadmap:&lt;BR /&gt;&lt;A href="https://communities.sas.com/t5/SAS-Product-Suggestions/idb-p/product-suggestions" target="_blank"&gt;https://communities.sas.com/t5/SAS-Product-Suggestions/idb-p/product-suggestions&lt;/A&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;(previously known as&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;SASware Ballot)&lt;/LI&gt;
&lt;LI&gt;You can also open a Technical Support ticket instead and ask for this. (&lt;A href="https://support.sas.com/en/technical-support.html" target="_blank"&gt;https://support.sas.com/en/technical-support.html&lt;/A&gt;)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;Some references:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;A href="https://support.sas.com/resources/papers/proceedings17/SAS0514-2017.pdf" target="_blank"&gt;Automated Hyperparameter Tuning for Effective Machine Learning&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;(SAS Global Forum&amp;nbsp;2017 paper)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;A href="https://blogs.sas.com/content/sgf/2025/06/13/boost-ml-accuracy-with-hyperparameter-tuning/" target="_blank"&gt;Boost ML accuracy with hyperparameter tuning (with a fun twist) - SAS Users&lt;/A&gt;&amp;nbsp;(&lt;SPAN class="posted-by"&gt;By&amp;nbsp;&lt;SPAN class="reviewer"&gt;&lt;A title="Posts by Stu Sztukowski" href="https://blogs.sas.com/content/sgf/author/stusztukowski/" rel="author" target="_blank"&gt;Stu Sztukowski&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="posted-on"&gt;on&amp;nbsp;&lt;SPAN class="dtreviewed"&gt;&lt;TIME class="value-title" title="2025-06-13" datetime="2025-06-13T12:19:14-04:00"&gt;June 13, 2025)&lt;/TIME&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;SPAN class="posted-on"&gt;&lt;SPAN class="dtreviewed"&gt;&lt;A href="https://blogs.sas.com/content/sgf/2025/12/17/the-afterparty-hyperparameter-autotuning-revisited/" target="_blank"&gt;The afterparty: Hyperparameter autotuning revisited - SAS Users&lt;/A&gt;&amp;nbsp;(&lt;SPAN class="posted-by"&gt;By&amp;nbsp;&lt;SPAN class="reviewer"&gt;&lt;A title="Posts by Stu Sztukowski" href="https://blogs.sas.com/content/author/stusztukowski/" rel="author" target="_blank"&gt;Stu Sztukowski&lt;/A&gt;&amp;nbsp;on&amp;nbsp;&lt;A href="https://blogs.sas.com/content/sgf/" target="_blank"&gt;SAS Users&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;TIME class="value-title" title="2025-12-17" datetime="2025-12-17T17:21:52-04:00"&gt;December 17, 2025)&lt;/TIME&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;SPAN class="posted-on"&gt;&lt;SPAN class="dtreviewed"&gt;&lt;A href="https://go.documentation.sas.com/doc/en/workbenchcdc/v_001/vwbcasml/vwbcasml_gradboost_syntax02.htm" target="_blank"&gt;SAS Help Center: AUTOTUNE Statement&lt;/A&gt; (&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;GRADBOOST Procedure)&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://go.documentation.sas.com/doc/da/pgmsascdc/v_067/casml/casml_introcom_sect005.htm" target="_blank"&gt;SAS Help Center: AUTOTUNE Statement&lt;/A&gt;&amp;nbsp;(Machine Learning Procedures --&amp;nbsp;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;SPAN class="posted-on"&gt;&lt;SPAN class="dtreviewed"&gt;Shared Concepts)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;SPAN class="posted-on"&gt;&lt;SPAN class="dtreviewed"&gt;&lt;BR /&gt;Ciao,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="xisCas-equals"&gt;&lt;SPAN&gt;&lt;SPAN class="posted-on"&gt;&lt;SPAN class="dtreviewed"&gt;Koen&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 23:26:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/PROC-GRADBOOST-AUTOTUNE-Partition-level-Gini-for-all-evaluated/m-p/983106#M11115</guid>
      <dc:creator>sbxkoenk</dc:creator>
      <dc:date>2026-02-05T23:26:23Z</dc:date>
    </item>
  </channel>
</rss>

