Powerlanguage - using functions to construct signals

June 10th, 2020, 05:00 PM

I tried to transform a signal into a generic function and reuse it into a signal. It seemed to work, but, after some updates in OS, I am not able to make it work anymore (the same signal and the others, meanwhile, I wrote). Maybe some name conflict (variable names?) came up. Is it generally possible to make this transformation? Which rules must be followed? Thank you in advance for any suggestions.

June 11th, 2020, 05:28 PM

Nabla76

I tried to transform a signal into a generic function and reuse it into a signal. It seemed to work, but, after some updates in OS, I am not able to make it work anymore (the same signal and the others, meanwhile, I wrote). Maybe some name conflict (variable names?) came up. Is it generally possible to make this transformation? Which rules must be followed? Thank you in advance for any suggestions.

I have just started using PowerLanguage, but I have a lot of EasyLanguage experience, which is very similar. First, a basic question: Did you try to recompile your function(s)? Maybe they need to be recompiled.

Here is my approach to turning an indicator into a function:

Get the indicator code
Create a new function: do not use any special character except underscore "_". I use a prefix before every function, example HSC_ is my prefix, so a function might be called HSC_NoLag_MA. This helps avoid naming conflicts
Remove Alert criteria from the code
Remove Plot criteria
If the function generates more than one value, then create the 'numericref' or 'stringref' inputs to store the values to be used (see example below)
Add a return statement (see example below)
Compile and correct any errors
Test the function in an indicator or signal

Here is an indicator that I turned into a function. I used a Return Type of TrueFalse (boolean), because my function generates three values that I need:

Code

// Alligator Indicator
[LegacyColorValue = TRUE];

Plot1(XAverage(MedianPrice,21)[8],"Plot1");  // Jaw
Plot2(XAverage(MedianPrice,13)[5],"Plot2");  // Teeth
Plot3(XAverage(MedianPrice,8)[3],"Plot3");    // Lips

Here is the function:

Code

//    HSC_Alligator Function
//    Based on Alligator indicator

Inputs:
	o_Jaw(NumericRef),
	o_Teeth(NumericRef),
	o_Lips(NumericRef) ;

o_Jaw = XAverage(MedianPrice,21)[8]   ;  
o_Teeth = XAverage(MedianPrice,13)[5] ;
o_Lips = XAverage(MedianPrice,8)[3]   ;

HSC_Alligator = True ;   // the return value

Here is how I would call the function:

Code

vars:
   o_Jaw(0),
   o_Teeth(0),
   o_Lips(0) ;

Value1 = HSC_Alligator(o_Jaw, o_Teeth, o_Lips) ; 

condition1 = o_Jaw > o_Teeth and o_Teeth > o_Lips ;

You can use the same approach with converting a Signal.

I hope this helps!

~vmodus

June 11th, 2020, 05:32 PM

vmodus

I have just started using PowerLanguage, but I have a lot of EasyLanguage experience, which is very similar. First, a basic question: Did you try to recompile your function(s)? Maybe they need to be recompiled.

Here is my approach to turning an indicator into a function:

Get the indicator code
Create a new function: do not use any special character except underscore "_". I use a prefix before every function, example HSC_ is my prefix, so a function might be called HSC_NoLag_MA. This helps avoid naming conflicts
Remove Alert criteria from the code
Remove Plot criteria
If the function generates more than one value, then create the 'numericref' or 'stringref' inputs to store the values to be used (see example below)
Add a return statement (see example below)
Compile and correct any errors
Test the function in an indicator or signal

Here is an indicator that I turned into a function. I used a Return Type of TrueFalse (boolean), because my function generates three values that I need:

Code

// Alligator Indicator
[LegacyColorValue = TRUE];

Plot1(XAverage(MedianPrice,21)[8],"Plot1");  // Jaw
Plot2(XAverage(MedianPrice,13)[5],"Plot2");  // Teeth
Plot3(XAverage(MedianPrice,8)[3],"Plot3");    // Lips

Here is the function:

Code

//    HSC_Alligator Function
//    Based on Alligator indicator

Inputs:
	o_Jaw(NumericRef),
	o_Teeth(NumericRef),
	o_Lips(NumericRef) ;

o_Jaw = XAverage(MedianPrice,21)[8]   ;  
o_Teeth = XAverage(MedianPrice,13)[5] ;
o_Lips = XAverage(MedianPrice,8)[3]   ;

HSC_Alligator = True ;   // the return value

Here is how I would call the function:

Code

vars:
   o_Jaw(0),
   o_Teeth(0),
   o_Lips(0) ;

Value1 = HSC_Alligator(o_Jaw, o_Teeth, o_Lips) ; 

condition1 = o_Jaw > and o_Teeth and o_Teeth > o_Lips ;

You can use the same approach with converting a Signal.

I hope this helps!

~vmodus

Thank you so much! Your sample is very detailed, I will definitely try your approach. I will surely let you know how it works! Thanks again!

June 12th, 2020, 09:24 AM

Nabla76

Thank you so much! Your sample is very detailed, I will definitely try your approach. I will surely let you know how it works! Thanks again!

You're welcome. I realize I made a mistake with the condition1 in the example, but you probably would have figured that out. Here is the correction:

Code

condition1 = o_Jaw > o_Teeth and o_Teeth > o_Lips ;

~vmodus

Powerlanguage - using functions to construct signals

Discussion in MultiCharts

Powerlanguage - using functions to construct signals