- ago

With ADA and ALGO, the prices are somehow equated, resulting in an incorrect quantity calculation.
The decimal places are also missing in ALGO. Perhaps this is an indication


0
105
18 Answers

Reply

Bookmark

Sort
Cone7
- ago
#1
There is no quote (Stream is not enabled.)
You're looking at price triggers for the same price and quantity for 2 different instruments. It seems most likely that you entered these manually.
0
- ago
#2
I only overwrite the quantity because I convert this in an Excel table for my BTC account. The prices from which this is calculated comes from WL.
Here are the signals without my correction.
0
Cone7
- ago
#3
When I run a strategy to generate alerts on a similar set of Binance symbols with Binance data, here's what I get -



Where do you think the difference comes from? My first observation is that your symbols have a "dot" separator in them? It's not the Binance format, so where is this data coming from?
0
Cone7
- ago
#4
.. but when sending those Alerts to the Quotes window, I see that were not using the correct number of "display decimals". It's cosmetic, but we should fix that!
0
- ago
#5
QUOTE:
Where do you think the difference comes from? My first observation is that your symbols have a "dot" separator in them? It's not the Binance format, so where is this data coming from?

I have no idea.
I have been running the system for many months. The error is new for a few days.
The data comes from Cryptocompare. I map all symbols to Binance format following the same pattern.
Something has obviously changed. But what?
0
- ago
#6
Another problem has arisen with Binance. The orders are no longer transmitted. Does this have the same cause? The timing of the problem is about the same. And both were running before.
0
Cone7
- ago
#7
Let's not mix problems. If you can't connect to Binance, that's different than where we started. Synchronize your computer clock, restart WL8, and if the problem persists, start a new Discussion.

On ADA / ALGO, it seems you must have made a mistake in the mappings. If you don't see the error, post the mappings that you're using.
0
- ago
#8
my mapping
CODE:
[[\.\/\-]=] DOT.BTC=DOTBTC
0
Cone7
- ago
#9
So you're just removing the separator. That just puts us back to where we started then - no idea how ALGO and ADA are equating.

1. If you chart both symbols with Cryptocompare, are they correct?
2. Why are you running the system on Cryptocompare data when you're trading on Binance? In other words, why wouldn't you use Binance's data?
0
- ago
#10
1.
yes


2.
2.
a.
The data series from CC are longer than those from Binance or Kraken. These only provide historical data from the date they themselves made it tradable.
b.
Especially Binance sometimes misses single quotes
c.
During the development I wanted to have a uniform and as long as possible database.
0
Cone7
- ago
#11
Okay, I assume that CryptoCompare is aggregating data from all the exchanges, so as long as you're not trading intraday by building bars from only one of the streams, it shouldn't matter too much which provider feeds the Quotes triggers.

Let's take it from the top...
How exactly did you generate the same order price for the 2 symbols?
We need to see the script and DataSet symbols please.
0
- ago
#12
I think I have found the error.
The "Highest" indicator is the problem.
If I exchange the indicator e.g. against the EMA, it works.
0
Cone7
- ago
#13
What exactly is the problem with "Highest"?
How did it make you think that ADA and ALGO were the same price?

While I don't believe there's an error with "Highest", it really does seem odd that it would return precisely the same price for those 2 instruments.
0
- ago
#14
I don't know what exactly the problem is with "Highest".
I only know that the problem with the indicator is there and disappears when I change the indicator. Even "Lowest", which belongs to the same category, works.

I have recreated my system with the Bulding Blocks just in case the old one is broken.
There it was the same.
0
Cone7
- ago
#15
Here's my test. What's the difference?



You need to show me what you're doing, not just a code block. Show me the whole strategy and DataSet that you're running it on. - pictures of the Strategy Design page and the Strategy Settings .
0
Cone7
- ago
#16
First, let's take CryptoCompare out of the equation. Run your script on a Binance-linked DataSet. Do you see the problem there?
0
- ago
#17
I have now run the following tests:
-A dataset from Binance directly--> works
-Another dataset from Cryptocompare that also contains the two symbols--> doesn't work
-Tested the system on another PC-->doesn't work
0
Cone7
- ago
#18
WL8 Build 23 will "fix" Cryptocompare display decimals problem, but we still don't see a way to make 2 symbols look like they have the same data when they do not.
0

Reply

Bookmark

Sort