-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BigWarp z offset issue in 2D mode #249
Comments
That's BigWarp dealing with it: if the source has a thickness of 1 slice, it is started as 2D, otherwise 3D. But there is a The most annoying part when dealing with 2d is if your sources have a z-offset, but you already know this... |
Ok, I did not know that BigWarp does that automatically.
will BigWarp still display such sources? |
BigWarp displays those sources, but at z = 0, so, you get a black image, unless the pixel size is above the z offset ... |
OK, that's an issue, I think (ping @bogovicj). Use case: alignment of TEM sections, which sit physically on top of each other (and may have thus a corresponding |
Thanks @tischi and @NicoKiaru
|
Yes, that's exactly it. And note that in the worst case scenario, the z offset may be different between the moving and the fixed source. If you go for some modification, I'd still like to be able to keep the default behaviour if possible: In ABBA, I'm shifting the source in Z to select the part I want the user to see (before starting BigWarp). |
I made some changes Bigwarp seemed to show the 2d sources correctly on start up, but it was possible to mess it up with the Specifically, @NicoKiaru
are you getting this on startup? if so, how? This is the demo I used to test things today: |
@bogovicj I tried your test (BigWarp 7.0.5), and we can't see the landmarks (unless they are made very big) because of the z offset. I'll open an issue in BigWarp as well |
@NicoKiaru
How do you in practice figure out whether you would like to launch
BigWarpLauncherCommand
in 2D?I have a feeling right now it is never launched in 2D?
Would it make sense to add a user parameter
boolean register2D
?In fact, what happens then if the sources actually are in 3D?
The text was updated successfully, but these errors were encountered: