banner91319

Collapse

Announcement

Collapse

Get a Free 3-Day Trial of OTTO

Give OTTO a try for free and Discover the Way mTurk Work Should Have Always Been. To get started, contact me at [email protected]





Our site is constantly growing and adding new features. We've already come a long way in a very short time, and would love for you to become a more active member of our group.

Beyond your initial Free 3-Day Trial, to have a permanent OTTO Key you need to have a Tier 2 or Tier 3 membership.

Our current membership prices are:

Tier 1: Free
Tier 2: $10/month
Tier 3: $15/month


If you need to upgrade your membership tier, please send me a message at [email protected] , and I'll get that taken care of for you.

To Find out all about OTTO check out https://www.ourhitstop.net/otto-instructions .
See more
See less

Page request errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Page request errors

    Question : I use MTS, mainly Hit Finder along with OTTO. Is this considered a scraper, so that I have to put the speed of it into the Page Request calculator? Thanks for any help that anyone can give.

    #2
    Jimmmac1 yes, MTS Hit Finder is a scraper. When you're thinking about PREs, you have to consider everything you have running that is going to call on mturk. Panda Crazy, Hit finder and catcher, Otto, Overwatch, Hit Forker. These are all commonly used scripts that call on mturk. The more you have running, the slower you have to run everything to keep the PREs down.

    Comment


      #3
      Hi ZeldaFoot

      Thanks so much. I will have to make some changes in how I do things. I had 3 hit finders and one hit catcher up and I was wondering why I wasn't catching things. Now I know. Thanks again.

      Comment


        #4
        On a related note, I'm running Otto LIte at 0.8 or 0.9 secs and MTS HitCatcher at around 1300-1500ms and recording no "PREs". (as HC displays PREs) So, I am thinking this is reasonably Ok to do. Is my thinking wrong? Any feedback is appreciated!

        Comment


        • ZeldaFoot
          ZeldaFoot commented
          Editing a comment
          It's generally recommended to keep everything at .8 or higher, collectively. https://www.ourhitstop.net/page-request-calculator This calculator can help you if you need to figure it out. But as with anything, your milage may vary and if what you're doing seems to be working for you then go for it. Just keep in mind if you do start getting a lot of PREs or it seems like you aren't catching anything, you may need to tinker with your settings.

        #5
        Originally posted by ZeldaFoot View Post
        Jimmmac1 yes, MTS Hit Finder is a scraper. When you're thinking about PREs, you have to consider everything you have running that is going to call on mturk. Panda Crazy, Hit finder and catcher, Otto, Overwatch, Hit Forker. These are all commonly used scripts that call on mturk. The more you have running, the slower you have to run everything to keep the PREs down.
        Hi Jimmmac1

        I've got two questions.
        1. This is my Panda timer. Which of the timer cycle is currently in use and how do I activate the timer I intend to use?
        2. Also, I want to calculate using PRE calculator. Would I input 1000, 1400 or 2100?

        I am novice at thisâ˜ș

        Comment


          #6
          Phungp
          So if that is PC.. when you look at the main screen it will have a 1 2 3 at the top to the left of where it says options. That is the 3 cycle timers. If you have it set on 1 it is 1000. If you have it set on 2 it is 1400. And so on. But keep in mind if you have anything on "go ham" it runs every 900ms regardless of what cycle timer you are using (1 2 or 3).

          Comment


            #7
            Originally posted by Acidhoe View Post
            Phungp
            So if that is PC.. when you look at the main screen it will have a 1 2 3 at the top to the left of where it says options. That is the 3 cycle timers. If you have it set on 1 it is 1000. If you have it set on 2 it is 1400. And so on. But keep in mind if you have anything on "go ham" it runs every 900ms regardless of what cycle timer you are using (1 2 or 3).
            Ohhh thank you! I got it.

            Comment

            Working...
            X