Not sure if something has been done in the last 10 hours or so, but now all unsegmented segments gets fluorescent green when howering over them in 2d. (Very distracting)
The blackout bug still there
Find path looks to be working.
yeah, find path works now!
this exists in BANC as well (at least for me, idk if it happens for anyone else) but in both BANC and now in Pyr for reasons I do not understand why but quite frequently when I split/before/during the Hide Segment ID 0 option in render gets unselected w/o me having unclicked it, I’d like it to stay selected xP
forums wont allow me to upload the vid. directly so here’s a vid. of the thing happening: Recording 2025-02-20 151341.mp4 - Google Drive
This seems to be related to the segment 0 issue that Nseraf mentioned as well. For now you’ll just have to keep reclicking the segment 0 box until we can get a fix. Chris is still working out some of the kinks from the recent update so it may take a little bit, but we’re aware of these issues! Thanks for your patience!
As I can identify it (and I could be wrong) every time you split something or you select a segment to be split from the rest of the cell (red or blue) and then clear it (button bottom left corner) then in either/both cases the segment ID 0 thingy gets deselected.
But the -perhaps- good thing is that most likely the same bug that affects this in Pyr is most likely the same bug in BANC.
ok after further investigation I know exactly how this happens:
- you click “c” to split/cut.
- you click a segment for red (or blue it doesnt matter which colour goes 1st for this bug, whether you do red > blue or blue > red it’s the same thing). Immediately after that 1st segment click the seg ID 0 gets unselected automatically. Hereafter if you select blue (or red if its your 2nd colour) and submit all is fine. Upon completion of the split the segment ID 0 gets automatically reelected.
- but if instead you click clear (w/o selecting the 2nd colour and submitting) and/or if you select the 2nd colour and then clear w/o submitting.
voila segment ID 0 does not get automatically reselected and you need to do it manually.
Possible solutions:
→ remove split being able to deselect and/or reselect that option, making it effectively able to change only manually. (idk what purpose it serves to even have it deselected in either split or merge considering ID-less segments cannot be split or merged into/from anything in the 1st place.)
or
→ remove the option entirely from being clickable by humans and remove it from split/merge as we cant do anything w/ unsegmented IDs since again we cant do anything with those, and just make it perma enabled in the background w/o us or split being able to enable/disable it.
That actually make sense, and explain why unsegmented stuff get hightlighted in cut mode. what function this has is a open question.
Thanks for tracking this down and figuring out how to reproduce the issue Nseraf!
And yeah, I’m with you annkri – I also have no idea why it’s a thing/function
i am getting a bug where both segments get deleted after splitting a segment ( not in segment list) when clicking on the segment again in 2d it come back as splitted.
when pasting this link neuroglancer a new tab it looks to work correctly for a short time but soon get the bug again.
Here is some of the error messages i get
https://play.pyr.ai/#!middleauth+https://global.daf-apis.com/nglstate/api/v1/4657772223266816
i’ve noticed this bug as well (in banc as well as pyr) since a bit before KK’s comment here: [addon] Undelete (BANC) - #9 by Krzysztof_Kruk I think it has something to do w/ neuroglancer’s new version and whatever they changed in there.
Will pass on this info.
I think, this one might’ve been the fault of the Undeleted script (as @Nseraf correctly suggested). I’ve just released a new version and now it’s should work fine.
wasnt trying to suggest, only point to a time frame (i thought it was the update causing it) lol
ok, but you’ve pointed in the right direction
well, that’s all good then, xD
anyone else unable to select anything in 2D or see 3D?
vid desktop capture of what I’m experiencing:
yes, looks like i also have that bug
Hi All, is this bug still happening?
We had some issues with data storage for some datasets on Friday afternoon. I believe it is fixed now as of yesterday. Please let us know!
hi, it’s ok now.