Announcement

Collapse
No announcement yet.

Inconsistent QQQQ Intraday Data

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

  • Inconsistent QQQQ Intraday Data

    I’m showing two different close values yesterday for QQQQ on the 30-minute (46.38) and 60-minute charts (64.61). Same values are showing up on QLink data as well. Can anyone explain to me what’s up with this. Is it a server update issue? Any insight would be much appreciated. -d

  • #2
    Hi Dave,

    I'm not seeing the disparity in prices you are.
    Could be server specific.

    Could you supply the IP number associated with Port 2192 please.
    Click Start>Run and enter... cmd ...to get the command window.
    Then enter... netstat -N

    LAM
    Attached Files

    Comment


    • #3
      Sorry...

      Hey Larry,

      Sorry, I forgot the drill. It is:

      216.23.233.219:2192

      Thanks for lending a hand.

      -d

      Comment


      • #4
        Well, hmmm...
        I'm seeing things as OK on the same IP.
        The screenshot is Multi-Minute Bars "accurate".
        Not shown is if MMB is "fast",which will include trades past 4pm to 4:30, it's still in the $46.XX range.

        At this time can only suggest exit/restart to try and clear stuff out.
        After exit, wait a couple of minutes before restart if you can.
        That will give the system time to fully disconnect from existing connections.
        You can see with Netstat when the Timed-Wait status goes away.

        LAM
        Attached Files

        Comment


        • #5
          Wow...it's not what I'm getting.

          Larry,

          This is vierd. No change on the data.

          I did the exit-wait to make a new pot of coffee-restart a few minutes ago.

          Can send you the before and after screen captures if necessary.

          After restart the server is now:

          216.23.233.218:2192

          ...and not .219 as before.

          Still seeing the same problem on QLink as well with it's own exit/wtmanpoc-restart.

          Please enlighten me Oh FlowMeister!

          -d
          Attached Files

          Comment


          • #6
            Well, phooey.
            I got's nuttin' at this point.
            Might be helpful to see the screenshots.
            Can you post 'em?
            or if you would rather, you can send them to...
            [email protected]

            oh..btw...the .ZIP you attached...it appears to be empty.

            LAM

            Comment


            • #7
              Well, it's Friday.

              Larry,

              It was because the forum interface barfed on the upload. BTW, how do you embed an image in the body of the post. I see "Attached" and IMG gives you an http:// reference. Also, is the 102,400 limit for embeds also?

              -d

              Comment


              • #8
                For imbeds...

                1. Have the image at a website somewhere. I use eSignal FileShare to upload images I wish to imbed rather than attach.
                2. When posting, just paste in the Fileshare URL into the popup box you get when you click the IMG button.
                You will see the URL when you upload to your FileShare account, which you will need to create.
                http://share.esignal.com/index.jsp
                Of course, the URL can be from anywhere. I have also used JING. Or if you have a website of your own, that's fine.
                3. The 102K limit is for attachments. I've imbedded much larger animated .GIFs. I'm assuming that's still the case.

                I'll be sending some feedback offlist in a bit regarding the screenshots you sent.

                LAM

                Comment


                • #9
                  Great.

                  Larry,

                  Thanks. That's what I thought. Didn't know about the eSignal FileShare though. That will be useful. Let me know what you see. Am glad to spend some time testing on this end if it helps. Talk to you later.

                  -d

                  Comment


                  • #10
                    Turned out to be a bad MktHours file.
                    Fallout from the recent server side DNS issue.
                    Charts OK now.

                    LAM

                    Comment

                    Working...
                    X