A better Trader: Difference between revisions
No edit summary |
|||
Line 6: | Line 6: | ||
** p_user_->findBrokerAccount(account_id); | ** p_user_->findBrokerAccount(account_id); | ||
** ba.getSPAS(run_id,&spit,&asit) | ** ba.getSPAS(run_id,&spit,&asit) | ||
** g_p_local->readRunHistory() | ** g_p_local->readRunHistory() (does rh allocations) | ||
** atc_.thread_analyzeHistory(aggressiveness, rh, *papsAnalysis) | ** atc_.thread_analyzeHistory(aggressiveness, rh, *papsAnalysis) | ||
*** generateAPSFromAggressiveness(aggressiveness, apsAnalysis) | *** generateAPSFromAggressiveness(aggressiveness, apsAnalysis) | ||
Line 13: | Line 13: | ||
** save papsAnalysis | ** save papsAnalysis | ||
** atc_.thread_buildRunJSON(rh) | ** atc_.thread_buildRunJSON(rh) | ||
** deallocate(rh) | |||
Auto-analysis selected (aggressiveness=0) | Auto-analysis selected (aggressiveness=0) |
Revision as of 11:50, 15 July 2016
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 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 no-adjust
- 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
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)