Fritz Jooste Administrator Posts: 6 6/21/2017

Fritz Jooste Administrator Posts: 6 During June 2017, some improvements were made to the automated backcalculation algorithm. These changes mean that you may find that the backcalculation algorithm now yields slightly different results compared to earlier backcalculation runs. The differences may not occur on all bowls, and the magnitude is likely to be quite small. The following improvements were made (applied only to the Online Tools version of the backcalculation tool): In the initial implementation, we stored imported deflections as integers (whole numbers). However, we found that even decimal deflection values could influence results. So we modified the storage procedure to include decimals in measured deflections. We found that the specified backcalculation error was not being properly applied in the backcalculation algorithm. Essentially, it was allowing the search process to terminate at 10% errors. This has now been fixed. The fact that some of your earlier stored analysis (that may be in a report by now) will now yield different results if you run it again is of course not ideal. But we have to keep on making improvements where we can, and in the interest of constant improvement, we decided to implement these improvements as soon as possible in the online tools. If for some reason you really need to reproduce the exact result set that you reported earlier, you can try the following: 1. Re-import your deflection data from your original Excel Template 2. Re-Run the backcalculation using the exact same layer properties and search ranges, BUT with a specified allowable error of 10%. Please feel free to get in touch with the engineering support team if you have any questions about this issue. edited by Fritz Jooste on 1/30/2020

0 link

---