why lastPrice is NOT between bid/ask price? (MarketByPrice)
hi
this is questiona following
how to get full order book (10 buy + 10 sell)
connected to reuters, service : EED_DELAYED , using QA account,
subscribe data by both "MARKET_PRICE" and "MARKET_BY_PRICE"
found that BID/ASK mismatch to order book, e.g.
for RIC : DXU7
time=[2017-09-01 16:17:55.684166], sym=[ DXU7], [Action=Update;Key=<strong>92.720A</strong>;
time=[2017-09-01 16:17:56.119753], sym=[ DXU7], [ ASK]=[<strong>92.755</strong>]
<br>time=[2017-09-01 16:17:56.119753], sym=[ DXU7], [ BID]=[<strong>92.750</strong>]
<br>time=[2017-09-01 16:17:56.416813], sym=[ DXU7], [Action=Update;Key=<strong>92.720A</strong>;
ask price (in order book) is less than BID price.
attached log file : wrongprice.txt
could you advise?
Best Answer
-
@qiang.zhu
Do you have the time of the updates?
It is possible that "MARKET_PRICE" and "MARKET_BY_PRICE" have difference delay.Consider that you subscribed to a delayed service, you should always use the time from time fields rather than system time.
0
Answers
-
hi
just checked, in msg for order book (marketByPrice), there is NO timestamp.
for the same RIC,
why "MARKET_PRICE" and "MARKET_BY_PRICE" have difference delay??
this will block my testing.
is there any other way to get 'last trade price/qty' and 'order book (10 bid + 10 ask) ', which are on the same timeline?
I was told that might get orderbook by normal marketprice mode, using another RIC, will receive tag like BID_1, ASK_1, ..., BID_10, ASK_10, etc.
where can I find all 'another RIC' for all future?
thanks
0 -
in msg for order book (marketByPrice), there is NO timestamp.
For <DXU7>, the time stamp is in summary data. The field is "TIMACT_MS".
Unlike "TIMACT", "TIMACT_MS" is milliseconds pass midnight.
why "MARKET_PRICE" and "MARKET_BY_PRICE" have difference delay??
The delayed is entirely up to the server configuration. You should contact server admin.
0 -
I was told that might get orderbook by normal marketprice mode, using another RIC.
Yes, you can get a fixed depth order-book from "MARKET_PRICE" domain.
You have to request 0#[Root-RIC]. You will get a chain containing the Root RIC, fixed depth order-book RIC, and other associated RICs.
For example, if you request 0#DXU7, the chain will return DXU7 and the fixed depth order-book RIC D2DXU7.
Please note that they are not full order-book.
Also, 0#[Root-RIC] will return not found status if Root RIC does not have order-book or if the fixed depth order-book already included in Root RIC.
0 -
hi
I just checked,
there is NO delay in 'TIMACT_MS' in order book (MARKET_BY_PRICE)
, but there is delay (around 10 minutes) in TRDTIM_1 (MARKET_PRICE)
that's the root cause.thanks.
0 -
hi,
thanks for the reply,
tried below scenario :
- send one request ,"0#DXU7"
- received data, [LINK_2]=[D2DXU7]
what does LINK_1/LINK_2/LONGLINK1/LONGLINK2 mean??
shall I choose LINK_2 and LONGLINK2 ?
- get new value(D2DXU7) from these data (by a tag LINK_2), then send out another request for this D2DXU7
- received a snapshot of order book for new RIC,
BEST_BID1/BEST_BSIZ1/BEST_ASK1/BEST_ASIZ1/etc.from 1 to 10
but there is NO more update.
actually, NO more update for any tag.
is there any simple way to get prefix/postfix for RIC?
it should be hard coded for specific exchange, right?
thanks.
0 -
They are chain RIC. This article should give you more info Decoding Chain.
There should be updates from D2DXU7, did you accidentally send "snapshot request"?
And yes, the prefix/postfix are defined for each exchange.
0 -
hi
thanks for the response.
but I cannot reply your latest response, so I reply in here
I just changed RIC code, have NOT changed any other code,
these code can get real-time updated data successfully before.
is there any sample code to get order book by "marketPrice"?
(bid_1/ask_1/etc., from level 1 to level 10)
where can I find these prefix/postfix definition??
it's per exchange, I can loaded these from config. it's easy to add this logic
thanks.
0 -
I'm using RFA's StarterConsumer example right now, and I can get updates from D2DXU7 just fine.
May be it is because you are connecting to delayed service. You may have to wait a few minutes before the application starts receiving updates.
And, unfortunately, there is no list of these prefix/postfix. Although the prefix/postfix are defined per exchange, they can be changed. So we would recommend getting the order-book RIC from 0# chain which will always reflect the change.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 256 ETA
- 564 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2.1K Refinitiv Data Platform
- 775 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 231 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 98 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛