QuantConnect / QuantConnect/Lean
User Defined Crisis Event
Open
Nobody has claimed this yet.
feature
- Dominant language
- C#
- Stars
- 21.7k
- Forks
- 5.3k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 34
Description
Expected Behavior
We can define a crisis event period in the algorithm. E.g.:
AddCrisisEvent("Lord of the Rings Trilogy", new DateTime(2001,12,19), new DateTime(2003,12,17));
The report will display this event.
Actual Behavior
The crisis events are pre-defined.
Potential Solution
N/A
Checklist
- I have completely filled out this template
- I have confirmed that this issue exists on the current
masterbranch - I have confirmed that this is not a duplicate issue by searching issues
- I have provided detailed steps to reproduce the issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing predefined crisis-event implementation and the report path; the issue names AddCrisisEvent as the proposed entry point but does not identify files or tests. Trace how predefined events reach the report, then determine how user-defined date ranges should follow that path. Done means a caller can define the Lord of the Rings period, and the report displays it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100