Jump to content

Alessandro Piazza

Rulexer
  • Posts

    5
  • Joined

  • Last visited

Everything posted by Alessandro Piazza

  1. Hi @Jack Adams Yes, you can add colours to your attributes! Just right-click on a column label, then select “Set style column” to modify the column's background colour, border, text font, etc. Keep in mind that columns with specific “Roles” have their own default background colour (for instance, “Output” columns are yellow). Right-clicking on a column label also gives you access to other options, like conditional formatting, so feel free to customize your spreadsheet! I hope it helps, Alessandro
  2. Hi Andrew! Yes, you can do it! Let’s take a look at this flow, where I divided “Fitting Data” in one line and “Future Data” in the other: In the upper line of the flow, we performed these steps: Fit a LLM model to the “Fitting Data”. Converted the ruleset generated by the LLM into a dataset (if you use a type of model that doesn’t export rules, you need a Model to Dataset task). Exported the datamanager into a folder (you can choose the format and the folder that you prefer). In the lower line of the flow, we performed these steps: We re-imported the file containing the rules in data structure. We re-converted the rules contained in this file from data structure to rules structure, through a Dataset to Ruleset task. With a Select Flows task, we kept the rules from the Dataset to Ruleset task and the data from the “Future Data” dataset. Through an Apply Model task, we applied the rules to the data . And we are done!
  3. Hi Andrew! Yes, you can make it through a join task with a certain configuration. Imagine that your key variable is the ID on the screen: 1. You can create a copy of the same dataset by connecting it to another datamanager. Then, you can input both datamanagers into a join task: 2. Now, you need to configure the join as "Inner join", select the IDs as Matching attributes and "<" as Operator: 3. And you are done! If you want to refine your result, you can also apply a Reshape to Long task on top of this (after dataman3) after creating another variable that identifies the “Pair ID” (you can create it just with an enum()), just to remove the dependence on the attributes ID and ID_1. This will be the final result: Please be aware that this method will not work with a large dataset, as the join computation could lead to memory issues.
  4. Hi Andrew! The function that you are looking for is exactly the find one, but you must set the charpos parameter to a value different respect to the default of 0: Otherwise it will give you only the True/False result.
  5. Hello! Please try to follow these steps: Split Attributes (right click on the attribute in the left panel of Data Manager) -> by fixed string -> |. (If you want to keep the original column, create a copy before splitting it). This will generate as many columns as the substrings delimited by |. The new columns will be called something like Reference Column-0, Reference Column-1. ToLong transforming all the attributes whose name starts with “Reference Column-”. (you can use “Filtered List” in Reshape To Long). This will generate a Long_1 (not relevant) and a Wide_1 column. Split Attribute as at point 1 on the Wide_1 column using - as separator. The columns generated by SplitAttribute should be the output you were expecting.
×
×
  • Create New...