Jump to content

Francesco Mantovani

Rulexer
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Francesco Mantovani

  1. Hi Griz! Yes what you are suggesting is correct. In detail for example if you have to compute a flow of 100 iterations, I would suggest you export a file for each of them. In case something goes wrong, just count how many files are exported to see at which iteration the process stopped.
  2. Hi Andrew! In this case, we recommend adding debug exports at different iterations. This offers a double advantage: monitoring the correct execution of the flow without necessarily waiting for the conclusion, and providing the option to resume the computation from where it stopped. Let me know how it goes!
  3. Hi Mike, to also include nodes that contain only incoming or outgoing edges, simply add the task "Reshape to long" and group on the resulting column in the datamanager after. As in this example: setting “Reshape to long” task in this way: After renaiming Wide_1 to Node, and grouping on that, you get this result:
  4. Hi, To make sure that the module is executed after the Runtime Variables task I would suggest you to add the Select Flow task that works as a kind of traffic light preventing the computation from continuing if all the tasks before it are not computed. Before: After: Flow computation will proceed only when both inputs (both the Data Manager and the Runtime Variables task) are correctly computed, so we can be sure that the Execute Rulex Flow File task is always executed next. Be sure to update the mapping in the Execute Rulex Flow File task, and define the input type in the Select Flow task. Another solution could be exploiting priorities. If you right-click you can edit the priority on each task. Tasks with a higher priority value will be computed first. For example you can do this:
×
×
  • Create New...