Skip to content

Latest commit

 

History

History
36 lines (33 loc) · 3.37 KB

Project.md

File metadata and controls

36 lines (33 loc) · 3.37 KB
Raw

Course Project

Team List (Presentation Order)

Group Members Repo
0 Feng Xi Detecting Financial Fraud with First Digit Law
1 Yang Hengyi Credit Default Prediction (HSBC)
2 Ma Fangyuan, Zhu Zerun Credit Default Prediction (HSBC)
3 Zhang Yuyang, Ge Ruiyang Usage of transaction data to predict credit event (HSBC)
4 Xiong Zichao, Yuan Yutao Recession Identification and Prediction
5 Li Yuhui Prediction of BTC price with Tweets(X) data
6 Gong Jiaxin, Wang Xin Stock Prediction Based on Report Similarity
7 Cheng Lei, Li Chang How to Capture the Patterns of Price and Volume data in Long Time Series
8 Zhang Qiuyan, Pan Kangyu Home Credit - Credit Risk Model Stability with Kaggle data
9 Chen Yichao, Yang Honggui Credit Default Prediction (HSBC)
10 Niu Yitong Niu, Deng Tingqin Home Credit - Credit Risk Model Stability with Kaggle data

Project Guidline

  • Report should be consist of the summary in README.md and the execution in python notebooks .ipynb. ( .pdf, .ppt, .doc NOT accepted.)
  • In the README.md summary,
    • You may update your proposal file.
    • briefly describe your motivation, goal, data source, result and conclusion.
    • A few figure or table for summary is recommended.
    • Use links to data or .ipynb files (see past year examples below)
  • In the .ipynb execution,
    • Put command cell and edit cell (comments) in a balanced way. (Do not only put code!)
    • Put a brief table of contents with links (example: PML)
    • You may breakdown code into several .ipynb files by function (e.g., data cleaning, learning, result analysis). In that case, make sure to save intermediate result into file so that I can run the later steps (result analysis) without running previous steps (data cleaning, learning).
    • The use of .py file should be strictly restricted to function or class only. (Do not put any learning procedure in .py)
    • I should be able to reproduce the result from your code. Your code should run with no error. Code with error will be severely deduct your score. Make sure to run your code in a new session.
  • Other considerations:
    • Make sure the workload within team is balanced. (Add your team members to collaborators, each team members commit codes, etc)
    • There should be no secret component (e.g., stock trading strategy)
    • Creative (out-of-textbook) ideas are recommended for better result or result analysis
  • Deadline for updating report is 11.21 Sunday Midnight (11:59 PM)