Getticker returned the volume data incorrectly.
Author: churchillxy, Created: 2022-04-06 16:30:01, Updated:Hi, I'm using thegetticker function to get the Link_USDT transaction price and transaction volume on the OKX exchange, but the running data and the live data obviously don't match, what's the reason?
Annex I: Transaction prices and number of transactions obtained by Getticker
Annex II: Screenshot of live data from the OKX
- Recent Situation and Recommended Operation of Funding Rate Strategy
- Dual Moving Average Breakpoint Strategy of Cryptocurrency Futures (Teaching)
- Cryptocurrency Spot Multi-Symbol Dual Moving Average Strategy (Teaching)
- Realization of Fisher Indicator in JavaScript & Plotting on FMZ
- The Trustee
- 2021 Cryptocurrency TAQ Review & Simplest Missed Strategy of 10-Time Increase
- Cryptocurrency Futures Multi-Symbol ART Strategy (Teaching)
- Upgrade! Cryptocurrency Futures Martingale Strategy
- The Getrecords function cannot get a K-string map in seconds
- FMZ Based Order Synchronous Management System Design (2)
- FMZ Based Order Synchronous Management System Design (1)
- Design a Multiple-Chart Plotting Library
- Simulated disk environment
- 60-Line Code Realizing One Thought - Contract Bottom Fishing
- FMZ Billing System Upgrade & Adjustment Announcement
- Notice for Ghostwriting Strategies on FMZ
- The upstream server is timing out.
- Binance reported error
- Multivariate
- Real Technology of FMZ Quant - How to Break the Limits for Obtaining Tick
Inventors quantify - small dreamsI don't understand your question, what exactly is it? What specific data is problematic? How is your test code written?
NO.1It's definitely your parameter problem, look at permanent, spot, current, next quarter, next week, next week these settings are right or wrong.
Inventors quantify - small dreamsGetTrades in the API documentation
churchillxyIs there a function that can get the transaction per penny?
churchillxyOkay, I see. Thank you.
Inventors quantify - small dreamsThe above has already been explained to you: the amount of transactions in ticker data is the amount of transactions that roll over 24 hours, and you compare it with the amount of transactions in the most recent transaction log, which are not the same time span.
churchillxyI'm already in the telegraph group, I'll join you.
Inventors quantify - small dreamsYou can add a telegram group and the homepage has an address.
churchillxyI've seen n times, including a demo of the documentation running.// Hi, can you help me see it? or give me a demo code.// I can pay for consultation, hopefully the solution is more efficient, the team card has been on this for a long time.//
churchillxyWe've been stuck with this problem, and our team is looking for efficient solutions.
Inventors quantify - small dreamsThere is a description in the API documentation, which you can check out here.
churchillxyWhat's the volume of thegetticker?
Inventors quantify - small dreamsThe two definitions of comparison are not the same.
churchillxyThis is in contrast to OKX's LINK-USDT incremental transaction, which can be seen in the screenshot.
Inventors quantify - small dreamsThe volume of transactions in ticker data is the amount of transactions scrolling for 24 hours. The comparison is the most recent transaction record? or what? The content of the comparison is not defined the same, there is no comparability.
churchillxyMy problem is that the transaction volume is different from the real disk data, this is my code, trouble seeing what is the reason? /upload/asset/24695bced45f1cf6fbe6d.png
churchillxyAlso, I set up the same parameters to run getrecords andgetticker to compare the data, and thegetticker data is clearly abnormal, see figure /upload/asset/246da876618407ece9de7.png
churchillxyI chose to read it on the spot, i.e. in the real disk setting, no problem.