Access the backtest dir location from within the script.

Hi John

Sorry, but there is no easy solutions for this one. It requires tempering things in the Docker level, so we don’t recommend members to do so. A workaround would be ”cd” to the last folder in the root project backtest result dir.

Best
Louis

Thanks Louis for getting back to me:

A workaround would be ”cd” to the last folder in the root project backtest result dir.

Can you tell me more about this? Say if my project structure was like so:

Lean Init Dir: /Users/username/Documents/dev/quant/strategies/

Project Dir: 
`/Users/username/Documents/dev/quant/strategies/project_name/`

If it is too hard to access the backtest dir location from within the algo, Is there a way I can output a file somewhere where I can access it after? I want to output this data so I can chart it on my own charting library. 

self.path_to_data = "chart_data.csv"
self.df.to_csv(self.path_to_data, encoding='utf-8', header=False, sep=';', index=False)

When I run the above I cannot find the file anywhere, is it being stored somewhere in the container? 

Would I need to add a volume to the container so I can access this location, or is there a built in way to do this already
 

CONTAINER ID   IMAGE                      COMMAND                  CREATED        STATUS                  PORTS     NAMES
69050ae4b98f   quantconnect/lean:latest   "bash /lean-cli-star…"   1 second ago   Up Less than a second             lean_cli_ef29c05d86d944aca6be0b6ab261407b

I believe I worked this out, the backtest folder on the local os is mounted to a /Results folder within the quantconnect/lean container so if you output what ever you want into /Results/ it will appear in your backtest folder. So:

self.path_to_data = "/Results/chart_data.csv"