A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.207
1. In the case of Expiry Only Backtest having multiple ports of different indices was working very slow, it's fixed now and speed should be improved significantly.
2. ‘Clone’ Icon added in the Multileg grid. Using this option you can create the clone of any existing portfolio and can save that portfolio with different Exchange / Symbol by keeping all other settings intact.
Previously you can achieve the same by clicking Add Portfolio > Load and then select the portfolio, Now you can do the same with a single click.
3. When you were trying to Change the Exchange of any NFO portfolio to BFO Portfolio, then it was resetting the time to the default. Now it will not change.
4. A New tick box ‘Improve Backtest Performance (Use mainly on Slower PC / Laptops)’ added under settings. By Default it will be unticked.
Users having a slower / less configuration PC can use this option. Users with higher configuration may also use this (as such not required) if they have free disk space.
If Ticked, then backinzo will take about 3 to 5GB extra disk space but it will improve the overall CPU and Memory Utilization which will improve the speed at the cost of extra disk space.
Changing this setting will take 10 to 60 minutes and do not close the Backinzo in between.
Update version you can see at the left bottom of Login Screen.
1. In the case of Expiry Only Backtest having multiple ports of different indices was working very slow, it's fixed now and speed should be improved significantly.
2. ‘Clone’ Icon added in the Multileg grid. Using this option you can create the clone of any existing portfolio and can save that portfolio with different Exchange / Symbol by keeping all other settings intact.
Previously you can achieve the same by clicking Add Portfolio > Load and then select the portfolio, Now you can do the same with a single click.
3. When you were trying to Change the Exchange of any NFO portfolio to BFO Portfolio, then it was resetting the time to the default. Now it will not change.
4. A New tick box ‘Improve Backtest Performance (Use mainly on Slower PC / Laptops)’ added under settings. By Default it will be unticked.
Users having a slower / less configuration PC can use this option. Users with higher configuration may also use this (as such not required) if they have free disk space.
If Ticked, then backinzo will take about 3 to 5GB extra disk space but it will improve the overall CPU and Memory Utilization which will improve the speed at the cost of extra disk space.
Changing this setting will take 10 to 60 minutes and do not close the Backinzo in between.
Update version you can see at the left bottom of Login Screen.
👍11❤1
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.208
1. In the case of Positional Portfolio’s Having ReEntry with Wait and Trade, in some cases, legs are taking reentry randomly due to which everytime BT results were changing.
This was happening only for the positional ports and that too in certain cases, it's fixed now.
Update version you can see at the left bottom of Login Screen.
1. In the case of Positional Portfolio’s Having ReEntry with Wait and Trade, in some cases, legs are taking reentry randomly due to which everytime BT results were changing.
This was happening only for the positional ports and that too in certain cases, it's fixed now.
Update version you can see at the left bottom of Login Screen.
👍2
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.209
1. In the case of Positional Portfolio’s, As per the current rules, Portfolio can only start execution from the next day when it gets SqOff.
However, few users were trying to take the entry in the same portfolio on the same day of the expiry.
We have made the necessary changes in this regard. Now the Positional Portfolios can take Entry again on the same day of the expiry only if the portfolio gets fully completed before the Entry Time.
Update version you can see at the left bottom of Login Screen.
1. In the case of Positional Portfolio’s, As per the current rules, Portfolio can only start execution from the next day when it gets SqOff.
However, few users were trying to take the entry in the same portfolio on the same day of the expiry.
We have made the necessary changes in this regard. Now the Positional Portfolios can take Entry again on the same day of the expiry only if the portfolio gets fully completed before the Entry Time.
Update version you can see at the left bottom of Login Screen.
👍5
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.210
1. For a very few users, Backtest Name screen where users can enter the name of BT was hanging.
We have not made any changes in that screen since very long but all of a sudden this issue arose for a very few users. In this regard we made some changes and it should work fine now.
Update version you can see at the left bottom of Login Screen.
1. For a very few users, Backtest Name screen where users can enter the name of BT was hanging.
We have not made any changes in that screen since very long but all of a sudden this issue arose for a very few users. In this regard we made some changes and it should work fine now.
Update version you can see at the left bottom of Login Screen.
👍5
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.211
1. In case of per lot brokerage, backinzo was calculating brokerage in double. This is fixed now.
2. There are a few other fixes as well.
Update version you can see at the left bottom of Login Screen.
1. In case of per lot brokerage, backinzo was calculating brokerage in double. This is fixed now.
2. There are a few other fixes as well.
Update version you can see at the left bottom of Login Screen.
👍3
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.212
1. Some users were unable to Backtest the Sensex positional portfolios on Backinzo Premium, This is fixed now.
2. There are some changes in the logic about how backinzo will handle if the setting ticked for “SL at the Broker”.
Update version you can see at the left bottom of Login Screen.
1. Some users were unable to Backtest the Sensex positional portfolios on Backinzo Premium, This is fixed now.
2. There are some changes in the logic about how backinzo will handle if the setting ticked for “SL at the Broker”.
Update version you can see at the left bottom of Login Screen.
👍4
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.214
1. After the Last Update, we have received complaints that backinzo is skipping a few days of results in the case of parallel processing. This was happening in some particular cases, This is fixed now.
2. There are some changes in the logic about how backinzo will handle the setting ticked for “SL at the Broker”.
Update version you can see at the left bottom of Login Screen.
1. After the Last Update, we have received complaints that backinzo is skipping a few days of results in the case of parallel processing. This was happening in some particular cases, This is fixed now.
2. There are some changes in the logic about how backinzo will handle the setting ticked for “SL at the Broker”.
Update version you can see at the left bottom of Login Screen.
👍2
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.215
1. After the Last Update, Peak Margin wasn’t showing in the results grid. This is fixed now.
Update version you can see at the left bottom of Login Screen.
1. After the Last Update, Peak Margin wasn’t showing in the results grid. This is fixed now.
Update version you can see at the left bottom of Login Screen.
👍6
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.217
1. ‘Move SL to Cost’ Settings has been Moved from the top to the 'Stoploss Settings' Tab
2. ‘ReEntry settings’ has been moved from 'Other Settings' tab to the ‘Monitoring’ Tab
3. Under the ‘Other Settings’ Tab, users can set the delay for the Execute / ReExecute of any Leg. Similarly users can set the delays for Portfolio Execute / ReExecute too.
Previously users were able to set these delays in terms of seconds only, however we were getting requests from many users to set these delays as per the candles close like 5 Mins, 15 mins etc.
Now users can also set these delays with respect to the candle timings as well. Users can specify the timings in both ways, if they have set both the fields, then both will be clubbed together.
Suppose you want to Execute / ReExecute the Portfolio with delay of specific candle time for an example 15 mins and your ReExecute triggered at 09:19 due to a SL, now in this case, your ReExecute will only be performed at the 09:30 which is the next time for a 15 mins candle.
Now, If you have specified the time in seconds as well, then both will be clubbed together. This is useful in cases where the user may want to execute at candle close but wants to delay slightly like 1 / 2 seconds to avoid any moves which may happen due to candle close.
4. Now users can control the ‘Move SL to Cost’ functions in a much better way.
Till now, If Move SL to Cost was ticked and if SL got hit for any of the legs, then the app will move the SL to the Avg Entry Price for all the Profitable legs only. However in certain rare cases, it is possible that the other leg may not be in profit at the time SL was hitting on the first leg, due to which Move SL to Cost wasn’t performed for that leg and that leg was left open for the whole SL.
We are updating the documentation regarding this feature, you can refer to the documentation for more details after one day.
Please let us know on DM If you have adverse observations regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
1. ‘Move SL to Cost’ Settings has been Moved from the top to the 'Stoploss Settings' Tab
2. ‘ReEntry settings’ has been moved from 'Other Settings' tab to the ‘Monitoring’ Tab
3. Under the ‘Other Settings’ Tab, users can set the delay for the Execute / ReExecute of any Leg. Similarly users can set the delays for Portfolio Execute / ReExecute too.
Previously users were able to set these delays in terms of seconds only, however we were getting requests from many users to set these delays as per the candles close like 5 Mins, 15 mins etc.
Now users can also set these delays with respect to the candle timings as well. Users can specify the timings in both ways, if they have set both the fields, then both will be clubbed together.
Suppose you want to Execute / ReExecute the Portfolio with delay of specific candle time for an example 15 mins and your ReExecute triggered at 09:19 due to a SL, now in this case, your ReExecute will only be performed at the 09:30 which is the next time for a 15 mins candle.
Now, If you have specified the time in seconds as well, then both will be clubbed together. This is useful in cases where the user may want to execute at candle close but wants to delay slightly like 1 / 2 seconds to avoid any moves which may happen due to candle close.
4. Now users can control the ‘Move SL to Cost’ functions in a much better way.
Till now, If Move SL to Cost was ticked and if SL got hit for any of the legs, then the app will move the SL to the Avg Entry Price for all the Profitable legs only. However in certain rare cases, it is possible that the other leg may not be in profit at the time SL was hitting on the first leg, due to which Move SL to Cost wasn’t performed for that leg and that leg was left open for the whole SL.
We are updating the documentation regarding this feature, you can refer to the documentation for more details after one day.
Please let us know on DM If you have adverse observations regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
👍6
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.218
1. Move SL to Cost was having a mandatory requirement that it will only be performed for those legs who have SL set, Now this requirement is removed and Now Move SL to Cost can be performed for any leg even legs without SL.
2. We have added the tool-tip for the Move SL to Cost fields. For your ease, it is mentioned below as well.
Move SL Safety Seconds
This will Help you to Stop Move SL to Cost for the legs which were executed in the last mentioned safety seconds. Eg suppose safety seconds was 7 and ReEntry of a leg happened at 10:01:02 and at 10:01:05 a older leg got SL, now in this case the app will not move sl to cost for the reentry leg as it is executed within the 7 seconds.
Move SL Action
1. Move Only for Profitable Legs
Move SL to Cost will move SL to the Entry Price only for the Profitable Legs.
2. Move SL for All Legs Despite Loss / Profit
Move SL to Cost will move SL to the Entry Price for the Profitable as well as loss making Legs.
3. Move SL to LTP + Buffer for Loss Making Legs
For Profitable Legs: SL will be moved to the Entry Price
For Loss Making: SL will be moved to the LTP + Buffer
Move SL Everytime
Normally Move SL to Cost is performed only once when the first SL gets hit for any one leg. However if you want to perform Move SL to Cost every time whenever there is a SL getting hit on new legs, you can tick this.
If this is ticked, Move SL to Cost will perform everytime for the legs whose SL is not yet moved.
Update version you can see at the left bottom of Login Screen.
1. Move SL to Cost was having a mandatory requirement that it will only be performed for those legs who have SL set, Now this requirement is removed and Now Move SL to Cost can be performed for any leg even legs without SL.
2. We have added the tool-tip for the Move SL to Cost fields. For your ease, it is mentioned below as well.
Move SL Safety Seconds
This will Help you to Stop Move SL to Cost for the legs which were executed in the last mentioned safety seconds. Eg suppose safety seconds was 7 and ReEntry of a leg happened at 10:01:02 and at 10:01:05 a older leg got SL, now in this case the app will not move sl to cost for the reentry leg as it is executed within the 7 seconds.
Move SL Action
1. Move Only for Profitable Legs
Move SL to Cost will move SL to the Entry Price only for the Profitable Legs.
2. Move SL for All Legs Despite Loss / Profit
Move SL to Cost will move SL to the Entry Price for the Profitable as well as loss making Legs.
3. Move SL to LTP + Buffer for Loss Making Legs
For Profitable Legs: SL will be moved to the Entry Price
For Loss Making: SL will be moved to the LTP + Buffer
Move SL Everytime
Normally Move SL to Cost is performed only once when the first SL gets hit for any one leg. However if you want to perform Move SL to Cost every time whenever there is a SL getting hit on new legs, you can tick this.
If this is ticked, Move SL to Cost will perform everytime for the legs whose SL is not yet moved.
Update version you can see at the left bottom of Login Screen.
👍6❤2
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.219
Backinzo was having Underlying Breakout and Leg Range Breakout features, however we were getting continuous requests for the Rolling Straddle Breakouts.
In pursuance to the same, we have added another breakout which we call as “Strategy Range Breakout” This feature will only be available for the Backinzo Premium Users.
Rather only limiting to the Straddles, users can select from a bunch of predefined standard options strategies and can backtest according to their breakouts.
This feature is still under development, however we are releasing it to have feedbacks / suggestions from the users.
For the better understanding of the feature, The Documentation will be updated soon, till then you can refer to the below text.
There were requirements from the users that they want to test the portfolio when there is a certain movement in Rolling Straddle Premium with respect to the Start, Low of the day or High of the day
To achieve this and many more, we have added “Strategy Range Breakout” under “Range Breakout” Tab.
1. Strategy: You have to select any predefined options strategy here, you can select the short straddle as well.
2. Start Time: It will be the Start Time of the Portfolio.
3. End Time: (optional) This will be the end time to get the High / Low of the selected strategy. It is optional. If not specified then strategy will keep under monitoring.
4. Underlying: You can select the underlying. Spot / Future / Implied (Synthetic Futures). This will only be used to keep tracking of strategy (which was selected in step 1) range breakout only.
5. Based On: On what basis you want to check for the breakout. This can be Strategy Start Value, High or Low value.
6. Monitoring: If Rolling then strikes will be changed with the change of underlying value, if static then strikes will be selected once and remain the same.
7. Breakout Value:
This value can be entered as Point / Percentage and Negative and Positive as well. Example 10%, -5%, 25 and -15 all are valid values.
Extra care would be required in short strategies for example straddle. Here you need to enter this value very carefully.
Let’s understand with an example:
Suppose Short Straddle Start Combined premium was: -100, and for below values the expected breakout value will become:
For 10% it will be: -110
For -10% it will be -90
For 10 points it will be -90
For -10 points it will be -110
Points and percentage will work differently as percentage will always be calculated on the underlying value which was -100 in example. Users are required to enter this value very carefully!
8. Breakout Minutes:
Users can specify the time in terms of minutes here to find the breakout within the specified last minutes.
Let’s understand with an example:
Suppose, minutes were mentioned as 10 and Based On was set to Low. In this case the app will only check the Low made within the last 10 mins and check if any breakout happened?
If Specified then Breakout End Time (if any specified) would be ignored.
9. Execute Action: Select the Action which you want to execute on satisfying the breakout conditions.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
Backinzo was having Underlying Breakout and Leg Range Breakout features, however we were getting continuous requests for the Rolling Straddle Breakouts.
In pursuance to the same, we have added another breakout which we call as “Strategy Range Breakout” This feature will only be available for the Backinzo Premium Users.
Rather only limiting to the Straddles, users can select from a bunch of predefined standard options strategies and can backtest according to their breakouts.
This feature is still under development, however we are releasing it to have feedbacks / suggestions from the users.
For the better understanding of the feature, The Documentation will be updated soon, till then you can refer to the below text.
There were requirements from the users that they want to test the portfolio when there is a certain movement in Rolling Straddle Premium with respect to the Start, Low of the day or High of the day
To achieve this and many more, we have added “Strategy Range Breakout” under “Range Breakout” Tab.
1. Strategy: You have to select any predefined options strategy here, you can select the short straddle as well.
2. Start Time: It will be the Start Time of the Portfolio.
3. End Time: (optional) This will be the end time to get the High / Low of the selected strategy. It is optional. If not specified then strategy will keep under monitoring.
4. Underlying: You can select the underlying. Spot / Future / Implied (Synthetic Futures). This will only be used to keep tracking of strategy (which was selected in step 1) range breakout only.
5. Based On: On what basis you want to check for the breakout. This can be Strategy Start Value, High or Low value.
6. Monitoring: If Rolling then strikes will be changed with the change of underlying value, if static then strikes will be selected once and remain the same.
7. Breakout Value:
This value can be entered as Point / Percentage and Negative and Positive as well. Example 10%, -5%, 25 and -15 all are valid values.
Extra care would be required in short strategies for example straddle. Here you need to enter this value very carefully.
Let’s understand with an example:
Suppose Short Straddle Start Combined premium was: -100, and for below values the expected breakout value will become:
For 10% it will be: -110
For -10% it will be -90
For 10 points it will be -90
For -10 points it will be -110
Points and percentage will work differently as percentage will always be calculated on the underlying value which was -100 in example. Users are required to enter this value very carefully!
8. Breakout Minutes:
Users can specify the time in terms of minutes here to find the breakout within the specified last minutes.
Let’s understand with an example:
Suppose, minutes were mentioned as 10 and Based On was set to Low. In this case the app will only check the Low made within the last 10 mins and check if any breakout happened?
If Specified then Breakout End Time (if any specified) would be ignored.
9. Execute Action: Select the Action which you want to execute on satisfying the breakout conditions.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
❤11👍9
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.220
1. In continuation to the last update, we have added one more field under the Based On ‘Average’. This will work based on the Average of the prices. This is not a VWAP but a simple average of the prices.
2. There are many users who are getting confused with the negative values. Let’s understand with an example.
Suppose you have selected the Short Straddle, Based On: Low
Now for the provided range Straddle premium was -173 and -96, here it is important to note that Low is -193 and High is -96 because of negative values.
When you specify the low with 20% breakout which comes to -207.6, use the high and low very carefully as per your requirements.
3. If End time was specified then Breakout condition wasn’t waiting till end time, it's fixed now.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
1. In continuation to the last update, we have added one more field under the Based On ‘Average’. This will work based on the Average of the prices. This is not a VWAP but a simple average of the prices.
2. There are many users who are getting confused with the negative values. Let’s understand with an example.
Suppose you have selected the Short Straddle, Based On: Low
Now for the provided range Straddle premium was -173 and -96, here it is important to note that Low is -193 and High is -96 because of negative values.
When you specify the low with 20% breakout which comes to -207.6, use the high and low very carefully as per your requirements.
3. If End time was specified then Breakout condition wasn’t waiting till end time, it's fixed now.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
👍5👏2❤1
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.222
1. ‘Strategy Range Breakout’ was not working as expected in case of BFO, it's fixed now.
Update version you can see at the left bottom of Login Screen.
1. ‘Strategy Range Breakout’ was not working as expected in case of BFO, it's fixed now.
Update version you can see at the left bottom of Login Screen.
👍6
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.224
1. We were getting requirements from the users to change the Strike in case of SL / Tgt hits on a particular leg. This is normally called as Risk On (trading higher premium) / Risk Off (Trading Lower Premiums)
Under the V2 Portfolio, When you set the ReExecute action on SL / Tgt for any leg, then you can also set the Risk ON / Off parameter.
RiskOn / Off:
In Case ReExecution of the leg due to SL / Tgt, if you want to move the Strike UP / Down then you can utilize this field. This can be specified in terms of Positive and Negative Numbers. 0 means this field is Off.
Risk Off: Move Step Up (Towards the OTM). Should be specified with the Positive Number. Suppose this is mentioned as 2 which means move 2 strike UP (towards OTM). So if the original strike was 50200CE then in case of ReExecution, it will become 50400 and for 50200PE it will become 50000.
Risk ON: Move Step Down (Towards the ITM). Should be specified with the Negative Number. Suppose this is mentioned as -1 which means move 1 strike Down (towards ITM). So if the original strike was 50200CE then in case of ReExecution, it will become 50100 and for 50200PE it will become 50300.
This will only be available with V2 Ports
2. Under the Backtest settings window we have made some changes for the selection of “DTE W.r.t Monthly Expiry Only for BNF, FIN and MID”.
3. We have removed the option to test Expiry Only Backtests, this can be achieved by selecting 0 DTE only.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
1. We were getting requirements from the users to change the Strike in case of SL / Tgt hits on a particular leg. This is normally called as Risk On (trading higher premium) / Risk Off (Trading Lower Premiums)
Under the V2 Portfolio, When you set the ReExecute action on SL / Tgt for any leg, then you can also set the Risk ON / Off parameter.
RiskOn / Off:
In Case ReExecution of the leg due to SL / Tgt, if you want to move the Strike UP / Down then you can utilize this field. This can be specified in terms of Positive and Negative Numbers. 0 means this field is Off.
Risk Off: Move Step Up (Towards the OTM). Should be specified with the Positive Number. Suppose this is mentioned as 2 which means move 2 strike UP (towards OTM). So if the original strike was 50200CE then in case of ReExecution, it will become 50400 and for 50200PE it will become 50000.
Risk ON: Move Step Down (Towards the ITM). Should be specified with the Negative Number. Suppose this is mentioned as -1 which means move 1 strike Down (towards ITM). So if the original strike was 50200CE then in case of ReExecution, it will become 50100 and for 50200PE it will become 50300.
This will only be available with V2 Ports
2. Under the Backtest settings window we have made some changes for the selection of “DTE W.r.t Monthly Expiry Only for BNF, FIN and MID”.
3. We have removed the option to test Expiry Only Backtests, this can be achieved by selecting 0 DTE only.
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
👍14👏2❤1🙏1
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.225
1. For Backinzo Premium Users, Bankex will also be the part of “DTE W.r.t Monthly Expiry Only for BNF, FIN and MID” for the Monthly Expiry Tick Box under Backtest settings window.
2. RiskOn / Risk Off wasn't working properly for the Premium / Greek Based legs, this is fixed now.
3. We were getting requirements from the users to monitor for the Premiums of CE and PE legs and when the difference between both of them increased by some percentage, then take the action.
To achieve this, we have added “Premium Comparison Monitoring” under the “Other Settings” Tab.
Premium Comparison Monitoring
If Enabled, It will compare the Premium of first active CE and PE legs as per the settings. If more than one CE / PE legs, then it will compare the premiums of first active PE vs CE leg. it will compare a lower premium with a higher premium. For example: if the CE is 50 and PE is 60. it's 20% higher than the lower strike.
Difference Percentage:
Here you have to enter the value in percentage which will be checked between the active CE / PE premiums. If the premiums between the Active CE / PE legs become more than the mentioned percentage, then selected action will be taken by the app.
Suppose CE was 100 and PE was 120, in this case percentage will be calculated w.r.t lower values with the difference which will come to 20%.
If you have specified the Min Hold for Seconds, then Before taking any action, the app will take action if the difference stays for more than mentioned time.
Min Points:
In some cases of lower premium, difference percentage may become a negligible value. In that case this field can be useful.
If this is mentioned, then the App will consider the higher value between ‘Difference Percentage’ and ‘Min Points’.
Suppose Lower premium was 5 and difference percentage was mentioned as 10% which will come to 0.5. Now suppose Min Point was mentioned as 2 then the app will consider 2 as a difference.
Min Hold for Seconds:
If you want to wait for sometime to avoid any sharp movements, you can specify the wait time in seconds here.
App will take the action only if the mentioned difference is sustained for more than the specified seconds.
Which Leg to SqOff:
Here you can set which leg you wanted to SqOff if the different conditions met.
Which Action to take on SqOff:
If you have specified any On SL / On Target action for the leg, then from here you can specify which action you wanted to take for that leg.
This will treat SqOff of the leg as per the action selected. Suppose you want to take OnSL action in case of SqOff due to Premium Difference, then the App will treat that leg was SqOff as OnSL and its action will be taken accordingly.
In Simple words, it will specify that the leg will be SqOff as OnSL or OnTarget.
IT IS IMPORTANT TO NOTE THAT IF THE ACTION HAS REECEUTION (OF ANY TYPE) OF THE LEG, THEN BEFORE TAKING ANY ACTION APP WILL FIRST CHECK THE CONDITION AND DETERMINE IF THE NEW LEG WILL HAVE DIFFERENT STRIKE OR NOT.
IF THE NEW LEG IS ALSO GOING TO HAVE THE SAME STRIKE, THEN IT WILL NOT TAKE ANY ACTION TOWARDS PREMIUM DIFFERENCE AND IT WILL DELAYED THE CONDITION CHECKING OF PREMIUM DIFFERENCE.
NEW LEG WILL ONLY EXECUTE WHEN IT DIFFERS FROM THE PREVIOUS STRIKE
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
1. For Backinzo Premium Users, Bankex will also be the part of “DTE W.r.t Monthly Expiry Only for BNF, FIN and MID” for the Monthly Expiry Tick Box under Backtest settings window.
2. RiskOn / Risk Off wasn't working properly for the Premium / Greek Based legs, this is fixed now.
3. We were getting requirements from the users to monitor for the Premiums of CE and PE legs and when the difference between both of them increased by some percentage, then take the action.
To achieve this, we have added “Premium Comparison Monitoring” under the “Other Settings” Tab.
Premium Comparison Monitoring
If Enabled, It will compare the Premium of first active CE and PE legs as per the settings. If more than one CE / PE legs, then it will compare the premiums of first active PE vs CE leg. it will compare a lower premium with a higher premium. For example: if the CE is 50 and PE is 60. it's 20% higher than the lower strike.
Difference Percentage:
Here you have to enter the value in percentage which will be checked between the active CE / PE premiums. If the premiums between the Active CE / PE legs become more than the mentioned percentage, then selected action will be taken by the app.
Suppose CE was 100 and PE was 120, in this case percentage will be calculated w.r.t lower values with the difference which will come to 20%.
If you have specified the Min Hold for Seconds, then Before taking any action, the app will take action if the difference stays for more than mentioned time.
Min Points:
In some cases of lower premium, difference percentage may become a negligible value. In that case this field can be useful.
If this is mentioned, then the App will consider the higher value between ‘Difference Percentage’ and ‘Min Points’.
Suppose Lower premium was 5 and difference percentage was mentioned as 10% which will come to 0.5. Now suppose Min Point was mentioned as 2 then the app will consider 2 as a difference.
Min Hold for Seconds:
If you want to wait for sometime to avoid any sharp movements, you can specify the wait time in seconds here.
App will take the action only if the mentioned difference is sustained for more than the specified seconds.
Which Leg to SqOff:
Here you can set which leg you wanted to SqOff if the different conditions met.
Which Action to take on SqOff:
If you have specified any On SL / On Target action for the leg, then from here you can specify which action you wanted to take for that leg.
This will treat SqOff of the leg as per the action selected. Suppose you want to take OnSL action in case of SqOff due to Premium Difference, then the App will treat that leg was SqOff as OnSL and its action will be taken accordingly.
In Simple words, it will specify that the leg will be SqOff as OnSL or OnTarget.
IT IS IMPORTANT TO NOTE THAT IF THE ACTION HAS REECEUTION (OF ANY TYPE) OF THE LEG, THEN BEFORE TAKING ANY ACTION APP WILL FIRST CHECK THE CONDITION AND DETERMINE IF THE NEW LEG WILL HAVE DIFFERENT STRIKE OR NOT.
IF THE NEW LEG IS ALSO GOING TO HAVE THE SAME STRIKE, THEN IT WILL NOT TAKE ANY ACTION TOWARDS PREMIUM DIFFERENCE AND IT WILL DELAYED THE CONDITION CHECKING OF PREMIUM DIFFERENCE.
NEW LEG WILL ONLY EXECUTE WHEN IT DIFFERS FROM THE PREVIOUS STRIKE
Please let us know on DM If you have any observations / suggestions regarding these newly launched features.
Update version you can see at the left bottom of Login Screen.
👍8👏4
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.227
1. There are some changes specific to some certain rare cases.
Update version you can see at the left bottom of Login Screen.
1. There are some changes specific to some certain rare cases.
Update version you can see at the left bottom of Login Screen.
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.228
1. Please use the Cache Manager after the Update.
Update version you can see at the left bottom of Login Screen.
1. Please use the Cache Manager after the Update.
Update version you can see at the left bottom of Login Screen.
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.229
1. In some cases, the DTE selection on the Backtest screen (where you enter the name for backtest) wasn’t working as expected, this is fixed now.
Update version you can see at the left bottom of Login Screen.
1. In some cases, the DTE selection on the Backtest screen (where you enter the name for backtest) wasn’t working as expected, this is fixed now.
Update version you can see at the left bottom of Login Screen.
👍3
A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.240
1. Reliance Strike Step was coming as 80 which has to be 10, this is fixed now.
Update version you can see at the left bottom of Login Screen.
1. Reliance Strike Step was coming as 80 which has to be 10, this is fixed now.
Update version you can see at the left bottom of Login Screen.