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
3D viewer (underneath main) has feature to select connecting neurons by spatial position, which are within a Euclidean distance from active node. To precisely select partners on specific parts of a skeleton, currently I am having to trial and error different nanometre distances (and upstream/downstream filtering) and post hoc cross-reference which partners I expected to see.
It would be great to instead visualise, seamlessly in the 3D viewer, what a proposed Euclidean radius around the active node would look like, such that we can be certain that we'll obtain the desired partners. Hopefully this, or a feature which does something roughly along these lines, won't be difficult to implement. Thanks!
The text was updated successfully, but these errors were encountered:
The spatial select dialog now adds a transparent green sphere to the 3D
Viewer to visualize the currently set selection radius. The sphere is
updated accordingly when the radius changes in the dialog.
Fixes#2247
Hi @swilson27, that's a good suggestion. I just added this feature to the dev branch. The dialog now adds a transparent green sphere around the active node with the radius set in the dialog:
3D viewer (underneath main) has feature to select connecting neurons by spatial position, which are within a Euclidean distance from active node. To precisely select partners on specific parts of a skeleton, currently I am having to trial and error different nanometre distances (and upstream/downstream filtering) and post hoc cross-reference which partners I expected to see.
It would be great to instead visualise, seamlessly in the 3D viewer, what a proposed Euclidean radius around the active node would look like, such that we can be certain that we'll obtain the desired partners. Hopefully this, or a feature which does something roughly along these lines, won't be difficult to implement. Thanks!
The text was updated successfully, but these errors were encountered: