Odd account behaviour, forum and play page

Eyewire Bugs
#1
Been making changes recently?

The forum didn't want to auto recognise me... and it seems that the score boards don't want to acknowledge my existence either.

I've just had to reset my password as the forum seemed to have no record of my account. That enabled me to log in to the forum, just going to test the project page.

Having said that, the interface feels much faster overall :)

Edit - has someone changed the loading behaviour for the image stacks..? The little loading spinner stays on the screen and no background image updates until the whole stack has loaded (or so it seems).

And the forum seems to be forgetting login information as well.

The scoreboards were working, they just didn't centre on my account name ... :)

Browser is latest Chrome.
#2

Forum didn’t recognise me either. I reset the password. I haven’t started playing yet although I noticed we have a new shade of blue… cool.

#3

The loading process feels a little different for me  (Mac Lion Firefox).  I used to start a new image, click up/down a few times, then do something else for a minute or two while it loaded. Now I’m not sure if those initial clicks are ‘turning on’ the upload process?  Even after waiting a while I still have to wait for individual frames to load.  I’ll keep on and see how things go - in case I am not understanding it.

#4

Sorry for lots of messages… but it does feel like something has gone a little haywire.  I know am finding that my mouse has a huge offset (half way across the image) to mark things. I reloaded eyewire and it came up with the same image and the same problem.  Hoping that these weird problems are an easy fix.

#5

In addition, people’s scores are missing from the starting page;


I’ve just tried to get it to load, and its just showing a small box saying ‘loading…’ To get any images, I have to reload the page… and most of the 3D reconstruction is missing.

Someone’s made a boo boo :slight_smile:

#6

Sorry guys, we had a bit of a crisis over the weekend.  The previous version failed pretty hard so we decided to push the updated version before it was 100% ready for prime time.  The good news is that you get the much faster upgraded version early.  The bad news is that it’s still quite buggy.  We’re aware of all these issues and we are working on them.  I’ll make a formal announcement in the next couple days once things have settled down a bit.  Thanks for alerting us to the problems you’ve been experiencing.  Sorry it’s been a bumpy ride!

#7

Thanks so much.  Great work you guys… I really love this project. It’s addictive.  Keeps me busy while the wind blows and the rain pours down here in New Zealand :slight_smile:

#8

FYI - left and right arrows for opacity control don’t seem to work now (slider is fine), and some tasks are breaking part way through - offsetting the cursor right across the screen and marking the wrong place.  

The good news - the “remember me” on login is now working for me for the first time. Thanks :slight_smile:

#9

It seems to be working much better now. Much more fluid operation; wonderful job.


The 3D widget didn’t work when I first loaded the page, but did for subsequent tasks. It just showed very small reconstructed sections (about 2 of them), but nothing else.

Edit - I’m still seeing the “load a large part of the stack” behaviour. It seems to occur if I attempt to scroll more that a couple of frames into an unloaded part of the stack. Previously it seemed to prioritise loading of parts that the user had visited before continuing with the rest, now it seems to try and just load the whole lot.

Is this the intended behaviour?

Also, when it decides not to load part of the stack, it won’t allow task completion either.




#10

I’m having much the same problems as others here. Two days ago it was telling me I didn’t exist. I abandoned it until today and now the login is working. (Nice touch on the spinning overview BTW.) But on some of the tasks I get the broken pointer about half way up the stack. It’ll go along just fine and then at some point it just decides that what I intend to select is on the other side of the frame.

Another oddity is the report a bug link. When clicked it still gives the box, takes input and seems to allow one to report (the message box goes away) but… the page freezes and nothing else will work after that. Have to close the tab and reload. Once reloaded all is fine. That is until the next hiccup.

Thanks for all the effort folks. All the improvements look good so far. Only a few bugs to work out.

Cheers

#11

Oh yeah, Win 7-64 latest firefox.

#12

@smalljude 

When you say the left and right arrows for opacity don’t work, can you make sure the opacity slider isn’t “selected”? That is, click somewhere else, on the instruction text for example, to remove focus from the opacity slider. Let me know if the keys still do not toggle the opacity.

@smalljude and @turing8
Painting far away from where you clicked (in this case) sounds like a new bug to me. If I understand correctly you’re saying it starts out OK, but as you page through slices, at some point it breaks and starts painting in a distant area. If this happens again, can you try reloading the page & see if the problem is reproducible? I haven’t been able to reproduce this problem myself yet. Also, if there are any things you’ve noticed that trigger this, that would also be helpful.

@backupelk
Part of the new code was switching the way pending image-load events are cancelled. Making this switch got rid of the flickering of images as you paged through slices, but it has also introduced a few mishaps where some requests aren’t cancelled. When this happens you end up having to wait for the whole volume to preload before you can continue. I’ll look into why this is happening.

@turing8
Yes, there are a number of things I couldn’t get hooked up before we pushed the latest code, one of which is the report-a-bug feature. I’ll work on getting this up within the next day.
#13

Hi, I just checked and I definitely don’t have the opacity slider selected. The behaviour I’m getting is simply an on/off opacity with the left and right arrows… the opacity doesn’t change gradually. If I select and use the slider then I can change it to any gradual change, but, when not selected I only get the on/off behaviour (hope that makes sense).

As far as the painting in the wrong area goes, yes you and @turing8 are describing exactly what I’m getting. Usually it’s a good half way through the image stack and then it will start painting somewhere far away. I’ve found that it is sometimes just one particular missing part of the neuron that will do it. I have tried many of these over several times, logged in and out and tried them again and I keep getting it.  I aborted several tasks that I just couldn’t complete because of it.  Unfortunately I can’t think of anything peculiar or of note that could trigger it. Some do and some don’t. I’ll keep my eye out.

#14

OK… not sure if this is helpful or not, but it appears that the offset occurs when I try to mark something in the area of the upper top left-hand side (roughly).  I can’t be sure that has been the case every single time, but it sure seems to be in the cases I’ve had this afternoon.

#15

So just FYI, the opacity thing is a feature not a bug.  We are trying it out this way because people thought that a toggle would be easier to use than a slider.  For the most part they only need 2 settings, on and off.  Please give it a try for a while and let us know how you like it.  You can still change the absolute level manually.

#16

Yes, again and I concur (mostly) with @smalljude. It happened again this morning. However, I noticed something, maybe a workaround for the time being. If you go ahead and color the part you want (or at least try, sometimes it just will not paint the spot you want) then deselect all the junk you didn’t want, it (again sometimes) will retain the selection you want and get rid of the junk. I’ve had to play around with it but was able to successfully complete the unit that did this. If when you get rid of the junk the part you want goes with it just go up or down a slide and try again. At least in this one case it worked for me.

#17

Oh yeah, almost forgot. There was another oddity concerning the 3D view. On one task I did it only showed two tiny dots in 3D but there was clearly more neuron in the unit than was shown. Any painting did not update in the 3D view either.

Thanks again.

#18

@turing8 Did that occur within the past 2 hours? I was just working on some caching stuff this morning and it  was causing meshes to not load properly for a bit. That particular issue should be fixed now.


#19

FYI, I am experiencing the same bug @smalljude described. I’m on Win 7 64bit, Firefox 12.0.
I extrapolated (by sampling with many clicks!) that it happens only in a small rectangular region (like a 1x2 rectangle in portrait orientation) at the upper left corner of the image, let’s say 60x120 px. It happens with every task, but you notice it only when you need to click in that region!

I hope this helps…

#20

@eluchinat  Yup… that’s exactly what I am seeing too. Thanks for being more specific.  Sadly I haven’t found that the workaround @turing8 mentioned has worked for me. I could never paint the bit I actually wanted … it just lights up a whole firework display all over the image where I don’t want it! :slight_smile:

@balkamm Ah I see.  From my humble viewpoint, I found the varying opacity very useful. I would constantly change it up and down as I move back and forth over the images to see how accurate I had been and if there were tiny areas I missed. That’s just me though… I’ll defer to whatever the masses prefer.