When a new block module is created there is an option to include additional default scripts in addition to the required script sections that are required in the Block-Type selected:

Blox Editor New Blox Creation Dialog

 

This next table provides the default script sections in the various types of block modules.  Default script sections can added by enabling the "Include Default Scripts, or they can be added after the blox is created using the "Add Script Section" option.  When a script section is needed that is compatible with the blox module type, adding a script section to a module is easy, and is often helpful.  

 

Some script sections define, and can change a blox type after a defining script section is added.  For example, any blox that contains Rank Instruments or Filter Portfolio will be defined as a Portfolio Manager blox.  Any script that contains any of the Risk Manager's scripts (see rows 20 to 23 in the table image below) will be defined as a Risk Manager blox.

 

Scripts in this image table use Default Script Red Letter Green background colored symbol to show which script section are included when blox is created and the blox creation dialog option to include Optional Scripts where the Blox creation option Default Scripts can be automatically added.

Click to Enlarge; Click to Reduce.

 

Legend:

Description:

Script Name Defines Module Type

Cells where this is displayed locate the script names that define the type of module.

Script Name Included as a Default Script

Script name section added when the Include Default Scripts option is enabled.

Optional Script Names Often Added

Can Fill Order scripts only execute when either an entry has been filled in the market, and when an exit order has closed an active position, or any of the position's unit segments.

 

Custom script execute when their names are called using the Script Object's Execute function

Intraday Script Section

Intraday script section executes for each intraday record.

 


NOTE:

Blox Script name rows in the above image that have a Legend 'D' mark entered in the Instrument column, those script names will automatically provide IPV variables with context so they can be accessed and changed.

 

Instrument scripts that automatically provide context, will execute each instrument symbol in the portfolio that has a date record in its file that aligns with the system testing date in progress.   For example, if there are ten-instruments in the portfolio, each instrument script will execute one time on on each of the system testing dates.  When a instrument doesn't have a date that aligns with the current system test date, the instrument object instrument.tradesOnTradeBar property, will be FALSE, and that instrument won't be tested again until has date record that aligns with the system testing date.  When an instrument has a date record that aligns with the next system testing date, the instrument.tradesOnTradeBar property will be TRUE.

 

There are exceptions with the script sections that contained a red Legend 'D' and a green background cell.  These scripts have dependencies that are explained in the Legend notes.

 

Instrument scripts without any Legend symbols, do not automatically provide instrument context, and they do not process each instrument in the portfolio.  Howevr, instruments can be processed in these script section, but they must be loaded and processed using the LoadSymbol function using a repeatative loop structure, and they must use Instrument-BPV type variable that is created in the BPV variable creation dialog.

 

Links:

Blox Script Timing, Blox System Placement, Blox Types, Trading Objects References

See Also:

 

 


Edit Time: 4/14/2018 3:03:12 PM


Topic ID#: 172

 

Created with Help & Manual 7 and styled with Premium Pack Version 2.80 © by EC Software