Why so many bugs compared to the original OsiriX?

[achir...@gmail.com]

Currently, it is not usable as a professional DICOM viewer.

[Phillip Jackson]

Hello - there are numerous folks using it who presumably haven't experienced the issues you are.  Can you articulate the issues you are experiencing?

On Fri, Mar 20, 2015 at 11:33 AM, <achir...@gmail.com> wrote:

Currently, it is not usable as a professional DICOM viewer.

--
You received this message because you are subscribed to the Google Groups "Horos Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to horos-projec...@googlegroups.com.
To post to this group, send email to horos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/horos-project/05d0517e-c296-458c-bf86-bf41ee6da000%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[achir...@gmail.com]

At least 4 "Spinning Beach Balls of Death" or crashes in less than 1 hour (but it's maybe my DICOM files, although it doesn't crash in OsiriX).

And a major issue: the Left/Right is flipped when you open the "3D-MPR" window : imagine if a surgeon uses Horos for pre-surgical planning : wrong side for a kidney or knee surgery?

[Phillip Jackson]

The presentation in 3P MPR is inconsistent with OsiriX, however the labelling of the images is correct.  We'll get this documented and reviewed right away.

Can you provide details regarding your DICOM data?  Perhaps an anonymized data set?

To view this discussion on the web visit https://groups.google.com/d/msgid/horos-project/b90a7ee6-28e3-4438-8c4a-8910bc80b7f9%40googlegroups.com.

[how...@xmission.com]

On Saturday, March 21, 2015 at 1:30:57 AM UTC-6, achir...@gmail.com wrote:

At least 4 "Spinning Beach Balls of Death" or crashes in less than 1 hour (but it's maybe my DICOM files, although it doesn't crash in OsiriX).

 

...........

I have noticed very slow opening of windows and, sometimes, an associated (temporary) Spinning Beach Ball as well.

On occasion, Horos was rendered "non-responsive" and I had to kill it. 

When I see this, Console shows (two examples):

....

3/21/15 11:46:57.058 AM WindowServer[101]: disable_update_timeout: UI updates were forcibly disabled by application "Horos" for over 1.00 seconds. Server has re-enabled them.

3/21/15 11:46:57.197 AM WindowServer[101]: common_reenable_update: UI updates were finally reenabled by application "Horos" after 1.14 seconds (server forcibly re-enabled them after 1.00 seconds)

3/21/15 11:46:57.245 AM Horos[6850]: start loading multiple thread

3/21/15 11:46:58.559 AM WindowServer[101]: disable_update_timeout: UI updates were forcibly disabled by application "Horos" for over 1.00 seconds. Server has re-enabled them.

3/21/15 11:46:59.325 AM Horos[6850]: end loading

3/21/15 11:46:59.683 AM WindowServer[101]: common_reenable_update: UI updates were finally reenabled by application "Horos" after 2.13 seconds (server forcibly re-enabled them after 1.00 seconds)

..........

3/21/15 11:50:34.909 AM ReadKit[2842]: Sync timer fired

3/21/15 11:50:38.001 AM Horos[6850]: start loading multiple thread

3/21/15 11:50:39.074 AM WindowServer[101]: disable_update_timeout: UI updates were forcibly disabled by application "Horos" for over 1.00 seconds. Server has re-enabled them.

3/21/15 11:50:39.519 AM WindowServer[101]: common_reenable_update: UI updates were finally reenabled by application "Horos" after 1.45 seconds (server forcibly re-enabled them after 1.00 seconds)

3/21/15 11:50:41.664 AM Horos[6850]: end loading

.........

When the operation involved a drag between two panes in the 2-D Viewer Window, which was slow, I see the following:

3/21/15 11:58:20.354 AM Horos[6850]: prepareForDragOperation

3/21/15 11:58:21.484 AM WindowServer[101]: disable_update_timeout: UI updates were forcibly disabled by application "Horos" for over 1.00 seconds. Server has re-enabled them.

3/21/15 11:58:21.700 AM WindowServer[101]: common_reenable_update: UI updates were finally reenabled by application "Horos" after 1.22 seconds (server forcibly re-enabled them after 1.00 seconds)

3/21/15 11:58:21.703 AM Horos[6850]: start loading multiple thread

3/21/15 11:58:21.887 AM Horos[6850]: draggingEnded

3/21/15 11:58:25.122 AM Horos[6850]: end loading

....................

Do you see the same ?

(I'll also submit this issue at horosproject.org.)

Howard

[Rafael Cruz]

I do agree that "Left/Right is flipped when you open the "3D-MPR" window" is a "major issue", but its not related to Horos itself.

We have here the same behavior using OsiriX MD 2.8.5 (OsiriX 5.8.5) after we updated to Yosemite. My hypothesis is that this is related to Yosemite. I'm not sure.

Besides that, we should note that OsiriX MD performance under Yosemite ir poor. Horos performance should be compared to OsiriX 5.9, under the same circumstances.

Yes, Alex Bettarini´s OpenJPEG implementation is slower, as he points:

​"​

The official OsiriX 64-bit version (not free) is using the Kakadu library for JPEG 2000. That library is not free, so I won't be using it. The alternative is to use OpenJPEG. Opening some large series won't be as fast as with the official version, but that's about the only difference I am aware of.

​"​

Rafael Cruz

rfl...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/horos-project/CACw9gbTgVBWty_XXxb_cytMcJwDKCcVPKt0dfYfGRSd6K8pARQ%40mail.gmail.com.