Open Microscopy Environment

Hi all,

Uploaded single SVS format image show 3 set of images as a series 1 series 2 and series 3.
Jpeg image uploading works good.

Single SVS uploading replicate 3 Series image.

Screen shot attached.

Many Thanks

What you're seeing here is the 3 images that are stored within the SVS file at different dimensions.
One image will be the full-sized image, and the others will be a smaller image and a thumbnail.

Since they all come from the same physical SVS file, it's not possible to E.g. delete one of them to free up space etc.

Hi,

we have one more issue with svs file, here with we attach the screen shot.During image preview we received this message in browser

here we attached one more screenshot

That's all most unfortunate, thank you for reporting the problem. We would like to try to reproduce it at our end. Would you be able to upload the problem image file and the zipped up contents of your server's var/log/ directory to http://qa.openmicroscopy.org.uk/qa/upload/?

Cheers,
Mark

Hi,

Kindly check the qa = 18847
we sent the log files.

Hi,

Thank you for submitting your files.

Unfortunately there seems to have been a misunderstanding on the location of the log files.
It would be great if you could upload the OMERO log files, and you can identify the folder location for the same by using the following command,

$bin/omero admin diagnostics
In your OMERO server. (Assuming you have access to this system)

You should get an output as shown in the following link,
https://docs.openmicroscopy.org/omero/5 ... iagnostics

If you could upload the files from the “Log dir” path, that would help us troubleshoot the issue in better detail.
Please let us know if you have any trouble on this front.

Best,
Balaji

Hi,

Kindly check qa = 18850 (new)
we uploaded the log of omero

And kindly deleted the previous log file

and here with we attach the omero admin diagnostics output in the txt file

Hi,

Thank you for sharing your files again.

It does look like a memory issue, (going by the log messages and the report from “bin/omero admin diagnostics”)
Modifying the configuration to allocate 'adequate' memory to the server, should potentially fix your issue.

Please take a look at the following link,
https://docs.openmicroscopy.org/omero/5 ... ments.html
This gives a brief overview of the hardware and memory requirements for a production server (within the boundaries mentioned).

Please use the following link to monitor and configure memory in your production server,
https://docs.openmicroscopy.org/omero/5 ... mance.html

And please take a look at the following link,
https://github.com/openmicroscopy/prod- ... r.yml#L311
This is the configuration we use for our demo server (https://demo.openmicroscopy.org/).

Hope that helps.

Best,
Balaji

Hi,

Kindly suggest the config file location and procedures, i looked the doc links but its not helpful.
Any specific file or config changes
kindly guide to solve this issue