EyeWire Stats - another TamperMonkey script

agree with you hwaaim.
Quick reap is great, i show things in explore-color, no need for annotate. And as you say, if more is needed, you can go into “normal” log

1 Like

Hey all, we’ll discuss some of these ideas on Mon and weigh in if there is more to add from HQ.

3 Likes

I honestly believe that annotate images is really important. When I complete a lot and look at entries that do not have annotations, I really get confused as to where the changes occurred as well as how. That I believe causes me to make mistakes at times (rarely, but still) and not communicate well when I work on completes.

I really appreciate you taking out your time to look at this discussion and weigh in everything. My heart and soul got almost 10x bigger just now! <3

That sounds really cool, and I think I’ve possibly heard of that, but I looked at all the settings and don’t see it anywhere. I’ll keep looking because I don’t want to inconvenience you in the hunt for it (unless you want to, in which it’s fine). Thanks for letting me know about it! I also don’t see it in the search engine.

While one can create a new entry, that really should be for an update (like there was a new change in the cube). Also, it’s really difficult and time-consuming to go back to the cube I was previously in, click reap again without making further changes (in which I could make mistakes/get in trouble for not double-checking) and then annotate the image there - in which I probably forgot the changes by then.

I wrote about the Auto Complete here:

You have to have at least v. 1.12 of the Utilities for the option to be available.

What @susi is talking about is that she have turned off Log & Reap (also available in the Settings -> Utilities), so she can add the changes in the Explore color, then quick log, then dismiss the changes and normal reap (with the option turned off there won’t the new popup after reaping).

1 Like

Maybe I don’t have v1.12. I wonder how to get it. That makes sense about what @susi does.

Looking back, I have questions for @susi.

How does one avoid the first paragraph? Also, how does finishing a branch faster in speeding up finishing than completing all the cubes or just completing random cubes? I’m confused on those two, as I just don’t know how that works :slight_smile:

Well, for one thing it is HQs request that we complete along branches as opposed to random cubes all over the cell. This may have gotten buried so I’m gonna leave this here. I think we can ignore the reapgrowing part of this and focus on the scythe complete for the purposes of this discussion.

Hi all. To wrap up this conversation, HQ just wants to affirm/reiterate that Scythes are expected to check branches using the overview, working from parents to children. Bouncing around branches would cause redundant reviewing and also divorce cubes from the context required for assessing consensus. In the future, it would be great to have a way to SC along a guided “track,” but that infrastructure doesn’t exist at the moment. If there are any further questions about Scythe Complete procedure, please open a new thread so that discussion in this one can remain focused on Krzysztof’s scripts.

4 Likes

If you SC a branch from its source, there’s high probability, that you’ll find the merger where it starts. If you’d jump to random cubes, you would, from time to time, be SCing cubes in a merger branch without knowing, that it’s a merger branch.
As for 2 scythes checking the same branch to remove it from being available to play - it has changed lately; now one SC vote is enough to block a cube. But not very long time ago it used to be better to double check a branch to block it from playing, than if one scythe would be checking one branch and the other some other branch, because in that case those 2 branches would be still available to play. Now it’s even better, if a scythe starts checking a cell from branches, that weren’t checking at all,to speed up the completion of the cell or if two scythes check two different branches. But still, checking the branches, from start to finish, seems to be the only way to be almost sure, that we aren’t checking some merger branches.

2 Likes

IDK if this is better directed at KK or admins, but if Scouts Log has been integrated into EW, can a limited version of SL be given to regular players, perhaps just the option to create + annotate screenshots from review?

1 Like

that’s an interesting idea. like scout lite?

Utilities v. 1.12.5
FIXED the problem with the camera icon not being fully visible when the SL was in the Compact Mode
MOVED options specific to SL to the “Scouts’ Log” section in the Settings menu.

Cubes v. 1.7.4
RENAMED the script to Cell Mission Control (after HQ’s suggestion), so the script now have more meaningful name.

1 Like

I wouldn’t say scout-lite but that’s ideally a direction I’d like things to head in. Advanced players tend to want to report things, but more importantly new players want to ask questions about cubes they’ve messed up and things like that, if they can have snapshots of things it’s a lot easier to get specific. If it’s easy for new players to get help like that they’re more likely to improve.

Now if you were to, say, build a game like this from scratch (just a hypothetical), it may be a solid idea to have a 2nd log that is built for players looking for feedback on a cube that mentors could respond to. I don’t know if it makes as much sense building the same thing for Eyewire right now which is why I haven’t put anything like it on the suggestion sheet, but it’s an idea.

I have a couple more thoughts along these lines but I dunno if they’re within the scope of this thread.

like if they’re like - potential merger on #______? Then what would be the purpose of a scouts role if everyone is a scout? Not that that’s bad, as it can streamline things, but still in my head

Awesome. Usually I look at the OV when something doesn’t seem right and I’ve found some pretty big mergers and missing branches from it. But what you say seems to make finding mergers even faster yet, which yes, does make the play go faster through efficiency for sure. It’s good to hear that different perspective to look outside of my own.

PS - the new camera shot feature seems cool!

Like I said, this is more so that it’s easier for new players to get feedback on things they are seeing, for faster improvement. There’s already a screenshot tool built in, but it’s… sub-optimal for uploading and stuff. I want to improve the experience from fresh-off-the-tutorial to enfranchised player.

Scouts still get much better tools to see beyond the cube, and get a much better grip of what’s going on at the branch level & neuron level. I won’t deny that this means more advanced players will be using chat to flag things, but anyone with a decent screenshot tool is doing that anyway, I just figure everyone should have a screenshot tool.

I’ve requested a screenshot tool in general before, but where I’m confused is what it’s used for - if you don’t mind clarifying. What would advanced players have greater capabilities of compared with all players? The reason is that you bring it up a lot and I’m trying to discern what you’re saying.

I think I’ll add it as a suggestion on the google sheets, but as it goes here, it’ll be worth mentioning. It’d be cool if there’s a way to post an update to log entries - like an update section under notes, and people can write in the update (or something else). Then it’d post underneath the entry in a different color in the cube details section once finished.