It only is used for Delayed Ham Mode. The option tells the script to go into ham mode on this job for 15 seconds if it finds a hit. So it only is trying to collect that one hit for 15 seconds before it turns off and continues trying to collect all hits turned on. At the beginning this worked out great but when throttling started to be more common then it started to cause problems with the script constantly being in ham mode but grabbing nothing. That was wasted time so I made it possible to lower that timer to give other hits a chance to be collected. Having a higher seconds timer here may grab more hits from requesters who drop hits slowly and not all in one batch. Throttled hits is something of a problem and it may or may not help with a lower timer for this option. I personally think a lower timer for this is better because if it's a non throttled hit the timer will reset once it collects a hit so it can fill up a queue with no problem. But there are times that a higher timer can give better results for throttled hits. You have to test it out on your own because I still haven't made up my mind what the best timer would be. In the general options you can also set the default value for it for any new jobs added.I'm very interested in the "Ham Timer (seconds)" detail setting. What is the reason for this ? It's the "delay" after finding the last HIT during HAMing? Is this often a waste of 15 seconds? Not criticizing, just trying to get a feel for when/if to alter this setting. I am finding Delayed Ham soooooo useful
Glad you found it. I think this is the number one thing people don't realize about the queue script. I use it so many times throughout the day.
That error is a mturk problem. For some reason it shows errors from previous pages you used. Usually the first message is the right one so it still works correctly. It should go to the next hit in your queue automatically without the queue helper.
No the new site should automatically go to the next hit in queue. The problem is there is no way to tell it which hit it should go to so the queue helper needs to do a redirect after going to the next hit if it needs to go to another hit in your queue.
The flash is the only way I could figure out to make the script to go to a hit other than the first one. It makes it translucent so you know the script is working so don't do anything yet. If it has no instructions to go to a specific hit in queue then it goes back to normal. If you wanted it to go to the third hit in queue then it will redirect to the 3rd hit after the translucent screen. Hope they can provide a better way of doing it like the old page but at this time this is the best I can do.
10 jobs is a lot to use up for one requester. It better pay very very well for me to hold up 10 jobs. So if it doesn't pay very well then using a search job would be a lot better. It would take 1 second to find out if there are any hits available instead of 10 seconds to go through all 10 group id's.
This used to work but I had to change the way jobs are moved to different tabs so I disabled this feature because of conflicts. I was hoping to add this feature back once I found a good way of having both features work but never had the time to work on it. Being able to move jobs to other tabs easier and less buggy was a lot better than having the dragging tabs around so it didn't bother me.
Alright brotherman, I appreciate the responses. It's pretty disappointing how backwards the new site is going and I'm sure this whole transition has been a giant headache for you. Thanks for your hard work!
I have seen this error before. The script doesn't understand expired hits in the queue. It's expecting a time left but it doesn't so it tries to convert it into a number which it then tries to convert to a human readable time left. It disappears in a few seconds so I never thought of it as something that needs to be fixed right away.
The old URL still works fine.
So it's an issue with VM huh? Just after I moved all my scripts over to it too! Guess it's a good time to move again since a lot of the old scripts are dead.
