I find EMACS too much complex for me. I want to concentrate on the analysis of data with Pyhton, so I have looked for and alternative IDE for Python: Pydev.
The steps I have followed are:
- Download and install Eclipse (in reality I had it on my computer).
- Then, download, install and test Phyton.
- Once done, download and install Jython.
- Download and install IronPython.
- Install PyDev.
- Create a new PyDev project.
- I have created a hello.py file with print(“hello world”), then I have debugged it and it worked.
- Create a package to gather all the information.
The set-up of the environment is very well explained. You first have to configure the interpreter, then you can develop all you need. In my case I’m starting importing some finance data from Yahoo Finance.
- Using Windows>Properties>Python Interpreter , install library “numpy” using “pip” as installer. This step is crucial to me as Python interpreter just work on PyDev in my computer.
I’m sure EMACS runs faster and it’s more efficient than Eclipse, but the point is that now I can concentrate on the development of the scripts I want to implement. 🙂
What IDE should I start with?
I have asked about some different IDEs for Python and this was the short list: EMACS, jupyter, syder and anaconda.
Then, I asked my friend: what is the more convenient for a basic learner as me? EMACS.
So this is the one I have installed. The basis of how to use EMACS can be read here. The guidelines recommends the installation of Elpy so this is the next step I have done.
Elpy – Python Development
Emacs is distributed with a python-mode (python.el), but if we want to have a more sophisticated IDE you can install Elpy (Emacs Lisp Python Environment) package.
Before to install Elpy, you have to install these 2 packages:
- Flake8: flymake-python-pyflakes.
The document I used to install it is this one.
The issue I’m finding is that the these 2 packages are legacy and they seem to not work properly. I’m sure that in reality the issue is that I’m not able to enable them in the right way or to enable python properly. I’m stuck here by the moment.
Some basic notes about the python files extensions:
.py: This is normally the input source code that you’ve written (the basis).
: This is the compiled bytecode. If you import a module, python will build a
*.pyc file that contains the bytecode to make importing it again later easier (and faster).
.pyo: This is a
*.pyc file that was created while optimizations (
-O) was on.
.pyd: This is basically a windows dll file. http://docs.python.org/faq/windows.html#is-a-pyd-file-the-same-as-a-dll
EMACS basic commands I have learned today.
- M-x list-packages: list the available packages you have in EMACS
- M-x customize-group: enable you to customize a package (in my case: “package”. I have added Melpa packages to the list so these packages can be installed.
- M-x package-install: to perform the installation of a package.
This video shows you how to install a package: .Emacs #3 – Installing Packages and Extensions. The series of videos are useful for new users as me.
Family traveling, me preparing the vacations to the Pyrenees mountains, and suddenly the possibility to ride this race. For sure I’m still far away of the shape I need for the Pyrenees, but this was a good check point to know how I was.
The total distance, taking into account the launched start was 62.17 km that I covered in 4:22 hours. The majority of the route was a wide path with a lot of stones in the middle.
I was making well till the km 50 where a steep slope told me: “you should save some energy for the other 12 kms”.
The roads closed to the coast have really nice view of the coast. The fog did not let me see Africa.
The strong wind from east was present the whole ride and it made the day a little bit difficult.
This book contains basic concepts and approach (step by step) for does that want to initiate themselves on Quantitative trading. The focus is on statistical arbitrage trading, that deals with the simplest financial instruments: stocks, futures, and sometimes currencies.
The chapters cover the steps a trader should take:
- The Whats, Whos, and Whys of Quantitative Trading,
- Fishing for Ideas,
- Setting Up Your Business,
- Execution Systems,
- Money and Risk Management,
- Special Topics in Quantitative Trading, (reading it now)
You can follow the author blog that contains further valuable information and some nice examples.
A short list of common pitfalls related to how the back-test program is written:
- Survivor-ship bias: data does not contain companies that have fallen bankruptcy.
- Look-Ahead Bias: this phenomenon happens when you are using information that was available only at a time ahead of the instant the trade was made. For instance, “Buy when the stock is within 1 percent of the day’s low”.
Data-Snooping Bias: the use too much parameters that make you build an over-optimized model. A rule of thumb: 5 parameters.
- Sample size: you need enough data to back test, how much? As a rule of thumb, let’s assume that the number of data points needed for optimizing your parameters is equal to 252 times the number of free parameters your model has. For instance, you define a daily trading model with three parameters, then you should have at least three years’ worth of back-test data with daily prices.
- Out-of-Sample Testing: divide your historical data into 2 parts. Use the first part for training, and keep the second part to test the resulting model.
offers a set of courses oriented on programming and data scientist. I found some basic courses about python that have helped me to understand how the language works and practice with a good balance of theory and exercise.
I have also done a couple of chapters related to data import and data visualization that helped me to understand how to work on it.
The main goal is to learn, but not just through the completion of courses or certifications. After the achieving the PMP certification I though about a project to focus on programming and data analysis.
My goal is Learn Python is my next project. I have defined 3 months of project where I would like to achieve a goal.
Following the V2MOM model:
- Vision: Be able to analyze data and predict behaviors.
- Values: have fun, learn a lot, build a team with Dani, do practices and more practices.
- Method: learn python, learn about patterns.
- Obstacles: Time.
- Measures: have an environment where I test a pattern with real time data from an external source. Have a list of learned lessons and experience.
Death line = December 2017