You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is additional math included in the VMR LUT tables (here) used by VMRouterCM and TrackletProcessorDisplaced which is specific for the prompt and not displaced tracking. There is a note that mentions this difference is only because the displaced tracking doesn't used combined modules, but combined modules have since been implemented and this comment has not been addressed. Should we now use the same VMR LUT tables as the prompt tracking? What does this actually do? It would be great if someone could look into this.
There is additional math included in the VMR LUT tables (here) used by VMRouterCM and TrackletProcessorDisplaced which is specific for the prompt and not displaced tracking. There is a note that mentions this difference is only because the displaced tracking doesn't used combined modules, but combined modules have since been implemented and this comment has not been addressed. Should we now use the same VMR LUT tables as the prompt tracking? What does this actually do? It would be great if someone could look into this.
This task is also included on the displaced tracking project list.
The text was updated successfully, but these errors were encountered: