Back

Undo

Is there a method of undo-ing an edit? Between my laptop and the editor I get some crazy edits sometimes.
Update Backtest








Hey Andrew! Pressing ctrl+Z will undo your last edits,

There is also:
Ctrl + / Toggle comments on selected code
Ctrl + Up/Down Increase/decrease font size
Ctrl + S Save document and compile project
Ctrl + D Remove line
Alt + Up/Down Move line up/down
Alt + Shift + Up/Down Copy lines up/down
1

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.


Hi Jared

Thanks for that, much appreciated.
0

Hi Andrew,

You might want to try a different workflow. I suggest you git fork the main Lean project into your github account and clone it to your local machine. (Because I develop on Windows, I use Visual Studio 2013 Community which is free). I then clone the basic algorithm and start hacking from there.

If you need back test data, look at the QuantConnect tools. They are quite good.

Once it compiles and runs back test locally well, I make a new project called {algorithm-name}QC and take out any debugging stuff I may have added in while developing. For example, I will write my indicator data to a file and make excel charts to see what they look like in a chart. I remove the System.IO using statements and the calls to my local file system. They are not white-listed in QC.
Then I just copy my strategy up to a QC project and the JIT compiler will tell me when I got something weird and I can correct it on the web site.

Then you run a back test on the web site. If it works you are ready to deploy.

I usually to compile and run a project many times before I actually run a back test on QC. But my back tests usually compile without warnings or errors. It saves a lot of time. The other advantage is that while debugging you can step into QC code on your local machine when you have a problem, which you cannot do in a back test.

Thank you Jared and company for making Lean open source. I bless you every day.

Nick
1

Hi Nicholas

That does sound interesting. It gets around the Log limits etc I imagine. (it would probably help a problem I have atm).
0

Update Backtest





0

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.


Loading...

This discussion is closed