<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Niko,
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div class="">congratulations to the release and many many thanks for all the effort!</div>
</blockquote>
<div class=""><br class="">
</div>
On behalf of the team, thanks!</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">I do have one small question though: as discussed with J-M and Sebastien during last year's meeting in Paris, it would be extremely helpful if the Python API call for importing an image into OMERO would report the ID of the new image after a successful
import.<br class="">
<br class="">
We are currently in the process of shifting one processing workflow to use OMERO as the *only* backend, meaning the files being processed are managed by OMERO, fully automated processing is happening on some network nodes and the results will be re-uploaded
into OMERO. For being able to create meaningful links between numerical / human readable results and images, it is crucial to be able to attach them to an image imported into OMERO - which does require the ID...<br class="">
<br class="">
The same holds for the OMERO-connector integrated into the latest HRM release [1]. For being able to upload parameter settings, coloc results, statistics etc. along a deconvolved dataset from the HRM, we'd need to know the ID of a newly created image.<br class="">
<br class="">
<br class="">
Does 5.2.2 expose the ID via its Python API already?<br class="">
</div>
</blockquote>
<br class="">
</div>
<div class="">Have you looked at some of our Python integrations tests, for example:</div>
<div class=""><br class="">
</div>
<div class=""><<a href="https://github.com/openmicroscopy/openmicroscopy/blob/develop/components/tools/OmeroPy/test/integration/clitest/test_import.py#L674" class="">https://github.com/openmicroscopy/openmicroscopy/blob/develop/components/tools/OmeroPy/test/integration/clitest/test_import.py#L674</a>></div>
<div class=""><br class="">
</div>
<div class="">Here we capture the stdout and stderr. The Pixels IDs are in stdout (just the IDs each on a new line), for example:</div>
<div class=""><br class="">
</div>
<div class="">“</div>
<div class="">9</div>
<div class="">
<div class="">10</div>
<div class="">11</div>
<div class="">12</div>
</div>
<div class="">"</div>
<div class=""><br class="">
</div>
<div class="">And the Image IDs can be parsed from stderr, which is, for example:</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">“</div>
<div class="">Imported pixels:</div>
<div class="">Other imported objects:</div>
<div class="">Fileset:6</div>
<div class="">Image:9</div>
</div>
<div class="">
<div class="">Image:10</div>
<div class="">Image:11</div>
<div class="">Image:12</div>
</div>
<div class="">“</div>
<div class=""><br class="">
</div>
<div class="">Is this the sort of thing you are after or are you looking at getting these IDs at some other point in your workflow?</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class=""><br class="">
</div>
<div class="">Colin</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On 29 Feb 2016, at 16:23, Niko Ehrenfeuchter <<a href="mailto:nikolaus.ehrenfeuchter@unibas.ch" class="">nikolaus.ehrenfeuchter@unibas.ch</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Dear all,<br class="">
<br class="">
congratulations to the release and many many thanks for all the effort!<br class="">
<br class="">
I do have one small question though: as discussed with J-M and Sebastien during last year's meeting in Paris, it would be extremely helpful if the Python API call for importing an image into OMERO would report the ID of the new image after a successful import.<br class="">
<br class="">
We are currently in the process of shifting one processing workflow to use OMERO as the *only* backend, meaning the files being processed are managed by OMERO, fully automated processing is happening on some network nodes and the results will be re-uploaded
into OMERO. For being able to create meaningful links between numerical / human readable results and images, it is crucial to be able to attach them to an image imported into OMERO - which does require the ID...<br class="">
<br class="">
The same holds for the OMERO-connector integrated into the latest HRM release [1]. For being able to upload parameter settings, coloc results, statistics etc. along a deconvolved dataset from the HRM, we'd need to know the ID of a newly created image.<br class="">
<br class="">
<br class="">
Does 5.2.2 expose the ID via its Python API already?<br class="">
<br class="">
<br class="">
Many thanks,<br class="">
~Niko<br class="">
<br class="">
<br class="">
[1] <a href="http://www.huygens-rm.org/wp/?p=193" class="">http://www.huygens-rm.org/wp/?p=193</a><br class="">
<br class="">
<br class="">
On 29.02.2016 16:17, Jean-Marie Burel (Staff) wrote:<br class="">
<blockquote type="cite" class=""><br class="">
Dear All,<br class="">
<br class="">
Today we are releasing OMERO 5.2.2, a bug-fix release which also<br class="">
introduces some new client features. Improvements include:<br class="">
<br class="">
* display of ROI masks in OMERO.web image viewer<br class="">
* display of OMERO.tables data for Wells in the OMERO.web right hand panel<br class="">
* 'Populate Metadata' script to enable generation of OMERO.tables for<br class="">
Wells is now usable from both OMERO.web and OMERO.insight (note this is<br class="">
still in development and has some limitations)<br class="">
* measurement tool fixes<br class="">
* fixed pixel size metadata and scalebar in OMERO.web image viewer for<br class="">
images with pixel size units other than micrometer<br class="">
* fixed OMERO.web handling of turning off interpolation of pixels<br class="">
* previous and next buttons fixed in OMERO.web image viewer<br class="">
* delete and change group performance improvements<br class="">
* better handling of dates in search<br class="">
* client support for map annotations in OME-TIFF<br class="">
* disabled orphaned container feature<br class="">
* OMERO.web clean-up to remove obsolete volume viewer<br class="">
<br class="">
Developer updates include:<br class="">
* Python API examples for creating Polygon and Mask shapes<br class="">
* Python API example for "Populate Metadata" to create OMERO.tables for<br class="">
Wells<br class="">
* OMERO.tables documentation extended<br class="">
* updated 'What's New for developers' to clarify that 'pojos' has been<br class="">
renamed as 'omero.gateway.model'<br class="">
* dynamic scripts functionality documented<br class="">
* dynamic loading of omero.client server settings into HTTP sessions<br class="">
<br class="">
System administrator updates include:<br class="">
* clarification of OMERO.web documentation for nginx deployment,<br class="">
including an experimental solution to resolve download issues<br class="">
* documentation of hard-linking issues for in-place import on linux systems<br class="">
<br class="">
This release also upgrades the version of Bio-Formats which OMERO uses to<br class="">
5.1.8. For more information see<br class="">
<a href="https://www.openmicroscopy.org/site/support/bio-formats5.1/about/whats-new.html" class="">https://www.openmicroscopy.org/site/support/bio-formats5.1/about/whats-new.html</a>.<br class="">
<br class="">
Note that the OMERO Virtual Appliance has been discontinued and will not<br class="">
be updated for version 5.2.2 or any later releases.<br class="">
<br class="">
The software is available at:<br class="">
<a href="http://downloads.openmicroscopy.org/omero/5.2.2" class="">http://downloads.openmicroscopy.org/omero/5.2.2</a><br class="">
<br class="">
Upgrade information is at<br class="">
http://www.openmicroscopy.org/site/support/omero5.2/sysadmins/server-upgrade.html.<br class="">
<br class="">
Regards,<br class="">
<br class="">
The OME Team<br class="">
<br class="">
The University of Dundee is a registered Scottish Charity, No: SC015096<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
ome-devel mailing list<br class="">
ome-devel@lists.openmicroscopy.org.uk<br class="">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel<br class="">
<br class="">
</blockquote>
<br class="">
-- <br class="">
Niko Ehrenfeuchter | Image Analysis Specialist | Biozentrum, University of Basel | Klingelbergstr. 50/70 | CH-4056 Basel<br class="">
Phone: +41 (61) 26 72673 | <a href="mailto:nikolaus.ehrenfeuchter@unibas.ch" class="">
nikolaus.ehrenfeuchter@unibas.ch</a> | <a href="http://www.biozentrum.unibas.ch" class="">
www.biozentrum.unibas.ch</a> | <a href="http://www.microscopynetwork.unibas.ch" class="">
www.microscopynetwork.unibas.ch</a><br class="">
_______________________________________________<br class="">
ome-devel mailing list<br class="">
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" class="">ome-devel@lists.openmicroscopy.org.uk</a><br class="">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<span style="font-size:10pt;">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>