Page 1 of 1

Combine_Images.py code question

PostPosted: Thu Aug 23, 2018 8:39 pm
by austinMLB
I have found the Combine_Images.py code to be very helpful, and I have used several ideas from that code in a related script. In that original code, the function scripts_utils.upload_plane_by_row(...) is used. I'm interested in knowing any pros/cons/differences of that function as compared to scripts_utils.upload_plane(...). In my particular case, I am seeing a significant performance improvement if I use the upload_plane(...) instead of upload_plane_by_row(...). Is there a motivation for choosing upload_plane_by_row(...) that I should consider in my script?
Thanks for any advice,
MLB

Re: Combine_Images.py code question

PostPosted: Mon Aug 27, 2018 9:15 am
by wmoore
Hi,

I can't tell you why we originally chose upload_plane_by_row().
One advantage it may have in some cases is where the image is quite large and an whole plane is expensive to handle as one. However, for big (tiled) images you need to use setTile() anyway, so I don't think we'd need upload_plane_by_row().

I'll investigate and propose updating this in the Combine_Images script.

Regards,

Will.