Width and height are not equal stopping queue

[stevewcorey]

We have encountered an issue where the processing on mercure stopped because of a video - 1.2.276.0.7230010.3.1.3.0.846.1674249459.868844#US.X.1.2.276.0.7230010.3.1.4.531396936.67960.1677801057.619333.dcm
Mar 02 18:54:31 ip-172-31-72-121 python[1753]: Error: Width and height are not equal. Not supported by this module)

I need to know what configuration my customer has that would cause this and to understand why the queue stopping processing imagery? This should not have been a fatal error. I assume the module can be updated to handle this scenario but just need to know what should be changed.

[tblock79]

According to the log statement, it is an issue caused by the processing module that you have developed. It's not related to mercure itself. Thus, you need to check the code of your processing module.

[stevewcorey]

Makes perfect sense. Thank you so much. Now I know where to check. We are using the sample module that comes with a default installation of Mercure.

[tblock79]

Oh ok. Yeah, that example-inference module only supports images with identical width and height (because the test CNN had only been trained for square images). If your model supports other inputs, you can remove that constraint in line 29 of the file inference.py.

[stevewcorey]

That is fantastic. We will do that. Tobias, I am the CTO of a company called BabyFlix and we provide fetal ultrasound imagery live and on-demand to expectant familes. We have just recently deployed a DICOM solution to ingest content. We had an outside consulting firm help us deploy Mercure and that consultant has moved on. We never customized the the module but created a number of AWS lambda functions to help with the conversion of ingested content. Your background is really impressive. I was wondering if you would be available for a small engagement to talk about the strategic use of Mercure?

[tblock79]

We've noticed from the GitHub visitor logs that you have an instance of the mercure UI running in the public internet. That is very risky. The mercure UI has not been designed/hardened/tested for public internet exposure. It should only be used within a protected intranet environment.