Skip to main content
Best Answer

The right way to branch the workflow

  • March 20, 2019
  • 4 replies
  • 25 views

Forum|alt.badge.img

Hi!

I'm sorry if the question seems trivial, but I didn't found a turnkey solution

I have two grids and a condition that subsequents flow of an algorithm depends on minimum value of mathematical difference between them. If it is larger than a certain value I must wright both of initial grids to defined place, if it's smaller - than do nothing.

Of course, there is no problem to use tester to RasterBandMinMaxExtractor. But on the output port I will get a raster with calculated difference but not the initial rasters. I can use result as a clipper for required rasters, but maybe there is more right and elegant way to branch an algorithm?

Thank you!

Best answer by jdh

You could use a featureMerger to add the results back onto the original features.

 

 

You could use a rasterBandCombiner to add the difference raster onto the original rasters.

 

 

Unfortunately there is no reliable way to proceed without merging the results back onto the original features without breaking up the workspace into multiple child workflows. (You could do the analysis and then use a workspace runner to launch the appropriate workspace for further processing).

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

jdh
Contributor
Forum|alt.badge.img+40
  • Contributor
  • Best Answer
  • March 20, 2019

You could use a featureMerger to add the results back onto the original features.

 

 

You could use a rasterBandCombiner to add the difference raster onto the original rasters.

 

 

Unfortunately there is no reliable way to proceed without merging the results back onto the original features without breaking up the workspace into multiple child workflows. (You could do the analysis and then use a workspace runner to launch the appropriate workspace for further processing).

 


takashi
Celebrity
  • March 21, 2019

I'm unclear what the point of the question is, but if the point is how to restore the original rasters after some operations on them, the RasterExtractor and the RasterReplacer might be a solution.


Forum|alt.badge.img
  • Author
  • March 21, 2019

I'm unclear what the point of the question is, but if the point is how to restore the original rasters after some operations on them, the RasterExtractor and the RasterReplacer might be a solution.

Thanks, takashi! The point of the question is to find out the methodologically correct way to branch the algorithm depending on what result will be obtained at a certain step regardless of the nature of the input data and action at the verification step. Some kind of analogue of precondition in Arcmap Model Builder , maybe.


Forum|alt.badge.img
  • Author
  • March 21, 2019

You could use a featureMerger to add the results back onto the original features.

 

 

You could use a rasterBandCombiner to add the difference raster onto the original rasters.

 

 

Unfortunately there is no reliable way to proceed without merging the results back onto the original features without breaking up the workspace into multiple child workflows. (You could do the analysis and then use a workspace runner to launch the appropriate workspace for further processing).

 

Thank you, jdh! It seems like a workspace runner is a good decision!