Download | Wiki

Post 1.7 Upgrade Issue


#1

I am running PT 2.2.0 and PTFeeder 1.7.0.1480.

Since the update, my PTFeeder is generating bad PAIRS and DCA properties files. The values all contain NaN.

Profit Trailer reports the following error. PTFeeder appears to be humming along.

2019-01-22 18:47 -05:00: 2019-01-22 18:47:40 ERROR AppErrorController - org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: NaN is not a valid double value as per JSON specification. To override this behavior, use GsonBuilder.serializeSpecialFloatingPointValues() method.

Example NaN
DCA.properties:# First bought in minutes NaN
DCA.properties:# Total cost NaN
DCA.properties:# Pending bought cost NaN
DCA.properties:# Pending value NaN
DCA.properties:# Profit NaN
DCA.properties:# Dca count NaN
DCA.properties:# First bought in minutes NaN
DCA.properties:# Total cost NaN
DCA.properties:# Pending bought cost NaN
DCA.properties:# Pending value NaN
DCA.properties:# Profit NaN
DCA.properties:# Dca count NaN
DCA.properties:# First bought in minutes NaN
DCA.properties:# Total cost NaN
DCA.properties:# Pending bought cost NaN
DCA.properties:# Pending value NaN
DCA.properties:# Profit NaN
DCA.properties:# Dca count NaN
DCA.properties:# First bought in minutes NaN
DCA.properties:# Total cost NaN
DCA.properties:# Pending bought cost NaN
DCA.properties:# Pending value NaN
DCA.properties:# Profit NaN
DCA.properties:# Dca count NaN
DCA.properties:# First bought in minutes NaN
DCA.properties:# Total cost NaN
DCA.properties:# Pending bought cost NaN
DCA.properties:# Pending value NaN
DCA.properties:# Profit NaN
DCA.properties:# Price change (120, 360, 720): NaN%, NaN%, NaN%
DCA.properties:# Volume change (120, 360, 720): NaN%, NaN%,

I’m not sure what conditions cause this to occur. This is not the case 100% of the time. There are times when PTFeeder is able to generate a (mostly) proper file; for example.

**#------------------BTC/ZRX------------------**
**# Last Price: 0.00007989**
**# Volume: 278.3357**
**# Coin age: 9/13/17 12:00 AM UTC**
**# Price change (120, 360, 720): -0.85%, -1%, 1.12%**
**# Volume change (120, 360, 720): -25.34%, -82.18%, -35.12%**
**# Upside volatility (120, 360, 720): 0.06%, 0.08%, 0.11%**
**# Downside volatility (120, 360, 720): 0.14%, 0.1%, 0.11%**
**# Dca count NaN**
**# First bought in minutes NaN**
**# Total cost NaN**
**# Pending bought cost NaN**
**# Pending count 0**
**# Pending value NaN**
**# Profit NaN**
**# Atrp (120, 360, 720): 0.183963%, 0.185285%, 0.227718% #**
**# Highest (120, 360, 720): 0.000081, 0.000081, 0.000081 #**
**# Lowest (120, 360, 720): 0.00008, 0.00008, 0.000079 #**
**# HighLowPercentageChange (120, 360, 720): -0.468048%, -0.642786%, -0.006241% #**
**# AverageCandleBodySize (120, 360, 720): 7.23942, 7.749557, 10.036051 #**
**# Vwap (120, 360, 720): 0.000081, 0.000081, 0.000081 #**
**# Macd (CandleSize: 5m, Fast Length: 12, Slow Length: 26, Signal Length: 9): -0.0000000405894769770818 #**
**# ShortSma (10 candles, 5m): 0.000080294 #**
**# LongSma (60 candles, 5m): 0.0000807858333333333 #**
**# ShortEma (10 candles, 5m): 0.0000803059343365792 #**
**# LongEma (60 candles, 5m): 0.0000806486598978456 #**
**# ShortRsi (20 candles, 5m): 30.9303919467216 #**
**# LongRsi (40 candles, 5m): 41.1325244415407 #**
**#**
**# Selected configs #**
**# PriceTrendChange: -0.853854720950371 <= 7 #**
**# DownsideVolatility: 0.1377 <= 1.5 #**
**#**
**ZRX_DCA_Trailing_Buy = 0.01**
**ZRX_DCA_Trailing_Profit = 0.5**

#2

It was determined in the PT Discord support group that the issue was missing indicators vs pairs. I’m able to add them in manually, but PT Feeder wipes them out.

I’m trying to find a listing of the indicators on the configuration page, but I can’t. Where can I find the possible tags for the appsettings file to represent the indicators?

What would these translate to?
STOCHRSID_candle_period = 900
STOCHRSID_rsi_length = 14
STOCHRSID_stoch_length = 14
STOCHRSID_K = 3
STOCHRSID_D = 3


#3

Sure, so Feeder follows a naming convention. Because these don’t have Default infront of them, they go in the Common section of your appsettings file. Then it is the section of the PT config it goes in first, then the property name, with a change of case instead of _. Examples can be found here. But for the above, it would be something like this:

	"Common": {
		"StochrsidCandlePeriod": "900",
		"StochrsidRsiLength": "14",
		"StochrsidStochLength": "14",
		"StochrsidK": "3",
		"StochrsidD": "3",