<?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: Covering array issue: not expected analysis output in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Covering-array-issue-not-expected-analysis-output/m-p/420515#M66935</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1)the output only show main effect and its level that causes fails, but no 2-factor-interaction. Why with t2 in this case , only the main effects reported?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The analysis works on the principle that the simplest explanation (involving the fewest number of factors) is where to investigate possible failure-inducing combinations. In this case, since there are main effects that would explain it, this is where it would start. Empirically it makes sense to investigate those first, but&amp;nbsp;in the future we plan to add the ability to increase the combinations looked at.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) there are couple of known combination that will cause fail were design into the test, but the analysis didn't show those factors and its combination that will cause fail. Is this an issue on Covering array?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The big issue here is that there are so many rows with failures, it still thinks there are single factors that could be the cause. In future versions we are planning to add the ability to examine a higher order of combinations. In this case though, there are so many failures and so few successes, even if you did this the list of potential causes would be nearly all two-factor combinations, because very few combinations can be removed from consideration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The key is to have some more runs with successes to reduce that set of potential causes. You can get a better sense in Section 4 of this paper: &lt;A href="https://rdcu.be/cv7tv" target="_blank"&gt;https://rdcu.be/cv7tv&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Sep 2021 01:22:25 GMT</pubDate>
    <dc:creator>Ryan_Lekivetz</dc:creator>
    <dc:date>2021-09-23T01:22:25Z</dc:date>
    <item>
      <title>Covering array issue: not expected analysis output</title>
      <link>https://community.jmp.com/t5/Discussions/Covering-array-issue-not-expected-analysis-output/m-p/419735#M66870</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran a covering array with t2. there are totally 27 runs with 15 factors.&amp;nbsp;&lt;/P&gt;&lt;P&gt;success runs = 3, failure runs = 24&lt;/P&gt;&lt;P&gt;1)the output only show&amp;nbsp; main effect and its level that causes fails, but no 2-factor-interaction.&lt;/P&gt;&lt;P&gt;Why with t2 in this case , only the main effects reported?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) there are couple of known combination that will cause fail were design into the test, but the analysis didn't show those factors and its combination that will cause fail. Is this an issue on Covering array?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone help me to understand more why above issues happened?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 00:39:09 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Covering-array-issue-not-expected-analysis-output/m-p/419735#M66870</guid>
      <dc:creator>dadawasozo</dc:creator>
      <dc:date>2023-06-09T00:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Covering array issue: not expected analysis output</title>
      <link>https://community.jmp.com/t5/Discussions/Covering-array-issue-not-expected-analysis-output/m-p/420515#M66935</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1)the output only show main effect and its level that causes fails, but no 2-factor-interaction. Why with t2 in this case , only the main effects reported?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The analysis works on the principle that the simplest explanation (involving the fewest number of factors) is where to investigate possible failure-inducing combinations. In this case, since there are main effects that would explain it, this is where it would start. Empirically it makes sense to investigate those first, but&amp;nbsp;in the future we plan to add the ability to increase the combinations looked at.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) there are couple of known combination that will cause fail were design into the test, but the analysis didn't show those factors and its combination that will cause fail. Is this an issue on Covering array?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The big issue here is that there are so many rows with failures, it still thinks there are single factors that could be the cause. In future versions we are planning to add the ability to examine a higher order of combinations. In this case though, there are so many failures and so few successes, even if you did this the list of potential causes would be nearly all two-factor combinations, because very few combinations can be removed from consideration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The key is to have some more runs with successes to reduce that set of potential causes. You can get a better sense in Section 4 of this paper: &lt;A href="https://rdcu.be/cv7tv" target="_blank"&gt;https://rdcu.be/cv7tv&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Sep 2021 01:22:25 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Covering-array-issue-not-expected-analysis-output/m-p/420515#M66935</guid>
      <dc:creator>Ryan_Lekivetz</dc:creator>
      <dc:date>2021-09-23T01:22:25Z</dc:date>
    </item>
  </channel>
</rss>

