You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some EOD models, it makes sense to place orders as 'market on open', rather than the default Zipline logic of 'market on close'. It's quite simple really and I've modded my own setup for this, and I thought might be of interest to the community.
The 'market on close' logic is currently hard coded in the slippage.py file, and I suppose the reason for that is that Quantopian assumed intraday, minute data.
The simple solution would be to add a field input argument to the constructors in the slippage.py file. Quick, easy and gets the job done.
The text was updated successfully, but these errors were encountered:
Just a friendly suggestion:
For some EOD models, it makes sense to place orders as 'market on open', rather than the default Zipline logic of 'market on close'. It's quite simple really and I've modded my own setup for this, and I thought might be of interest to the community.
The 'market on close' logic is currently hard coded in the slippage.py file, and I suppose the reason for that is that Quantopian assumed intraday, minute data.
The simple solution would be to add a field input argument to the constructors in the slippage.py file. Quick, easy and gets the job done.
The text was updated successfully, but these errors were encountered: