For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
I query RIC code TUU0, field SETTLE using websocket connection to TREP machine. it return me a number 110.4219, however the RIC page from desktop application Eikon show 100 108/256 = 110.421875, why websocket truncate to 4th digit. Seems wrong!
This automatically truncating does not happen in getting option settlement price.
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
I have connected to ADS3.4.0.L1 with the WebSocket connection.
The retrieved price wasn't truncated.
RECEIVED:
[
{
"Fields":{
"ACTIV_DATE":"2020-07-17",
...
"ACVOLTM_MS":"08:15:34.167",
"ACVOL_1":15569,
"ACVOL_TIM":"08:15:34",
...
"SETTLE":110.421875,
"SETTLEDATE":"2020-07-16",
"SETTLE_TIM":"23:34:56",
...
},
"ID":2,
"Key":{
"Name":"TUU0",
"Service":"ELEKTRON_REPLABLINUX1"
},
"PermData":"AxHvMVPA",
"Qos":{
"Rate":"TickByTick",
"Timeliness":"Realtime"
},
"SeqNumber":33472,
"State":{
"Data":"Ok",
"Stream":"Open",
"Text":"All is well"
},
"Type":"Refresh"
}
]
It looks like to be a bug fixed in ads3.4.0.L1.
TREP-2667; WebSocket price fields are rounded to 4 decimal places. Case 08218129 RWF to JSON converter library (librsslJsonConverter.so.1) has loss of precision for REAL fields if greater than 4 decimal places.
