Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

stackImagePositionSynchronizer should only synchronize images on approximately the same plane

See original GitHub issue

I’ve had a number of users report to me directly that the stackImagePositionSynchronizer exhibits unexpected behavior. For example:

  • Two axial stacks
  • Two coronal stack

When scrolling one of the axial stack’s, I would expect the other to update it’s image to the closest slice. I would expect both coronal stack’s, because their for a different orientation, to remain on their current image.

Unfortunately, in some instances, we stacks in other orientations “jump” to a new image. Often the first or last one in their stack.

We can accomplish this by updating the synchronizer to discount images that aren’t in the same orientation. I think the math here is making sure the row dot product and column dot product are ~1 for the two images being compared (the source image, and each target image in the stack)

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:2
  • Comments:10

github_iconTop GitHub Comments

racacerecommented, Nov 5, 2021

Hi @ranasrule. Yesterday we had some problems with our Gitlab server, now it’s back online. Please try again, sorry for the inconveniences.

racacerecommented, Jan 3, 2022

Hi @ranasrule,

I’m very sorry for the response delay. The commit mentioned above, is our implementation of the solution to the scroll synchronization error between viewports. In brief, we added a sync botton to the toolbar when two or more viewports are active and that component has the needed logic to sync the viewports in a correct way.

The error that you described earlier is because we use a custom field in the ohif settings that indicates the study instance UID that you want to visualize, here are an example of this settings:

  servers: {
    dicomWeb: [
        name: 'SomeName',
        wadoUriRoot: '',
        qidoRoot: '',
        wadoRoot: '',
        qidoSupportsIncludeField: true,
        imageRendering: 'wadouri',
        thumbnailRendering: 'wadouri',
        enableStudyLazyLoad: true,
        supportsFuzzyMatching: true,
        studyInstanceUids: [

Best regards.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Sub-Frame Synchronization in a Smartphone Camera Network
SocialSync is a sub-frame synchronization protocol for cap- turing images simultaneously using a smartphone camera network. By synchronizing image captures ...
Read more >
Ideal Photographs And Radiographs
Natural head position with eyes looking forward. • Entire head and neck ... Approximate center of frame ... Occlusal plane should be horizontal...
Read more >
AN377 Timing and Synchronization in Broadcast Video
Since synchronization of the video signal is lost during storage, it must be re-synchronized to the studio's master sync generator before moving ...
Read more >
FTIR chemical imaging using focal plane array–based systems
Focal Plane Array1 (FPA) detectors allow for the simultaneous acquisition of an n by n number of spatially resolved spectra (where n =...
Read more >
Glossary of Film Terms | UWG
2D computer animation: Digitally generated series of images that give the ... in the image, as when dialogue is out of synchronization with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found