The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
OperatorChain - execute subprocess line by line
I have class OperatorChain which has two (extendable) inner ports:
- OutputPortExtender
- InputPortExtender
(see the figure below)
Is it possible to execute process in a "line by line" manner (i.e. port by port)?
Currently I call:
The only possible way I know is to terminate the execution by throwing an exception in the inner operator. I am afraid that capturing exceptions can be much slower.
Thanks for any help.
radone
- OutputPortExtender
- InputPortExtender
(see the figure below)
#######################
# #
##-------Line 1------##
# #
##-------Line 2------##
# #
# ... #
# #
#######################
Is it possible to execute process in a "line by line" manner (i.e. port by port)?
Currently I call:
getSubprocess(0).execute();I would like to save processing time and execute next "lines" only if the previous lines go well (something like AdaBoost).
The only possible way I know is to terminate the execution by throwing an exception in the inner operator. I am afraid that capturing exceptions can be much slower.
Thanks for any help.
radone
Tagged:
0
Answers
it seems like your "lines" are independent. Can't you make multiple subprocess and put a "line" into each?
Best,
Simon
In case of subprocesses it should work, however the GUI interface will be quite .
If the same would be possible in line by line approach it would be much better.
just to make sure we are talking about the same thing: These 40 subprocess you are expecting, are all different, so the user has to do a lot of process design work anyway, right?
Best,
Simon
* I hope I will find some time to to contribute to RCOMM this year and present our work.
radone
that sounds cool! But if the process is designed by GP, it should not be a big problem that it clutters up the design perspective - after all the user will not really look at it, so you can go with 40 subprocesses. That sounds like the most reasonable idea to me.
Best,
Simon