When B# will not work!
Although B# can generate high quality BUY and SELL signals, it is not a perfect tool. These are the following instances when B# will fail to work as intended because B# cannot pick up a change in trend immediately:-
It is highly unlikely that these events will not be accurately discounted in stock pricing. If a stock price pattern changes, as a result of these types of events, B# is likely to track and identify this, but it may take a few days to catch-up.
If there has been a highly volatile price move within the Source dataset, this will have an impact on the optimization process for setting the two B# parameters (Step and Max PSAR values). As this price volatility shifts out of scope (as time progresses), this swing in price will result in a reset of the B# parameters. You should be aware that this could occur so either wait until the event has moved out of scope or be prepared for a change in B# BUY/SELL indicator sequencing as the back-end days are removed from consideration.
It is therefore highly advisable to use B# to track a stock for as long as you can before you decide to take any positions. Each stock will have its unique Optimized PSAR profile and this will change over time – it is best to be patient and learn how B# is trading your stock of interest before you commit capital.
Leveraging B# for Dollar Cost Average investing
Many investors save regularly, usually monthly, on a dollar cost averaged basis. This is an excellent investing approach as it does mitigate the volatility in stock prices. Instead of maintaining a constant time schedule, a possible improvement is to consider stock purchases when B# suggests these. It may require more attention on your part but could result in a healthier returns over time.
Troubleshooting
Although every care has been taken in developing our software, you may experience the following problems when using B# depending on your system configuration. Here are a few suggestions of how you may solve these.
Although running on your phone, B# will be executing very extensive calculations so the performance of your phone’s CPUs are crucial in speedy completion of all calculations. A new phone will be expected to complete the calculations in 3-5 seconds. Older phones could take several minutes to complete the same calculations. There is no workaround to long waiting times other than running B# on newer phones.
Do not try to start a simulation run before a previous run is still on-going. Two separate processes will be initiated and this will result in issues with completing either run.
Copyright © 2023 PenPointSoftware - All Rights Reserved.
Powered by GoDaddy