something like this is ‘too small’ as I understand it. Everything else is outside of the dataset.
3 Likes
Thanks both, i modified my logs !
1 Like
I put this one as “Too Small”, good ?
https://play.pyr.ai/#!middleauth+https://global.daf-apis.com/nglstate/api/v1/5947784516599808
Not sure, how others would do, but I’d mark it as an MF. After all, if’s possible to identify it (many vesicles, synapses with those “bubbly” neurons) and has some length of the axon.
2 Likes
i would also mark it as a MF
2 Likes
I’d do the same.
2 Likes
I think too small is basically only for when the only thing in the dataset is a bouton or less than a whole bouton and no axon or similar.
2 Likes
Would you say that’s an MF ? It is small and directly on the main, but it is connected to a bubbly, so i would say yes
https://play.pyr.ai/#!middleauth+https://global.daf-apis.com/nglstate/api/v1/5492482306473984
1 Like
Yes, I’d say, it’s an MF. It has high density of the neurotransmitter vesicles and also synapses with the bubbly one in this sort of a jig-saw puzzle way, unlike other synapses, where they only (almost) touch each other.
3 Likes
Would you label this one as too small or MF? If it was the 1/3 of a bouton alone I’d be more certain abt TS, but it has at least some small part of an axon so now Idk.
1 Like
I’d label it as an MF. I have this rule (that I’ve just created, lol), that if the axon is longer, than the longest dimension of the bouton, mark it as an MF.
3 Likes
lol, fair enough, thnx.
1 Like
Hi all,
Re: questions about what is considered “Too Small.” I inquired, and this label should be given to anything that meets the following requirements:
Case 1: If the segment has only one bouton and it is cut off at the edge of the dataset (partial bouton), it should be considered “Too Small,” even if there is some amount of axon emerging from the bouton.
Case 2: If the bouton is fully intact, it should still be considered “Too Small” if there is no axon branch emerging from it.
Anything else (cells with at least 1 fully intact bouton and some amount of axon branch) should be given the MF categorization.
Hope this helps clarify things! Sorry for some confusion earlier. Also no need to revisit cells that were previously labeled, please just use these definitions moving forward. TIA!
6 Likes
i have seen some cells that have a half button but, axon still crossing trough the whole dataset. so after new definition it should be labeled too small?
3 Likes
If it’s like KK says “if the axon is longer, than the longest dimension of the bouton” then mark it as MF.
A “small amount of axon” is something that is just barely poking into the dataset.
This would be marked as a MF even though the bouton is cut-off: neuroglancer
If in doubt, better to mark it as a MF than as “Too Small” if you can determine it’s an MF bouton (attached to the thorny excrescenes or “bubblies” (thanks Kfay - I like this name, better than the scientific one I struggle to pronounce!), has many vesicles, etc.).
2 Likes
A question about the initial mergers:
if the merger consists of an obvious MF and a branch, that doesn’t have any boutons and may or may not be an MF, should we still trace that branch or just remove it?
If it’s attached to the initial branch then you should trace it until you can determine if it’s a MF. If it is, complete it.
1 Like
This is a question for as much BANC as Pyr:
Is there a shortcut/way for me to right click/select a segment in 3D that will also ‘scroll’ to the same segment in the list to the right if the list is too long for the segment to be immediately visible? (like in the pic)
For example if I can somehow right click the pink segment (red arrow) in 3D and have it also scroll and be highlighted in that list?
(I’m breaking up a mega merger remnant in BANC and this’d be immensely useful lol)
I am not aware of any functionality that allows you to jump directly to the spot in the list like that. I agree that it’s an issue and have also had trouble with it in certain circumstances.
To help minimize this issue you can use annotations to label important segments and use SHIFT+DOUBLE CLICK when removing segments you don’t want to keep from having many extraneous hidden segments in your list.
1 Like
in this case hidden segments ‘can’t’ be removed as they are segments that I have de-tached from overall mergerness, they are ‘single’ (nothing that doesnt belong attached on it) but arent proofread/completed. So, removal isn’t an option, 
. But, thanks for the reply, I’ll add it on the suggestions thread.