Task #11619 (closed)
Opened 11 years ago
Closed 10 years ago
Bug: rendering setting on import of exported image
| Reported by: | cblackburn | Owned by: | jburel |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.1.0 |
| Component: | Insight | Version: | 5.0.0-beta1 |
| Keywords: | n.a. | Cc: | pwalczysko |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
While testing an unrelated PR I did the following using gretzky:
dist/bin/omero import ../../Images/dv/mt1_R3D_D3D.dv ... Image:6452 dist/bin/omero export --file mt.ome.tif Image:6452 dist/bin/omero import mt.ome.tif ... Image:6453
On comparing the two images in Insight it was noticeable that the rendering settings of the re-imported image were different to the originally imported image on just one channel. See attached screenshot. I'm not sure if this is an Insight or export problem.
Attachments (3)
Change History (7)
Changed 11 years ago by cblackburn
comment:1 Changed 10 years ago by jburel
comment:2 Changed 10 years ago by pwalczysko
Repeated the same workflow, not using cmd line, but Insight to change and save the rendering settings on this dv image. Then exported as one-tiff. Re-imported the one-tiff using Insight. Went to Web. The situation was identiical with the one in Insight (see screenshot). I was working on howe.
Changed 10 years ago by pwalczysko
comment:3 Changed 10 years ago by jburel
- Milestone changed from 5.0.0-beta2 to 5.0.0-beta3
- Sprint OMERO 5 Beta 2 (1) deleted
comment:4 Changed 10 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
The problem has been fixed with recent changes in the RE (5.1.0-m1) see screenshot
Changed 10 years ago by jburel
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
what was the result in Web?