Projects

Environments

Introduction

An environment is everything that's installed on a machine where a program is executing. The Lean cloud image that runs the backtesting, research, and live trading nodes in QC Cloud is the latest master branch on the Lean GitHub repository. When you open a project, a new environment starts running with this branch.

View Running Environments

The Projects page displays all of your running environments in your current organization. To view the page, log in to the Algorithm Lab and then, in the left navigation menu, click Projects.

To open one of the environments, click the project name.

To stop the environments, click the stop icon next to a project name.

The left navigation bar of the Algorithm Lab also shows the running environments underneath Projects. The blue environment represents the environment that's currently open. The gray environments represent the environments that are currently minimized.

Coding Session Quotas

If you have a project open, it uses a coding session. Your account can have up to one coding session across all of your free organizations. If you connect as a paid organization, your account can have multiple active coding sessions. The following table shows how many active coding sessions you can have on each organization tier:

TierCoding Session Quota
Quant Researcher2
Team4
Trading Firm8
Institution16

The quota for free organizations is a global quota, so you can have one active coding session across all of your free organizations. The quotas for paid organizations are at the organization level. Therefore, if you are in two Quant Researcher organizations, you can have two active coding sessions in one of those organizations and another two active sessions in the other organization. These paid tier quotas are for each account, not for the organization as a whole. For instance, a Trading Firm organization can have more than eight members and all of the members can simultaneously work on projects within the organization.

LEAN Engine Branches

Custom Lean engine branches give you access to custom versions of Lean in the QuantConnect web IDE to run backtests, launch research notebooks, and deploy live trading strategies. The custom versions include historical master branches of Lean and other feature branches. If you are in an organization on the Trading Firm or Institution tier, you can change the Lean engine branch that's used in your projects. These branches are created by making pull requests, which are reviewed by the Lean team.

Change LEAN Engine Branches

Follow these steps to change the Lean engine branch that's used to run your backtests and live trading algorithms:

  1. Open the project for which you want to change the Lean engine branch.
  2. In the Project panel, click the LEAN Engine field and then click a branch from the drop-down menu.
  3. (Optional) Click About Version to display the branch description.
  4. If you want to always use the master branch, select the Always use Master Branch check box.
  5. Click Save.

Changing the Lean engine branch only affects the current project. If you create a new project, the new project will use the master branch by default.

You can also see our Videos. You can also get in touch with us via Discord.

Did you find this page helpful?

Contribute to the documentation: