The Project Management Worksite of Xalgorithms Alliance: Issueshttps://xalgorithms.redminepro.net/https://xalgorithms.redminepro.net/themes/redminepro2-2.8.0/favicon/favicon.ico?15657305472024-02-20T12:01:43ZThe Project Management Worksite of Xalgorithms Alliance
Redmine 2.1 Rule Maker v3 - Bug #233 (New): Remove obsolete mouse-over containing the former suggested 99...https://xalgorithms.redminepro.net/issues/2332024-02-20T12:01:43ZJoseph Potvin
<p>The end-date field in rule metadata still has a mouse-over suggesting 9999, even though we have the improved auto-fill method. Please remove the obsolete 9999 one. Screenshot attached here.</p>
2.1 Rule Maker v3 - Design #230 (Feedback): In the "Add Linked Rule or Lookup" form, "Column" and...https://xalgorithms.redminepro.net/issues/2302023-08-23T12:14:52ZJoseph Potvin
<p>While working on a sample rule, I realised that the column and row should be optional fields.</p>
2.1 Rule Maker v3 - Design #229 (New): When RM is saves a record with a lookup table, the filenam...https://xalgorithms.redminepro.net/issues/2292023-08-23T12:03:49ZJoseph Potvin
<p>When RuleMaker saves a record with a logic gate, it correctly produces a filename like: rule_64a3389a-2d1f-4906-ad6b-d38414a157a2.json</p>
<p>But when it is saving a record with a lookup table, it should produce a filename like: lookup_64a3389a-2d1f-4906-ad6b-d38414a157a2.json</p>
2.1 Rule Maker v3 - Bug #227 (New): Columns don't need to be shifted for lookup tables.https://xalgorithms.redminepro.net/issues/2272023-08-01T22:08:43ZHuda Hussain2.1 Rule Maker v3 - Bug #226 (New): Show loading bar when loading in arrayhttps://xalgorithms.redminepro.net/issues/2262023-08-01T22:07:05ZHuda Hussain2.1 Rule Maker v3 - Bug #225 (New): Add scrolling to both rows and columns in lookup tablehttps://xalgorithms.redminepro.net/issues/2252023-08-01T22:03:59ZHuda Hussain2.1 Rule Maker v3 - Design #222 (Feedback): Add ability to draw upon words from standard schemas ...https://xalgorithms.redminepro.net/issues/2222023-07-27T11:47:37ZJoseph Potvin
<p>This task follows from <a href="https://xalgorithms.redminepro.net/issues/104">https://xalgorithms.redminepro.net/issues/104</a></p>
<a name="Requirement"></a>
<h3 >Requirement<a href="#Requirement" class="wiki-anchor">¶</a></h3>
<p>Standard semantic schemas should be easy to draw upon while using RuleMaker and RuleTaker.</p>
<a name="Discussion"></a>
<h3 >Discussion<a href="#Discussion" class="wiki-anchor">¶</a></h3>
<p>Most OASIS schemas now include a JSON representation. However overlapping inconsistencies among both complementary and competing standard semantic schemas are common, and can be expected to persist in varying degrees. So the RuleData representation, as well as the RuleMaker and RuleTaker functions, need a simple way for rule authors to employ terminology from any schema(s) they consider relevant.</p>
2.1 Rule Maker v3 - Feature #221 (New): Add a Free/Libre LLM Service to RuleMaker for Users to Op...https://xalgorithms.redminepro.net/issues/2212023-07-26T22:08:37ZJoseph Potvin
<a name="Context"></a>
<h3 >Context:<a href="#Context" class="wiki-anchor">¶</a></h3>
<p>A user of RuleMaker wants to structure into RuleMaker a rule or section of a rule.</p>
<a name="Problem"></a>
<h3 >Problem:<a href="#Problem" class="wiki-anchor">¶</a></h3>
<p>Often, the original text of a rule is so convoluted that a typical intelligent person would find it difficult and/or time-consuming to tease it apart into discrete declarative statements of the Input Conditions and Output Assertion statements that the RuleMaker user must begin with. </p>
<a name="A-Solution"></a>
<h3 >A Solution:<a href="#A-Solution" class="wiki-anchor">¶</a></h3>
<p>Add an auxiliary LLM text simplifier service to RuleMaker to enable the following sequence:</p>
<ol>
<li><p>A user copies the (extended unicode) text of a rule (or section of a rule) from any source, and pastes it into a field in RuleMaker (perhaps a frame called "Simplify this!").</p></li>
<li><p>RuleMaker first prefaces the pasted text with a default "response engineered" instruction that instructs an LLM to simplify the pasted text in a way that will then be much easier for the user to shoehorn into DWDS RuleFiniteStateGrammar (RFSG). RFSG is discussed on pgs 155-159 of the DWDS specification. The default instruction to the LLM can be something like: <u>"Re-write the following quoted text using only discrete declarative sentences in a style that conforms with the essential practices of 'RuleSpeak'. Start a new line for each sentence. Retain all semantic meaning, operational steps, and/or external references."</u></p></li>
<li><p>The user of RuleMaker must be able to edit this default instruction, and then to save their customized or alternative instruction into a locally-stored lookup table. A retrieval process will enable the user to find and load from a list of default instructions.</p></li>
<li><p>Upon "Submit" cicked by the user, RuleMaker runs the instruction with the pasted text through the LLM, and presents the result to the user in a refreshed frame (or equivalent). This result should be presented to the user in an editable text field so that they can directly modify that text. </p></li>
<li><p>The 'Result" frame should be able to e dragged to any position on the screen and should be able to be minimimzed/maxmined with conventional [-] and [+] operations, so that the user can easily copy and paste segments from that result into a RuleMaker Logic Gate. </p></li>
</ol>
<a name="Method"></a>
<h3 >Method:<a href="#Method" class="wiki-anchor">¶</a></h3>
<p>Initially I suggest to use MPT-30B-chat for this purpose. <a href="https://github.com/mayooear/private-chatbot-mpt30b-langchain">https://github.com/mayooear/private-chatbot-mpt30b-langchain</a> <br>
(See the README file at <a href="https://github.com/mayooear/private-chatbot-mpt30b-langchain#readme">https://github.com/mayooear/private-chatbot-mpt30b-langchain#readme</a> ) </p>
<p>You can comparatively test various LLMs here: <a href="https://chat.lmsys.org/?model">https://chat.lmsys.org/?model</a> In particular, click on "Leaderboard" in the top navigator there to see that MPT-30B-chat is adjacent to the most capable LLM. Also try some examples with the "Side-by-Side" option from the navigator along the top.</p>
<p>Either we run it as part of a RuleMaker instance, or RuleMaker runs through a frame someone else's hosted instance of this LLP such as this one: <a href="https://huggingface.co/spaces/mosaicml/mpt-30b-chat">https://huggingface.co/spaces/mosaicml/mpt-30b-chat</a> </p>
<p>If we run it as part of RuleMaker, it could be trained on a database on RuleSpeak examples. But initially I reckon it's simpler for use to rely on the external hosted service.</p>
<p>Once RuleReserve contains a significant number of RuleData records that real people have created with RuleMaker, our own MPT-30B-chat instances can be trained on these.</p>
2.1 Rule Maker v3 - Feature #220 (Resolved): Automatically segment large lookup tables upon .csv ...https://xalgorithms.redminepro.net/issues/2202023-07-26T17:14:27ZJoseph Potvin
<p>Sometimes when importing a .csv file into RuleMaker's "Lookup Table" utility, the source table might be larger than the RuleMaker application can conveniently handle. This task is to design and create a simple routine that will automatically generate hierarchical forward-chained tables [table->subtables->subsubtables] when there are many columns of hierarchical data; and automatically generate sequential forward-chained tables [table1->table2->table3...] when there are many rows data. Suggestions for how to implement this can be discussed in replies to this 'task'.</p>
<p>RuleMaker is not running the data queries, but it does provide a general utility for converting locally stored .csv tuples of reference data into DWDS-conformant .json tuples available for universal use over the IPFS Internet. Typically one needs to first determine if most queries of a lookup table will be sequential or random. RuleMaker's Lookup Table generator needs to support both. </p>
<p>I have checked boxes for Don, Ted and Nhamo to 'watch' this task, as each of you might have suggestions for a simpler and/or more standard way to meet this requirement; and at least to be aware that we're planning to do this.</p>
2.1 Rule Maker v3 - Feature #217 (New): Adjust the RuleMaker navigator UI so that Logic Gate and ...https://xalgorithms.redminepro.net/issues/2172023-07-20T02:17:02ZJoseph Potvin
<p>The "Lookup Table" option should be at the same general location as the "Logic Gate" option, so that it is obvious the user has to choose one or the other.</p>
2.1 Rule Maker v3 - Bug #216 (New): Make sure lookup table is exported to ietf standard.https://xalgorithms.redminepro.net/issues/2162023-07-19T18:42:30ZHuda Hussain2.1 Rule Maker v3 - Feature #215 (New): Create an optional window that shows the JSON window of l...https://xalgorithms.redminepro.net/issues/2152023-07-19T18:39:54ZHuda Hussain2.1 Rule Maker v3 - Bug #212 (New): Import/Export: Filter the shown list for only ".json" fileshttps://xalgorithms.redminepro.net/issues/2122023-06-29T14:08:59ZJoseph Potvin
<p>When the user clicks to upload from "Drag and drop a Rule file here or click to upload", the resulting list of files should only display ".json" and ".dwd" files. </p>
<p>(We're not yet producing a ".dwd" extension, but once we have RM-RR-RT integration fully operational, we'll do that. So you might as well include .dwd in this filter now.)</p>
2.1 Rule Maker v3 - Bug #210 (New): WHEN-WHEN-THEN lookup table: Provide toggle to show/NOTshow ...https://xalgorithms.redminepro.net/issues/2102023-06-28T02:12:06ZJoseph Potvin
<p>Having the default show WHEN and THEN is useful but the user should be able to make those labels disappear with a toggle at top left</p>
2.1 Rule Maker v3 - Support #209 (New): WHEN-WHEN-THEN lookup table: Make 'clickable' text notice...https://xalgorithms.redminepro.net/issues/2092023-06-28T01:44:24ZJoseph Potvin
<p>I think it would be useful to given all clickable text a light grey background. Or some other distinguishing method. And then change the "Generate Internal Cells" text also to this method -- making it grey might confuse with being "grey'd out" (i.e. inactive). </p>