We're Hiring!

Combine_Images.py code question

General user discussion about using the OMERO platform to its fullest. Please ask new questions at https://forum.image.sc/tags/omero
Please note:
Historical discussions about OMERO. Please look for and ask new questions at https://forum.image.sc/tags/omero

There are workflow guides for various OMERO functions on our help site - http://help.openmicroscopy.org

You should find answers to any basic questions about using the clients there.

Combine_Images.py code question

Postby austinMLB » Thu Aug 23, 2018 8:39 pm

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
austinMLB
 
Posts: 19
Joined: Wed Jul 25, 2018 3:26 pm

Re: Combine_Images.py code question

Postby wmoore » Mon Aug 27, 2018 9:15 am

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.
User avatar
wmoore
Team Member
 
Posts: 674
Joined: Mon May 18, 2009 12:46 pm


Return to User Discussion

Who is online

Users browsing this forum: No registered users and 1 guest