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

Why the data confused once several RICs were asked #40

Open
hzadonis opened this issue Jun 6, 2018 · 4 comments
Open

Why the data confused once several RICs were asked #40

hzadonis opened this issue Jun 6, 2018 · 4 comments

Comments

@hzadonis
Copy link

hzadonis commented Jun 6, 2018

Hi, Masters:
I'm using pyrfa to subscribe data from TREP.
Once I subscribe server RICs, in this case, such as 300570.SZ and 600519.SH. I found my program sometimes confused the price provider. Such as:
Line1: QList(['2018-06-06T05:05:24.000000000'], dtype='datetime64[ns]'), QList([b'600519'], dtype='|S9'), QList([798.8], dtype=float32), QList([100]), QList([798.88], dtype=float32), QList([400])]
Line2:[QList(['2018-06-06T05:05:27.000000000'], dtype='datetime64[ns]'), QList([b'300570'], dtype='|S9'), QList([798.67], dtype=float32), QList([400]), QList([798.88], dtype=float32), QList([400])]
Line1 from 600519.SH is right, but Line2 should come from 300570.SZ

Could you please give some suggestion how to fix the problem? Thanks!

Regards
Zheng

@wiwat-tharateeraparb
Copy link
Contributor

Hi, not sure how’s your program parse and cache the data from pyrfa though as we don’t see your code here. My guess is that the data is in incremental updates and you probably didn’t clear the previous value from previous update.

@hzadonis
Copy link
Author

hzadonis commented Jun 6, 2018

This was caused while I asked several RICs, the data package input from TREP, I can't tell which package belongs to which RIC. Then confusion occurred.

@hzadonis
Copy link
Author

hzadonis commented Jun 6, 2018

Yes, not clear is a problem, let me try it. Thanks!

@hzadonis
Copy link
Author

hzadonis commented Jun 6, 2018

Thanks! it was caused not clear the initial data after every update data package passed.

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