Hi all,
After having seen Chris's videos and Dave Steckler's reviews, I am pretty jazzed at the thought of being able to create my own templates, that will identify BUY and SELL signals, based on things such as BONGO, FORCE, IAN PCT B, SAR, etc. There are tons of Edgerater scans, so the sky is the limit.
I am not a programmer, but I am determined. I have been able to create Edgerater templates, but so far a working EdgeClub template hasn't been completed. I am attaching a spreadsheet with my first attempt (in the attached zip file), with the hopes that a simple answer may be at hand. If I get this darn thing working, I'll post it to the forum.
In the attachment, I have added text boxes to give some explanation of what I was doing or was hoping to achieve. My starting point was another template that I knew worked, and my method was basically to swap out the Edgerater system scan information, with that in the template and cross my fingers that it would work. It did not, and I was not sure how to troubleshoot where the issue lie, so I am asking for help here in the forum.
Thank you
PS For the Administrator, an *.xlsx file was not allowed for upload, so I used WinZip to get around that issue.
Creating a custom EdgeClub Template
Moderator: Chris White
Creating a custom EdgeClub Template
- Attachments
-
- BONGO_TEMPLATE_ATTEMPT.zip
- (26.15 KiB) Downloaded 2380 times
-
- Posts: 212
- Joined: Mon Nov 29, 2010 9:21 pm
Re: Creating a custom EdgeClub Template
Hi Mike,
I have modified this template by adding comments that you can see if you view it in Excel. In summary, to get it to work the way you want you need to do the following:
1. Create a ChartScript that is a generic 'EntryExit_State' script that will take any other chart script as an entry script and any as an exit script. I have given the code within the comments too.
2. Change the column headings on the 'System' sheet to refer to this new script. Because the script will be in your 'My Scripts' area you need to prefix the name of the script with 'My'. You will see how I have done that in the comments in the file.
3. Change the range referred to by ERF_ on the 'System' sheet
4. Change the formatting rules referred to by ER_SETTING_FORMATRULES on the 'Parameters' sheet.
Once you have done that you have a generic template that you can add as many systems as you like.
Chris.
I have modified this template by adding comments that you can see if you view it in Excel. In summary, to get it to work the way you want you need to do the following:
1. Create a ChartScript that is a generic 'EntryExit_State' script that will take any other chart script as an entry script and any as an exit script. I have given the code within the comments too.
2. Change the column headings on the 'System' sheet to refer to this new script. Because the script will be in your 'My Scripts' area you need to prefix the name of the script with 'My'. You will see how I have done that in the comments in the file.
3. Change the range referred to by ERF_ on the 'System' sheet
4. Change the formatting rules referred to by ER_SETTING_FORMATRULES on the 'Parameters' sheet.
Once you have done that you have a generic template that you can add as many systems as you like.
Chris.
Re: Creating a custom EdgeClub Template
Thanks for the comments on the template and the script. I have a few follow-up questions.
I went to create the generic ENTRYEXIT_STATE script and ran into a few problems. Probably minor, but I can't find info to help me resolve it in the documentation:
I started with the script that you provided
entrysig:= FML(ENTRYSCRIPT);
exitsig:= FML(EXITSCRIPT);
system:= SCALEINLT(entrysig, exitsig, 1);
Buy1: system == 1 & REF(system,1) == 0;
Hold: system > 0 & (REF(system,1) == system);
Exit: system == 0 & REF(system,1) > 0;
On the parameters tab, I then went and added AUBB, BLBB, BongoDailyDn, BongoDailyUp. The default was "test", so I changed that to 20 for the indicators. I also set the parameter type to "Indicator". Hit compile, and ran into errors.
Error ID: CS0103 The name(s): 'ENTRYSCRIPT', 'EXITSCRIPT', 'SCALEINLT' does not exist in the current context.
I tried various permutations to resolve the errors, starting with swapping out the ENTRYSCRIPT and EXITSCRIPT with the actual name of the indicators, and later getting rid of the Bongo indicators to just have the AUBB, BLBB indicators, but could not get past the error.
Can you help me with this, please? Thanks for your support.
-
- Posts: 212
- Joined: Mon Nov 29, 2010 9:21 pm
Re: Creating a custom EdgeClub Template
Hi Mike,
You're nearly there. You have the script tab set up correctly like this: But you need to set up the parameters tab like this: Explanation:
The parameters to the script are ENTRYSCRIPT and EXITSCRIPT, meaning that you provide these scripts as inputs whenever you call this script. The default parameter values are Scan.BLBB(20,2) and Scan.AUBB(20,2), meaning that when you first drop the script onto a chart area it is set with these two inputs which you can the change in the 'Area Properties' panel.
So now when you create your custom template, you provide the names of the scripts that you want to use for entry and exit in the cell that is named 'ERF_x'. In the case of your BongoDailyUp and BongoDailyDn system that would be:
That represents the text that needs to be in the ERF_x named cell but with a bit of Excel text manipulation I'm sure it's possible to write an Excel formula in the cell that creates that text for you based on two other cells, one containing only
Scan.BongoDailyUp[Event]
and the other containing
Scan.BongoDailyDn[Event]
Thanks,
Chris.
You're nearly there. You have the script tab set up correctly like this: But you need to set up the parameters tab like this: Explanation:
The parameters to the script are ENTRYSCRIPT and EXITSCRIPT, meaning that you provide these scripts as inputs whenever you call this script. The default parameter values are Scan.BLBB(20,2) and Scan.AUBB(20,2), meaning that when you first drop the script onto a chart area it is set with these two inputs which you can the change in the 'Area Properties' panel.
So now when you create your custom template, you provide the names of the scripts that you want to use for entry and exit in the cell that is named 'ERF_x'. In the case of your BongoDailyUp and BongoDailyDn system that would be:
Code: Select all
My.EntryExit_State(Scan.BongoDailyUp[Event],Scan.BongoDailyDn[Event])[AS_TEXT]
Scan.BongoDailyUp[Event]
and the other containing
Scan.BongoDailyDn[Event]
Thanks,
Chris.
Re: Creating a custom EdgeClub Template
Hi Chris,
Been bogged down since your posting, and now am getting back to finalizing the template. However, I ran into another error:
CSO103 - The name 'SCALEINLT' does not exist in the current context
This pertains to the system, I believe - where do we define this value? Thanks again.
Been bogged down since your posting, and now am getting back to finalizing the template. However, I ran into another error:
CSO103 - The name 'SCALEINLT' does not exist in the current context
This pertains to the system, I believe - where do we define this value? Thanks again.
-
- Posts: 212
- Joined: Mon Nov 29, 2010 9:21 pm
Re: Creating a custom EdgeClub Template
Hi Mike,
That function should be part of the core EdgeClub software. Please make sure that you are running version 6.0.0.16. You can find the version on the login screen:
Or from the Ribbon Menu once in the EdgeClub application:
That function should be part of the core EdgeClub software. Please make sure that you are running version 6.0.0.16. You can find the version on the login screen:
Or from the Ribbon Menu once in the EdgeClub application:
-
- Posts: 212
- Joined: Mon Nov 29, 2010 9:21 pm
Re: Creating a custom EdgeClub Template
Also, in version 6.0.0.16 I have added the EntryExit_State script as a system script so you do not need to define it yourself in your 'MyScripts' area. Just make sure when referencing it that you...
Do Not Use:
In Version 6.0.0.16 and higher USE:
Do Not Use:
Code: Select all
My.EntryExit_State(Scan.BongoDailyUp[Event],Scan.BongoDailyDn[Event])[AS_TEXT]
Code: Select all
EntryExit_State(Scan.BongoDailyUp[Event],Scan.BongoDailyDn[Event])[AS_TEXT]