Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pyrfa returns different value when comparing with testclient #57

Open
unnikvin opened this issue Oct 18, 2021 · 8 comments
Open

pyrfa returns different value when comparing with testclient #57

unnikvin opened this issue Oct 18, 2021 · 8 comments

Comments

@unnikvin
Copy link

Example: For 019490.KS, fID 6614 TRD_STATUS on 13 Oct 2021, the value was blank when using testclient (confirmed correct with helpdesk) however pyrfa was showing as OD (Opening Delay). Please could you explain the difference?

@wiwat-tharateeraparb
Copy link
Contributor

Hi, this 6614 FID is an enumerate type and translated as the following. Can you check with your testclient's enumtype.def file?

!
! ACRONYM    FID
! -------    ---
!
TRD_STATUS  6614
!
! VALUE      DISPLAY   MEANING
! -----      -------   -------
      0         "  "   Undefined
      1         "N "   Normal
      2         "H "   Halted
      3         "S "   Suspended
      4         "OD"   Opening Delay
      5         "R "   Restricted
      6         "CD"   Closing Delay

@unnikvin
Copy link
Author

enumtype.def reads exactly the same as listed above. Refinitiv Helpdesk also confirmed that they see " " (undefined) and that matches our finding.
We are trying to figure out why it is different in pyrfa - "OD"

@wiwat-tharateeraparb
Copy link
Contributor

Can you try to set pyrfa.cfg

\Connections\<Connection_RSSLxxx>\traceMsg = true

To see raw RSSL message and check FID 6614 value.

@unnikvin
Copy link
Author

unnikvin commented Oct 19, 2021 via email

@unnikvin
Copy link
Author

unnikvin commented Oct 20, 2021 via email

@wiwat-tharateeraparb
Copy link
Contributor

@unnikvin We think this is a bug in the PyRFA decoder. The trace message data shows raw blank data on FID 6614 from the server which I believe is correct. However, we are not able to investigate and fix this mainly because we don't access to real-time Refinitiv anymore. But if this is important to you and need it fixed, we can provide service for that matter.

@unnikvin
Copy link
Author

unnikvin commented Oct 20, 2021 via email

@wiwat-tharateeraparb
Copy link
Contributor

Please contact support@devcartel.com for assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants