EMA Returns TIME value upto nanoseconds, whereas RFA used to return upto seconds. Is this intentiona
We have noticed difference in time values, RFA used to return "20:12:27" whereas EMA returns "20:12:27:000:000:000". Not sure if this was intentional or not ?
Best Answer
-
Hello @gaurav.mahajan
EMA is designed to support MiFID II(the precision of timestamp extends to microsecond and nanosecond) from the beginning. That’s why you see it returns the timestamp up to nanosecond i.e. 20:12:27:000:000:000 even the timestamp’s precision is up to second. While RFA 8.x has been enhanced to support microsecond and nanosecond later from RFA 7.x. RFA 7.x supports up to second and millisecond and it throws an exception if it receives time stamp containing microsecond or nanosecond. For more details, please refer to the article Coding For High Precision Time . That’s why you see RFA returns up to second for the second timestamp.
Based on my test, RFA 8.x returns timestamp according to the timestamp’s precision. For example:
- second timestamp: 20:12:27
- Millisecond timestamp: 20:12:27:001
- Microsecond timestamp: 20:12:27:001:002
- Nanosecond timestamp: 20:12:27:001:002:003
While EMA returns up to nanosecond regardless the timestamp's precision. For example
- second timestamp: 20:12:27:000:000:000
- Millisecond timestamp: 20:12:27:001:000:000
- Microsecond timestamp: 20:12:27:001:002:000
- Nanosecond timestamp: 20:12:27:001:002:003
Anyway, EMA provides com.thomsonreuters.ema.access.OmmDateTime interface which has the method to get hour, minute, second, millisecond, microsecond and nanosecond. Hence, you can use the methods to get only unit time you prefer. Please refer to the method decode(FieldList fieldList) in the Consumer example application in example200__MarketPrice__Streaming demonstrating how to use these methods.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛