Using the appId, the reactor will run the app using the inputs given. Based off of the app's state.json, the reactor should know which reactors to call, the input/output variables to track, and the order in which to run the tabs (can be found in the executionOrder array).
The pixel should return the final output of the app and the appropriate PixelDataType as a NounMetadata object. Return an exception if the execution of the pixel list fails at some point.
Existing
See how query.state.ts._processRun and cell.state.ts._processRun methods in semoss-ui function. One way to approach this reactor would be to emulate this behavior on the backend, call each reactor separately.
Alternatively, if we are able to extrapolate the master pixel list we can send the whole recipe to the pixel runner, kind of like stored insights.
Description
This reactor will take the following inputs:
Using the appId, the reactor will run the app using the inputs given. Based off of the app's state.json, the reactor should know which reactors to call, the input/output variables to track, and the order in which to run the tabs (can be found in the executionOrder array).
The pixel should return the final output of the app and the appropriate PixelDataType as a NounMetadata object. Return an exception if the execution of the pixel list fails at some point.
Existing
query.state.ts._processRunandcell.state.ts._processRunmethods in semoss-ui function. One way to approach this reactor would be to emulate this behavior on the backend, call each reactor separately.Reference
193
Tasks