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

Wrong prices displayed on summary for formula assets #55

Open
Zapata opened this issue Jun 7, 2018 · 1 comment
Open

Wrong prices displayed on summary for formula assets #55

Zapata opened this issue Jun 7, 2018 · 1 comment

Comments

@Zapata
Copy link

Zapata commented Jun 7, 2018

If I run HERTZ.yaml (after fixing #37), I have inconsistent information displayed on the console:

$ python3 cli.py --configfile bitshares_pricefeed/examples/hertz.yaml update

+--------+------------+--------------+--------------+------------------------+------------------------+------------------------+--------------+------------------------+--------+--------+-------------------------+-------------+
| symbol | collateral |  new price   |     cer      |          mean          |         median         |       wgt. avg.        | wgt. std (#) |       blockchain       |  mssr  |  mcr   |      my last price      | last update |
+--------+------------+--------------+--------------+------------------------+------------------------+------------------------+--------------+------------------------+--------+--------+-------------------------+-------------+
| HERTZ  |    BTS     | 4.7511676181 | 0.2525694937 | 0.2104745781 (2157.36) | 0.2104745781 (2157.36) | 0.2104745781 (2157.36) |  0.00 ( 1)   | 0.2262904320 (1999.59) | 110.0% | 200.0% | -1.0000000000 (-575.12) | unknown ago |
+--------+------------+--------------+--------------+------------------------+------------------------+------------------------+--------------+------------------------+--------+--------+-------------------------+-------------+

As you can see new price = 4.7511676181 and cer = 0.2525694937, it seems inverted.

@Zapata
Copy link
Author

Zapata commented Jun 7, 2018

This commit fixes this issue and #37.

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

1 participant