Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - gionni

Pages: [1]
1
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 21, 2017, 12:00:15 AM »
Hi,
reporting an issue on poloniex.
I noticed that sometimes BTC_TRADING_LIMIT doesn't get picked up in hot reconfig.
I'm not sure if it's the whole reconfig or just that setting.
In the config file the limit was set at the new price but in the save.json was still the old one.


The FTP client I was using for editing the config files was not updating the date of the file so I believe it was not picked up by the BOT.

2
I believe that it kills all the processes running from the window and then quit the screen session
Thanks for your answer :)
Well not exactly the kind of "smart" exit I am looking for ... but I guess there is no other way...

What were you looking for?

3
I believe that it kills all the processes running from the window and then quit the screen session

4
I made up a little something for those who like to manage the bot manually.
Do take a look at this post by user shacky here if you want to start all your pairs at once instead:
https://gunthy.org/index.php?topic=129.0

Note that I'm using exactly the same command here to launch the bot and I respected the same screen naming. I haven't tested but I believe this script is compatible with shacky's script and you can use gunctl script to stop a single pair also launched with shacky's script.

- configure the botfolder in the script
- make the script executable: chmod u+x gunctl.sh

USAGE:
Start:
Code: [Select]
./gunctl.sh start [strategy] [pair] [exchange or leave blank for poloniex]
Stop:
Code: [Select]
./gunctl.sh stop [pair]
List (running pairs, strategy and exchange):
Code: [Select]
./gunctl.sh list [pair]
View the running bot:
Code: [Select]
screen -r PAIR_NAME
Code: [Select]
#!/bin/bash
########### EDIT PLEASE ###############
# exact folder where gunbot and config files are
botfolder="/your/path/to/gunbot/"
########## NO MORE EDIT ###############


############## DONT EDIT ##############

red=`tput setaf 1`
green=`tput setaf 2`
blue=`tput setaf 4`
reset=`tput sgr0`
cmd=$1
strat=$2
pair=$3
exchange=$4


echo "*********** GUNCTL - v0.0.2 - $( date ) ***************"

if [[ -n "$cmd" ]]; then
  if [[ "$cmd" == "list" ]]; then
  lookup='ps aux'
  printf "%-10s %-10s %-10s\n" "Strategy" "Pair" "Exchange"
  printf "%-10s %-10s %-10s\n" "----------" "----------" "----------"
  $lookup | grep -v grep | grep -v gunctl | grep "node [stepgain|BB|1000trades]" |  awk '{printf "%-10s %-10s %-10s\n",$12,$13,$14}' | sort -nk2
  exit 0
  fi 
  if [[ "$cmd" == "stop" ]]; then
    pair=$2
    if [[ -n "$pair" ]]; then
      if ! screen -list | grep -q "$2"; then
        echo "${red}Pair not running or not started with gunctl... ${reset}"
        exit 0
      else
        echo "${green}Stopping Pair $2${reset}"
        screen -S $2 -X quit
        echo "${blue}Pair $2 stopped.${reset}"
        sleep 0.2
        exit 0
      fi
    else
      echo "Pair is missing"
      exit 0
    fi

  fi
else
  echo "Command missing"
  echo "Usage: gunctl [start [strat] [pair] [exchange],stop [pair],list]"
  exit 0
fi
if [[ -n "$strat" ]]; then
  echo "Strategy: $2"
else
  echo "Strategy is missing"
  exit 0
fi
if [[ -n "$pair" ]]; then
  echo "Pair: $3"
else
  echo "Pair is missing"
  exit 0
fi
if [[ -n "$exchange" ]]; then
  echo "Exchange: $4"
else
  exchange="poloniex"
  echo "Exchange: Poloniex"
fi
cd $botfolder
echo ""
if ! ls | grep -qw "$3"; then
  echo "Config missing for $3"
  exit 0
fi
echo "Checking if pair $3 is running..."
if ! ps aux | grep -v grep | grep -v gunctl | grep "$3"; then
  echo "${red}Pair not running...${reset}"
  echo "${green}Starting $3 pair. ${reset}"

  screen -dmS $3
  screen -S $3 -p 0 -X exec node $2 $3 $4
else
  echo "${green}Pair $3 is already running${reset}"
  sleep 0.2
fi


5
You can use the old BB file to bypass the problem and then relaunch with the new one since the problem looks to be only on cold start.

1. Get a copy of previous BB.js in another folder
2. Rename it to oldBB.js
3. Move it to the gunbot folder
3. Launch "node oldBB BTC_XXX exchange" and wait to see the bot working correctly
4. Stop the bot
5. Launch "node BB BTC_XXX exchange"

6
Beginners & Help / Re: Gunbot Configuration Guide (WIP)
« on: May 01, 2017, 03:58:57 PM »
Adding something I just learned from Gunthar regarding the GAIN setting.
As pointed out this is used before BB can kick in but also:
Quote
Gunthar De Niro, [01 mag 2017, 16:51]:
if the BB calculation is complete but the gap is lower than %GAin it sells at %GAIN

look at BB value you have in yoru bot

and do maths

there is a protection against too tiny BB

Quote
or because BB are too tiny so if it follows BB - highBB value you would trade at loss

so it falls back to %GAIN minimum

So basically even when working with BB don't forget to set your GAIN level appropriately.

PS. +1 For getting a nicely commented config file

7
I would be happy with a simpler double config, one for positive/bullish market, one for downtrend

8
Oh you mean make selllevels all the same
Still maybe playing with the security_margin might be better for limiting bag holding but it's good to know!

9
Quote
If you want to avoid this: raise the % to sell and the bot will not sell at the stop: it will continue with one buy and one sell.
Raise LEVEL 1 and 2?

10
You are obviously right, the sell is still there!
Still at the end of the road, the sell did not go, the bot used twice the amount he was supposed to spend, it did not sell afterwards and so I'm holding the bag I was willing to risk plus another one.
I understand the strategy but I still feel like the bot is not respecting the indication I gave.


11
mmm ok I don't see the sell in my case.
And the problem here I think is that the bot made 2 buys using the max allowed each time without a sell in between so basically it didn't respect the limit of the settings.

12
Hi I believe this is for Gunthar.
I started the bot this morning for a pair, came back after a few hour and I see 2 buys, both for the max btc allowed.
I checked to see if there were 2 bots running the same pair but it is not the case.
I usually understand what the bot is doing but this time I'm lost...

Logs are attached.
CONFIG:

BUYLVL1: 0.8, // first level margin to buy when currency decreases its value (example: buy when currency decreases 1% of EMA)
   BUYLVL2: 0.8, // second level margin to buy when currency decreases its value (example: buy when currency decreases 3% of EMA)
   BUYLVL3: 20, // third level margin to buy when currency decreases its value (example: buy when currency decreases 5% of EMA)
   SELLLVL1: 1, // first level margin to sell when currency increases its value (example: sell when currency increases 2% of paid)
   SELLLVL2: 1, // second level margin to sell when currency increases its value (example: sell when currency increases 5% of paid)
   SELLLVL3: 70, // third level margin to sell when currency increases its value (example: sell when currency increases 10% of paid)
   BUYLVL: 3, // buy level you want your gunbot to reach (example: i want my gunbot to buy when price reaches level 3)
   SELLLVL: 3, // sell level you want your gunbot to reach (example: i want my gunbot to sell when price reaches level 3)
   BTC_TRADING_LIMIT: 0.01,// max amount of BTC balance to use for each pair
   SECURITY_MARGIN: 40, // sell all balance if currency decreases x% after you bought it
   SELL_ON_START:false,
   CANCEL_SELL_ORDERS_ON_START:false,

   MAX_LATEST_PRICES: 30,// limit of latest prices to analyze to determine if price is growing or falling
   MAX_LATEST_DIRECTIONS:30,// limit of latest  price directions ,used in supergun detection

   STARTEMA1: 0.02,// weighted average interval in hours
   STARTEMA2: 0.04,// weighted average interval in hours
   PERIOD: 15,   // candlestick period


PS. Man, sold the pink too early and double buy of a dropping coin... And even so I still have 2% more than yesterday overall :D

13
Technical Support & Development / Re: GUNBOT buying micro amounts
« on: April 15, 2017, 01:12:12 PM »
Good Gunthar, alway on top of things ;)

14
Technical Support & Development / GUNBOT buying micro amounts
« on: April 15, 2017, 10:51:01 AM »
Hey, I have this issue were sometimes GUNBOT buys so little of a currency that it cannot sell it afterwards.
I believe that it just should not be allowed to do so.

For example, it bought 0.00006166 BTC worth of AMP. Now it's trying to sell it but polo doesn't allow it.

Pages: [1]