Improve Pinescript Harmonic Pattern Detector
Budget: $15 – $25 AUD
I am looking for a skilled freelancer to help improve an existing Pinescript Harmonic Pattern Detector. The script is by reees and is called the "Harmonic Pattern Detection, Prediction, and Backtesting System". It is available on Tradingview. I have attached the code here.
Objectives (in order of priority):
1. Add a new Input variable for custom entry alert.
2. Add new Input variables for custom TP1, TP2 and SL alerts, and add the ability to output these alerts (currently the script does not have the ability to create alerts for TPs and SL.)
3. Remove all code not related to Shark patterns: We want a leaner version of the script without all the other pattern detection. We are only interested in Sharks.
4. If possible, remove "potential patterns" from the indicator. We are not interested in the indicator's ability to detect or paint potential patterns, UNLESS this is essential to detecting and painting complete patterns. If the feature isn't necessary, we want it removed.
5. Add new Input variable for minimum size pattern: Filter out patterns below a certain size. Use the distance between point D and TP1 (in pips) to remove patterns that do not meet the threshold.
6. Add new Input variable to be able to move the Results Table to a different location e.g. bottom right.
7. Add new input variable for TP3
8. Remove "Enter after point C" functionality. We only use "Enter after point D".
NOTE: While the script does re-paint, you must understand how/why this happens and therefore why it DOES NOT matter. Entries DO NOT repaint. The pattern detection itself may repaint when new data comes in from the market. The repaint may extend the size of the detected pattern or move point D. This may therefore result in a repaint of the TP and SL levels as well, however, the original entry DOES NOT repaint.
If the TP/SL levels repaint, the alerts for TP/SL should only trigger on the new repainted levels.
Any further questions please feel free to ask.
Objectives (in order of priority):
1. Add a new Input variable for custom entry alert.
2. Add new Input variables for custom TP1, TP2 and SL alerts, and add the ability to output these alerts (currently the script does not have the ability to create alerts for TPs and SL.)
3. Remove all code not related to Shark patterns: We want a leaner version of the script without all the other pattern detection. We are only interested in Sharks.
4. If possible, remove "potential patterns" from the indicator. We are not interested in the indicator's ability to detect or paint potential patterns, UNLESS this is essential to detecting and painting complete patterns. If the feature isn't necessary, we want it removed.
5. Add new Input variable for minimum size pattern: Filter out patterns below a certain size. Use the distance between point D and TP1 (in pips) to remove patterns that do not meet the threshold.
6. Add new Input variable to be able to move the Results Table to a different location e.g. bottom right.
7. Add new input variable for TP3
8. Remove "Enter after point C" functionality. We only use "Enter after point D".
NOTE: While the script does re-paint, you must understand how/why this happens and therefore why it DOES NOT matter. Entries DO NOT repaint. The pattern detection itself may repaint when new data comes in from the market. The repaint may extend the size of the detected pattern or move point D. This may therefore result in a repaint of the TP and SL levels as well, however, the original entry DOES NOT repaint.
If the TP/SL levels repaint, the alerts for TP/SL should only trigger on the new repainted levels.
Any further questions please feel free to ask.