Support Board

Date/Time: Thu, 25 Apr 2024 10:13:43 +0000

Post From: Keeping spreadsheets light

[2013-09-26 11:46:12] Link To Thread - Link To Post [Go To First Post]
TheOddsAreYouDontKnowTheOdds - Posts: 29
Thanks to everyone who replied. This is what I have learned from others and by trial-and-error. 1. Use as few rows as possible. Don't worry if your signal relies on long/slow moving averages or far-back data. There's a solution for that (see #3 and * below). Remember to delete the data from rows you don't want. 2. Make the logic simple. Complexity introduces execution risk. 3. Let the chart do the work, not the spreadsheet.* 4. Reserve spreadsheet power for position-dependent logic and risk-management (e.g. once I have x contracts at an average price of y, shift my exit criteria/price by z). There's other stuff but this will address many of the common causes of computational speed problems. * If you are using spreadsheets with more than a handful "if-then" statements, consider using studies like "Color Bar on Alert" etc. That way you can generate signals based on multiple criteria from the main price graph AND adjacent studies. You write the alert to say that if X, Y and Z conditions occur in such and such studies and price graphs, then DO SOMETHING. In this case, color the relevant bar in say, Yellow. This paints the bar Yellow, but more importantly, also outputs a signal to the spreadsheet. You have the result but the logic is OFF the spreadsheet. SC Engineering, please correct if anything sounds wrong. Cheers.