A better Trader

From Bitpost wiki
Revision as of 17:55, 27 November 2016 by M (talk | contribs)

CI

MASTER SCRIPT: atci

RUN LIVE at bitpost.com:

m@bitpost rs at
m@bitpost # if that doesn't work, start a session: screen -S at 
m@bitpost cd ~/development/thedigitalage/AbetterTrader/server-prod
m@bitpost atlive
 ========================================================
    *** LIVE MODE ***
 ========================================================
CTRL-A CTRL-D

ANALYZE PSEUDO (REFACTOR THREE)

Single aggressiveness slider value selected:

  • analysis page requests analysis via AJAX: user selects aggressiveness
  • APIGetRunAnalysis::handle_call()
    • p_user_->findBrokerAccount(account_id);
    • ba.getSPAS(run_id,&spit,&asit)
    • g_p_local->readRunHistory() (does rh QAB pB_ allocations)
    • atc_.thread_analyzeHistory(aggressiveness, rh, *papsAnalysis)
      • generateAPSFromAggressiveness(aggressiveness, apsAnalysis)
      • create MemoryModel, AppUser, BrokerAccount
      • pba->analyze(rh)
    • save papsAnalysis
    • atc_.thread_buildRunJSON(rh)
    • deallocate(rh)

Auto-analysis selected (aggressiveness=0)

carefully select (0..n) APSs to test based on a range of aggressive levels
then do a small monte carlo around the best result
only apply to one stock at a time (unlike before where we ran all - revisit this)

TRADE PSEUDO

load from SQL tables into Major Objects (std::unordered_sets of PersistentIDObjects)

API PSEUDO

   APIGetRunLive::handle_call()
       g_p_local->getRunLiveJSON()
           readRunQAB(s_str_db_name...)
           (SAME as readRunLive!!)
   APIGetRunHistory::handle_call()
       g_p_local->getRunHistoryJSON()
           readRunHistory
               readRunQAB

DEBUG LIVE

NOTE that you WILL lose stock quote data during the debugging time, until we set up a second PROD environment.

  • WRITE INITIAL DEBUG CODE in any DEV environment
  • UPDATE DEBUGGER to run with [live] parameter instead of debug ones
  • COPY DATABASE directly from PROD environment to DEV environment: atimport prod
  • STOP PROD environment at_server
  • DEBUG. quickly.  ;-)
  • PUSH any code fix (without debug code) back to PROD env
  • RESTART PROD and see if the fix worked
  • REVERT DEV environment: clean any debug code, redo an atimport and reset the debugger parameters

Qt Creator settings

  • Make sure you have already run [atbuild] and [atbuild debug].
  • Open CMakeLists.txt as a Qt Creator project.
  • It will force you to do CMake - pick cmake-release folder and let it go.
  • Rename the build config to debug.
  • Clone it to release and change folder to release.
  • Delete make step and replace it with custom build:
./build.sh
(no args)
%{buildDir}
  • Create run setups:
you have to use hardcoded path to working dir (or leave it blank maybe?): /home/m/development/thedigitalage/AbetterTrader/server
[x] run in terminal
debug args: localhost 8000 test reanalyze (matches attest)
release args: localhost 8080 live (matches atlive)