#

Inputs

Description

Values & examples

 2.3.1  Use TimeCriticalClose Rescue Mode?  That is toggle to allow / disable TimeCriticalClose rescue mode True/False  2.3.2  Panic motive that allow CritClose

<utilized in mixture with PanicClose>

This selection is used when consumer wish to restrict CritClose to being executed ONLY when the grid is in throughout Panic mode (detected by PanicClose bot).
if you do not need this restriction you may select the explanation = _no_panic_reason_  

Choices:

_1_or_more_panic_reason_: allow CritClose base on any ‘panic’ standards: e.g. attributable to both drawdown stage, order’s depend or max lotsize opened

_for_drawdown_or_maxlot_only_: allow   CritClose might be executed when the tracked grid is underneath any both drawdown stage or max lotsize opened triggers 

_for_drawdown_only_ :  allow CritClose base on the Drawdown standards in PanicClose bot

_for_maxlot_only_: allow CritClose base on the MaxLot standards in PanicClose bot

_for_drawdown_and_maxlot_only_: allow CritClose base on each Drawdown and MaxLot standards in PanicClose bot

_no_panic_reason_ : no want Panic mode to allow CritClose

 2.3.3 Set TimeRange(s) for CriticalClose, separated by comma  The time vary by which CritClose is energetic base on dealer’s server time (displayed within the Terminal’s MarketWatch)  

String of time-range, separate by comma (,)

Format for every time vary (Begin Time and Finish Time): “hh:mm”

The time-range syntax can be {Begin Time}-{Finish Time}

For instance 04:30-10:00 means Begin Time = 4:30 and Finish Time = 10:00

Consumer can set a number of timeranges, separated by comma:

04:30-10:00,14:30-22:59

In order that CritClose will solely be energetic inside these ranges

 2.3.4 CriticalClose when BottomOrder has been opened > N minutes  Open length of BottomOrder. CritClose will solely activated when the BottomOrder’s open length has handed this quantity Integer Instance, if consumer set this to 30 → CritClose will try to shut High and BottomOrder as soon as BottomOrder has been opened greater than half-hour (supplied that TopOrder’s revenue standards meet the worth in #2.3.5 beneath)  2.3.5 TopOrder Revenue ($) for CriticalClose  Minimal revenue ($) of TopOrder at which CritClose will shut TopOrder with BottomOrder

Decimal

Will be detrimental  2.3.6  [AllGrid] Revenue ($) for CriticalClose  <Extented choice> 

when the monitoring grid attain this revenue stage CritClose will attempt to shut the entire grid as an alternative of simply TopOrder and BottomOrder    2.3.7  [AllGrid] Min order’s depend for CriticalClose  <Extented choice used with #2.3.6> 

Minimal Grid Dimension permit for CritClose to shut complete grid    2.3.8  Solely Shut all Grid?  <Prolonged choice>
shut all opened orders for the entire grid as an alternative of simply the High and Backside order  True/False

if True : instruct CritClose bot to ONLY shut complete grid, i.e. this can ignore High&BottomOrderClose (#2.3.5) and ForceClose parameters (#2.3.9 and #2.3.10)

 2.3.9  Drive-Shut At EndTime  <Prolonged choice>  execute TimeCriticalClose another time proper on the finish of the desired time-range

True/False

Utilizing the instance in #2.3.3: if True, then CritClose bot will try to shut High and Backside orders when server time is 10:00 and 22:59

 2.3.10  Drive-Shut Ignore Max Period  <Prolonged choice used with #2.3.9>  used with Drive-Shut At EndTime choice. This specified if ForceClose bot ignoring the open-duration attribute of the Backside order within the grid

True/False

If True: ignore Backside order’s open-duration when carry out ForceClose. That is for further aggressive exit technique, CritClose will skip the BottomOrder length standards

————————————

*Creator notice: use this with warning as this may occasionally trigger CritClose to shut High and Backside order with giant loss if the TopOrder revenue (#2.3.5) is just too low to compensate for the loss in BottomOrder  2.3.11  Allow Information Filter?  This toggle to allow/disable including NewsFilter for CritClose rescue mode.  True/False  2.3.12  Minutes earlier than information  Period (in minutes) BEFORE Information launch for rescue situation (specified #2.3.16 beneath)  Integer  Beneficial values to be 30, 60, 90, or greater than 120  2.3.13  Minutes after information   Period (in minutes) AFTER Information launch for rescue situation  (specified #2.3.16 beneath)  Integer
Beneficial values to be 30, or 60  2.3.14  Information Affect to filter  The Information occasion’s impression for NewsFilter. Solely information with this impression or greater would allow CritClose bot motion  Choices:

_LowImpact_

_MediumImpact_

_HighImpact_  2.3.15  Information’s forex to verify  CritClose would solely motion on the tracked grid’s image if it comprises the forex impacted by the present energetic Information occasion

Checklist of forex, separated by comma

Instance: USD,EUR,GBP

This may have an effect on:

• XAUUSD
• All EUR main and crosses
• All USD main and crosses
• All GPB main and crosses

 2.3.16  {OpenMinutes:Revenue:MinGridSize:IsAllGrid?} That is the OrderClose setting for activate CritClose bot to shut High and BottomOrder throughout Information rescue  

Syntax: {OpenMinutes:Revenue:MinGridSize:IsAllGrid?}

Instance: “5:0:2:true”

This implies:

 – `5’: as soon as the BottomOrder has been opened for greater than 5 minutes 

 – `0’: at $0.00 revenue (break even)

 – `2’ when there’s at the very least 2 orders within the grid

 – `True’: Shut complete grid solely, i.e. #2.3.8  2.3.17  minutes Earlier than Excessive information  Duration size (in minutes) Earlier than EXTREME information occasion  As per #2.3.12  2.3.18  minutes After Excessive information  Duration size (in minutes) After EXTREME information occasion  As per #2.3.13  2.3.19  Key phrases to verify, comma separated- syntax {Forex}:{phrases}  The key phrases and forex filter to find out if a Information occasion is of ‘Excessive’ class for instance if consumer put “USD:communicate,nonfarm” to NewsFilter key phrase, then for the scheduled speeches by US’s central banker and Non-farm payroll occasion, the GridRescue can use the ExtremeNews parameters to shut at a extra aggressive setting as per consumer’s outline  2.3.20  CritClose Choices round Excessive Information  That is the OrderClose setting for activate CritClose bot to shut High and BottomOrder when NewsFilter detect energetic Excessive Information occasion As per #2.3.16
This parameter permit consumer to set a separated, extra aggressive exit standards round Excessive Information occasions like Non-farm payroll or Fed speaker.  2.3.21  Present NewsFilter Panel on Chart  Toggle On/Off for show of NewsFilter Panel    True/False
———————
Notice: advocate to show this off in Technique Tester to hurry up the back-test pace should you don’t want to check the CritClose exercise round Information occasion