<?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 Custome DOE: Controlling a factor so that it cannot repeat in run order in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Custome-DOE-Controlling-a-factor-so-that-it-cannot-repeat-in-run/m-p/384477#M63484</link>
    <description>&lt;P&gt;I am attempting to create a DOE with 2 factors we will call them configuration ( a 3 level categorical) and operator (also a 3 level categorical).&amp;nbsp;&amp;nbsp; I am trying to figure out a way in which JMP will allow me to create the DOE with a run order condition.&amp;nbsp;&amp;nbsp; The condition I need to set is that the same operator may not do two consecutive trials.&amp;nbsp;&amp;nbsp; I.e. Run 1 is Configuration 1, Operator 1 and Run 2 is Configuration 3, Operator 1 ; I have been told this cannot take place.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I am unsure as to how I could go about controlling this or instilling a rule?&amp;nbsp;&amp;nbsp; Any input would be greatly appreciated.&amp;nbsp;&amp;nbsp; Thank you for your time.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Jun 2023 21:04:08 GMT</pubDate>
    <dc:creator>A4Man2310</dc:creator>
    <dc:date>2023-06-08T21:04:08Z</dc:date>
    <item>
      <title>Custome DOE: Controlling a factor so that it cannot repeat in run order</title>
      <link>https://community.jmp.com/t5/Discussions/Custome-DOE-Controlling-a-factor-so-that-it-cannot-repeat-in-run/m-p/384477#M63484</link>
      <description>&lt;P&gt;I am attempting to create a DOE with 2 factors we will call them configuration ( a 3 level categorical) and operator (also a 3 level categorical).&amp;nbsp;&amp;nbsp; I am trying to figure out a way in which JMP will allow me to create the DOE with a run order condition.&amp;nbsp;&amp;nbsp; The condition I need to set is that the same operator may not do two consecutive trials.&amp;nbsp;&amp;nbsp; I.e. Run 1 is Configuration 1, Operator 1 and Run 2 is Configuration 3, Operator 1 ; I have been told this cannot take place.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I am unsure as to how I could go about controlling this or instilling a rule?&amp;nbsp;&amp;nbsp; Any input would be greatly appreciated.&amp;nbsp;&amp;nbsp; Thank you for your time.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2023 21:04:08 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Custome-DOE-Controlling-a-factor-so-that-it-cannot-repeat-in-run/m-p/384477#M63484</guid>
      <dc:creator>A4Man2310</dc:creator>
      <dc:date>2023-06-08T21:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Custome DOE: Controlling a factor so that it cannot repeat in run order</title>
      <link>https://community.jmp.com/t5/Discussions/Custome-DOE-Controlling-a-factor-so-that-it-cannot-repeat-in-run/m-p/384577#M63495</link>
      <description>&lt;P&gt;Presumably if you generate a table that randomizes the run order, then it would be possible for the same operator to run twice in a row. &amp;nbsp;What I would do is let JMP create the random order then manually revise that run order to meet your goal. &amp;nbsp;It can still be random enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is acceptable if you do it infrequently. &amp;nbsp;If you need to do this many times, then I understand your desire for an automated method. &amp;nbsp;However, if you need this randomized run order frequently, perhaps you can develop a randomized order once then re-use it for future experiments.&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2021 16:05:04 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Custome-DOE-Controlling-a-factor-so-that-it-cannot-repeat-in-run/m-p/384577#M63495</guid>
      <dc:creator>MiBo</dc:creator>
      <dc:date>2021-05-12T16:05:04Z</dc:date>
    </item>
  </channel>
</rss>

