New RangeMask needed in ProcessContainer for each batched image.

[H2ologg]

First post!  The PixInsight community has been so vast and helpful I haven’t found the need to request help until now.

I'm processing a time lapse of solar prominence action consisting of 80+ images. I've created a ProcessContainer with all the process steps involved and am attempting  to apply these steps to all images. In the processes I create a rangemask to protect/ enhance the sun’s surface and the prominences.

You probably can guess where I’m going here.  The rangemask is unique to every new image in the batch since the prominence, disk alignment and surface feature change over the two hour period of capture.  When I run the ProcessContainer to the batched ImageContainner I find the original mask is used for each new solar image and further ProcessContainer steps needing their own specific rangemask end up producing unpredictable results.

 In short, Is there some source code that will allow me to create a specific new RangeMask (same parameters for every image) for every new image in the ImageContainer?

I’d hate to have to manually apply a RangeMask to every solar image when a process needs one.

Lazy me.

Thanks I hope,
Dan

[ngc1535]

So, if you run just rangemask on your 80 images you can generate 80 unique masks with image container- and then you would apply each mask to the image by double clicking on the "mask" field in another (subsequent) image container. Finally you would run whatever the other processes were on your now uniquely masked images. Not quite automated... but would this work?

-adam

[H2ologg]

Thanks Adam,
I was afraid of that.  Making several ImageContainers and several ProcessConainers to make and use a unique rangemask with identical build parameters for each solar image is what I must do then.

Masks must be handled/coded/ formatted in an alternate process condition for them not to be used generically as other processes are.

Thanks for your help.

Dan

[pfile]

since process icons are just xml files, you could use other utilities to generate them and then load them into the pi workspace... i sometimes generate calibration icons that way.

rob