How to interpret session data for specific instruments?
I am trying to match session information for JGBc1 retrieved via the RDP data library for .net (using the 3.2.06-Endpoint-TSIMetadata example) with the trading sessions shown by the EIKON instrument explorer. The first session for Monday, according to EIKON, starts on Friday 15:30 and an ends on Saturday 6:01 (as expected). For all other days it starts on the day before and ands on the respective trade day. But looking at the json data I cannot see how I am supposed to derive this information. I extracted and appended the relevant json data below.
What does the "trades" array mean and how is it connected to the "tradesText"? That is the part I suspect encodes the information but I don't see how I am supposed to interpret it.
{
"trades": [
null,
2,
3,
4,
5,
1
],
"tradesText": {
"tue": "tue",
"wed": "wed",
"thu": "thu",
"fri": "fri",
"mon": "mon"
},
"tradingPhase": "Normal (Evening Session)",
"startTime": [
15,
30,
0
],
"endTime": [
6,
1,
0
],
"classificationText": "Normal",
"classification": 1,
"isOvernight": true
}
Best Answer
-
I've reached out to the internal team to see if there are any details related to the interpretation of the Trading Sessions as these rules are quite detailed. Based on what I know, the "isOvernight" flag will need to be taken into consideration.
The "TradingSessions" definition are designed to determine the rules to be applied based on the datetime of the trading activity. When the overnight flag is set set to false, the range of the trading window is literally between the start/end time defined for the current day based on the exchanges timezone (OSA). However, if the overnight flag is set to true, the range of the trading window spans a day. For example, based on the market activity, the trading window for the "Normal (Evening session) can be either (today:tomorrow), i.e. today (3:30 P.M) to tomorrow (6:01 A.M) or (yesterday:today) yesterday (3:P.M) to today (6:01 A.M).
0
Categories
- All Categories
- 6 AHS
- 37 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛