TR.OPENPRICE, TR.HIGHPRICE, TR.LOWPRICE, TR.SETTLEMENTPRICE returning NaN for ESU0

Using this line of code:
df, err = ek.get_data(['ESU0'],
['TR.SETTLEMENTPRICE.DATE', 'TR.OPENPRICE', 'TR.HIGHPRICE', 'TR.LOWPRICE', 'TR.SETTLEMENTPRICE',
'TR.ACCUMULATEDVOLUME', 'TR.OPENINTEREST'],
{'SDate': "01/01/2006", 'EDate': "12/31/2020", 'Frq': 'd'})
returns many NaN entries for Open, High and Low on dates where there is a Settlement price and volume & OI. Settlement price for most recent traded day (18 Sep 2020) is also NaN.
Best Answer
-
Hi @nrowe
I checked on 2 fields, TR.SETTLEMENTPRICE and TR.OPENPRICE
TR.SETTLEMENTPRICE has the data from 2019-06-24 (Seems to be 15 months from today)
TR.OPENPRICE has the data from 2019-09-24 (Seems to be 1 year from today)
You can clarify the content behavior with Refinitiv Helpdesk by submitting a ticket at my.refinitiv.com/
0
Answers
-
It's not uncommon to have open, high, low, close prices missing at the beginning of the contract life cycle when trading is thin. Settlement price is calculated and published at the end of every trading day regardless of whether there were any trades in the contract. The non zero volume indicates that there were trades on that day, but even on the days with non zero volume open, high, low, close prices may be missing. Not all trades are summarized into open, high, low, close bars. Certain trades are excluded from this summarization. If on a given day the only trades that occurred were the ones that are excluded from open, high, low, close summarization, then for that day you'll have non zero volume, yet open, high, low, close prices will be null. One example of this that you can examine is ESM1 that on 17-Aug-2020 had one special trade that was excluded from open, high, low summarization. The value of TR.ACCUMULATEDVOLUME for ESM1 on 17-Aug-2020 is 1. Yet the values of TR.OPENPRICE, TR.HIGHPRICE, TR.LOWPRICE and TR.CLOSEPRICE are NULL. If you look at the intraday price history for ESM1 in Eikon Time & Sales app for 17-Aug-2020, you'll see a single trade for that day with the trade volume of 1. This trade is marked in the Trade Flags column as "Special Trades".
This said, if you believe open, high, low, close prices are missing improperly for some dates and contracts, could you provide a specific example, so we could look into it?0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 650 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
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛