New Members: Be sure to confirm your email address by clicking on the link that was sent to your email inbox. You will not be able to post messages until you click that link.
Chip asked us to send in issues between the Classic Workbench and the New for things that we use that are not on the New Workbench or things that we'd suggest to improve it.
So don't be surprised if you get an influx of these requests.
On the Classic there is a dropdown for ChartStyles and at the bottom of that dropdown listing are additional chartstyles listed under Predefined. The Predefined chartstyles are not listed in the New workbench dropdown. I use this feature on the Classic to get quick access to the "expert" chartstyles you have available.
Please Add the additional Predefined chartstyles to the CHARTSTYLES dropdown listing at the top of the workbench.
Got a response. One only has to CLICK on Chartstyle Library then CLICK on the Select Library dropdown, then CLICK to select a category of Libraries, then CLICK to select the chartstyle of interest (a preview appears) and then CLICK to Apply Chartstyle to get it into the Workbench.
Then CLICK on the Chart Settings link to see the workbench again.
YES, that is the response.
So, a one click dropdown and click to select is now 6 clicks and you have to know the route.
Well sir, I will not be much help for charts, as have no real use ever here for them at all.
What I tried to get = no result was database structure & order = which knowing field & column order that is 'stored' ='s proper order to apply in scans = reduced time
Again, SIMPLE request
ps...scan function appendix layout = [like they taught ya in grammar school when ya readin a book at end for fast lookup] = seek, and ye shall find = way to easily !!
I don't think you need to know the database structure to write efficient scans. Also, the answer may not be as simple as you think it is. Database technology has changed a lot.
First, these days, with the processor speed and memory capacity available today, even a poorly written scan will run in a blink of an eye from the user's point of view.
Second, after the interpreter gets done translating your scan into machine language, it won't look like your scan anyway.
Third, the speed of processing doesn't depend on the location of data on the individual record. It depends on how many records have to be looked at. So, if you want to write an efficient scan, you would order your logic by the fewest records fitting the criteria first.
So, let's say you want MACD Line crossing above MACD signal where price is above the SMA 200 and volume is three time the 20 day average and the stock is in the Industrial sector.
You would not put MACD Line x MACD signal first, because lots of stocks not in the Industrial sector would also do that so they don't need to be looked at all. Likewise the other conditions. So you want to move from the least general to the most general i.e. least hits likely to most hits likely, so the scan looks at the fewest records (not the fewest fields in the record).
So the first line of the scan is
[group is IndustrialSector]
Then you would decide which is the next least likely. Probably 3x average volume (but not necessarily, so it's a toss up). So the next line would be
and [volume > sma(20, volume) * 3)]
next least likely
and [close > sma(200,close)]
and now finally
and [MACD Line(12,26,9) x MACD Signal(12,26,9)]
But again, probably no matter the order, on your side you wouldn't notice the difference in processing time. And even if it did matter, it would likely be cancelled out by events on the web between your machine and the SC server.
Comments
Chip asked us to send in issues between the Classic Workbench and the New for things that we use that are not on the New Workbench or things that we'd suggest to improve it.
So don't be surprised if you get an influx of these requests.
On the Classic there is a dropdown for ChartStyles and at the bottom of that dropdown listing are additional chartstyles listed under Predefined. The Predefined chartstyles are not listed in the New workbench dropdown. I use this feature on the Classic to get quick access to the "expert" chartstyles you have available.
Please Add the additional Predefined chartstyles to the CHARTSTYLES dropdown listing at the top of the workbench.
Then CLICK on the Chart Settings link to see the workbench again.
YES, that is the response.
So, a one click dropdown and click to select is now 6 clicks and you have to know the route.
What I tried to get = no result was database structure & order = which knowing field & column order that is 'stored' ='s proper order to apply in scans = reduced time
Again, SIMPLE request
ps...scan function appendix layout = [like they taught ya in grammar school when ya readin a book at end for fast lookup] = seek, and ye shall find = way to easily !!
DUH
https://ta-lib.org/functions/
and another fwiw here is the "stable"
https://www.highcharts.com/demo
result set of those two?
Here's the church and there's the steeple.
Open the door and see all the people.
https://nurseryrhymescollections.com/lyrics/heres-the-church.html
First, these days, with the processor speed and memory capacity available today, even a poorly written scan will run in a blink of an eye from the user's point of view.
Second, after the interpreter gets done translating your scan into machine language, it won't look like your scan anyway.
Third, the speed of processing doesn't depend on the location of data on the individual record. It depends on how many records have to be looked at. So, if you want to write an efficient scan, you would order your logic by the fewest records fitting the criteria first.
So, let's say you want MACD Line crossing above MACD signal where price is above the SMA 200 and volume is three time the 20 day average and the stock is in the Industrial sector.
You would not put MACD Line x MACD signal first, because lots of stocks not in the Industrial sector would also do that so they don't need to be looked at all. Likewise the other conditions. So you want to move from the least general to the most general i.e. least hits likely to most hits likely, so the scan looks at the fewest records (not the fewest fields in the record).
So the first line of the scan is
[group is IndustrialSector]
Then you would decide which is the next least likely. Probably 3x average volume (but not necessarily, so it's a toss up). So the next line would be
and [volume > sma(20, volume) * 3)]
next least likely
and [close > sma(200,close)]
and now finally
and [MACD Line(12,26,9) x MACD Signal(12,26,9)]
But again, probably no matter the order, on your side you wouldn't notice the difference in processing time. And even if it did matter, it would likely be cancelled out by events on the web between your machine and the SC server.