Keep Currently Completed State on Exception.

dragoljub
dragoljub New Altair Community Member
edited November 5 in Community Q&A
Is there any way that RM could keep the results of the last successfully completed operators so that when an exception occurs you do not have to start from the beginning of the process to fix the problem.

It would be nice to go into the pause mode right before the problem operator and then continue after parameters have been changed etc.

-Gagi
Tagged:

Answers

  • fischer
    fischer New Altair Community Member
    Hi,

    there used to be an option to execute only dirty operators when running a process which would do pretty much what you are asking. However, this freature has its limitations. E.g., if you have an operator that changes *data*, the changes are also propagated "to the left". Hence, if you execute it twice, your results will be rubbish. This feature would work if we would always copy the entire data which is what we want to avoid. However, in its current state, this feature causes more trouble than it avoids. Therefore, we removed it again.

    Cheers,
    Simon

    (If you check out the current SVN version, the feature you are asking for is commented in MainFrame, line 622-633, so you can easily re-enable it and play with it.)

Categories