|
SNew Color Options, New Frame Options, QnA Templates, DYO #1312, Multiple Use of GV Numbers, #1309, #1308, #1303, AskBidRatio Template |
Oct 4 , 2006
16:31 Ensign Howard: Welcome to today's training class on Oct 4th, 2006.... This is Howard, the owner of Ensign Software and I will be the trainer today. I would like to cover several topics, but the bulk of the discussion today will be training on using DYOs which is our Design Your Own feature in Ensign Windows.
16:32 Ensign Howard: This past week we published the Sept 2006 issue of the Trading Tips newsletter, in its 7th year of continuous publication. I want to publicly thank Ana Maria Gallo for her excellent article on the nature of Equi-Volume Bars. This is the newsletter for last month which you can read on the Newsletter page of our web site if you have not read it yet.
http://www.ensignsoftware.com/tips/tradingtips81.htm
16:34 Ensign Howard: Since the addition of Equi-volume characteristics to our charting, and the 3-D shading to candlebodies, and the Ask/Bid volume capabilities, we have received a lot of positive feedback from our users, and an outpouring of gratitude for the enhancements.
16:35 Ensign Howard: During most of the month of September we were in a Beta test phase of all the new features, and have been off of Beta status for a week now. Minor changes continue to be made to the program, as is typical, and there is an Oct 4th version which you can download after the class. The only change of any real significance is code added for the refresh for eSignal users, which does additional testing of the timestamps in the tick refresh. There is a bum timestamp in the tick refresh dated 07-09-2005 in the middle of the morning on 09-29-2006 in the Esignal database. I do not know if this bum tick is universal to all server farms, but it is common enough to have been reported by a few users and reproduced by myself. The current version of Ensign will test for this out of sequence time stamp and discard it rather than putting it in the chart file. The problem it causes is to purge valid bars between 07-09-2005 and 09-26-2006 when refreshing any of the charts that are based on ticks. So, I consider it important for Esignal users to get the current Ensign Windows upgrade so you do not get tripped up by this bad time stamp.
16:39 Ensign Howard: Any questions or feedback about the tick refresh for
Esignal users?
16:40 Ensign Howard: ok, we will move on to next topic.
http://www.elitetrader.com/so/?action=view&SR_ProductID=56
16:40 Ensign Howard: Some of the positive feedback about Ensign gets posted to the elitetrader web site. You are welcome to read through the comments users are making about Ensign, and we appreciate the positive feedback and thank those who have posted to elitetrader. Your word of mouth is our advertising and that help keep our overhead low and the price we charge for the software at a low price. Thanks for the help you all are in bringing customers to us and helping to retain them through the chat room support you provide each other.
New Color Options
16:43 Ensign Howard: Last week there was a wish expressed for the Standard Color Dialog to have the custom colors be remembered and restored when Ensign reruns. At the time, I stated I did not know how to tell the Dialog how to restore the colors.... .but thanks to another Google search, I was able to find the answer I needed.
http://www.ensignsoftware.com/help/features.htm#color
16:44 Ensign Howard: The current version has this improvement to restore the custom colors you set on the Standard Dialog form. I had worked on this issue twice before and did not find the answer, but this time around, I did find what I needed on the Internet on how to control the standard dialog
16:45 Ensign Howard: On the Setup | Computer form is where you select which style of Color dialog you prefer to use. Choices are Standard and Hexagon. Personally I prefer to use Hexagon.
16:47 Ensign Howard: This is the Hexagon color dialog, and I wanted to point out the presence of the vertical slider bar on the right side pointed to by the arrow. This slider can be moved vertically to add blackness to the hexagon wheel of colors. And by using it you can get practically any of the custom colors you might have used the Standard dialog to get. Let me demonstrate dragging the slider downward. In the image posted above the slider it at the top so call the colors are bright.
16:51 Ensign Howard: In this image, the slider is down from the top, colors are darker, and I will select the cell pointed at to get this shade of teal for my chart background.
16:51 Ensign Howard: This is the custom color selected using the Hexagon dialog for the chart background color. I am just illustrating that the Hexagonal has a lot more color selection than is first realized by using the slider to add blackness to the choices you see. Both color dialogs have lots of capability in getting the colors you prefer for your bars, candles, lines, and backgrounds.
16:53 Ensign Howard: Any questions about color dialogs?
New Frame Options for Candles
16:54 Ensign Howard: On, moving on to a new topic, another one of the requests last week was to remove the black frame from around our Flutes candle style and have the frame use the candle fill color. This was implemented in the current version, and expanded to be a feature for all of the Ensign candle styles. The last chart showed our Rockets formation and had the black frame colors. Let me change to Flutes for the next chart, and have the black frame removed.
16:57 Ensign Howard: In this example, we have the No Frame option checked, which removes the black border around the candle stick. I will now uncheck the No Frame to return the display to the typical style and repost the chart so you can compare the visual change.
16:59 Ensign Howard: The same No Frame option is also available for the Ask/Bid display in the 2nd panel and the Volume display in the 3rd panel. Let me post `1 more image with these options changed.
17:00 Ensign Howard: This gives you lots of flexibility in the visual display
of the Candle Styles.
17:01 Ensign Howard: Any questions about the No Frame option enhancement?
http://www.ensignsoftware.com/help/features.htm#frame
Q&A DYO Templates
17:02 Ensign Howard: Ok, on to next topic of DYOs. We have worked to offer a collection of Templates, many of which contain DYOs so that users can just get the template and not have to set up the DYO to do the special implementing in the DYO.
17:04 Ensign Howard: On the HELP page of our web site, in the center column for the Design Your Own section, we have a new link for Library of Examples. This will take you to the same cross reference page, but I figured it was not previously obvious this was an important page full of examples.
http://www.ensignsoftware.com/help/dyo-cross.htm
17:05 Ensign Howard: This web page is a directory to 90 examples (currently) and should be a great resource to those using DYOs or trying to learn about them. The top table is the directory of examples. Further down is a cross reference of statements you might want to learn about, and links to examples that use this statement so you can see the statement in the context of a working DYO. So if you have a question about the Do Next IF category, you can scroll to the bottom and see that category, and some of the statements and links to examples. I use this directory often myself and encourage you to do so too.
17:08 Ensign Howard: Many of the example links take you to DYO examples published on other pages on the web site, such as to examples in Newsletters. Many of the links reference the Q&A Knowledgebase articles, are answers written by me in reply to e-mail requests or questions. Because of changes to the DYO statement organization in the versions in early September, I have been grooming and creating the examples to post more current examples.
17:10 Ensign Howard: One of the primary changes between pre-Sept versions and the current version is the category Global Value was split into two categories names Expression and Function. This split was done because the category was getting to be too huge with over 220 selections.
17:11 Ensign Howard: The Expression group has statements that deal with math relationships between Value, Next and #, such as Value + #. The Function group will have all the statements that return a value from a function such as Abs(Value + #) for the Absolute value.
17:12 Ensign Howard: Old DYOs auto covert to the new structure, so do not hesitate to upgrade. It is the examples that I am grooming and reposting to show the use of Expression and Function instead of Global Value. I have been asked the question several times over the past month by a person on the current version trying to type in the example that shows Global Value and they can no longer find a Global Value selection. While I am revisiting all the examples, I am now saving the example as a template and posting that for download. Lets take a recent post to the Q&A Knowledgebase as an example.
http://www.ensignsupport.com/email/1312.mhtml
17:15 Ensign Howard: This is article number 1312 in the knowledgebase. You can read the request, and my reply. I show an example of the DYO on the chart, and the DYO content and have some discussion. Most important is the entry just above my signature, which says Template: 1312-SwingSize
17:17 Ensign Howard: This "Template:" entry tells you there is a template for this example so you do not have to manually entry the DYO selections. You can click menu File | Open | Internet Services, select the Download tab, wait for the form to populate with dates and then use the Q&A Templates drop down list to select the 1312-SwingSize template.
17:19 Ensign Howard: After selecting the template, click the Download button and the file will be on your computer in the currently selected Template folder.
17:21 Ensign Howard: Now we have two selection boxes for Templates. The one labeled Template is populated with 47 templates provided by me or by customers with names like OpeningPrice. These templates do not have the 4 digit dash prefix that is consistently used for the template names on the Q&A Template list.
17:21 Ensign Howard: The prefix in the Q&A Template name is the article number, which in our example is 1312. This is a quick cross reference back to the Knowledgebase article that might be useful in understanding the purpose of the template. So if you are interested in the 1300-BigBlocks template, go read the Knowledgebase article. The 1300 would be the name of the page in the database as in this example.
http://www.ensignsupport.com/email/1300.mhtml
17:23 Ensign Howard: The URL root will be the same, and the suffix of mhtml will be the same. You can also navigate to the Knowledgebase and search it using the menu Help | Q&A Knowledgebase.
http://www.ensignsupport.com/cgi-bin/ensign/bb.cgi
17:25 Ensign Howard: Click on the link I just posted that does not auto show in the room. Now that I have covered how to harvest templates for the examples, lets move on to a discussion of specific DYO examples.
DYO #1312
www.ensignsupport.com/email/1312.mhtml
17:26 Ensign Howard: Lets start with this example of #1312. User wanted two conditions to be met, 1) Exceed a minimum swing size in the Pesavento swings and the slope of the Regression channel be above a certain threshold.
17:27 Ensign Howard: Line A and B get the swing point values of the current Pesavento Patterns swing.
17:28 Ensign Howard: Line C subtracts these 2 values and also does the absolute on the result. I use the absolute so it makes no difference whether the swing is going up or down. I am interested in the size of the swing in either direction. On Line C, note the structure of the statement is Value + # so the Value will be the content of the GV in the Read reference which is GV [1]
17:34 Ensign Howard: This GV was written by Line A, so it has a current swing price. The + # is going to Add the Number field, which happens to be a reference to a GV instead of a pure number. The reference is because the 2 is in square brackets..... go this is GV[2] and not number 2. This GV[2] was written by line B, so it has the price of the prior swing point from the Pesavento Patterns swing study. We need to subtract prior price from the current price
17:36 Ensign Howard: Line C does this... though the notation is +# note the use of a minus sign in the Number field ahead of the [2]. The statement is adding a negative value, which is thereby a subtraction. Is anyone confused by the structure of Line C, and how we accomplished the subtraction of two prices? After Line C makes its calculation, it takes the absolute value of the result, and writes the result in the Write GV reference which is [3]
17:40 Ensign Howard: Line D is the Size test by doing a global flag which compares Value to #. Value is the [3] content written by Line C. The # is the content of the Number field which in the example is a pure number of 4.0 So if the swing size is greater than 4 points, the flag will be True, otherwise it will be False. This flag is written to GV [3] since we have no further need for the prior content in [3]. Note this line also has a Show marker of a square box. When the Flag is true, it will ALSO draw the marker
17:43 Ensign Howard: So on the top of the chart you will see some sequences of the pink square box. This is showing you the bars or zones where the Pesavento swing size is exceeding the 4 size test. I find it a useful thing to show markers like this, even if it is just temporary during development and design, so I can verify I am getting the expected result... and so far, all looks good.
17:45 Ensign Howard: Line E will get the study slope and put it in a GV to work with, and it is written to GV [1] since we no longer need the price from Line A
17:45 Ensign Howard: Line F does the absolute function thing so the test is independent of direction up or down for the slope.
17:46 Ensign Howard: Line G is the slope test against a threshold, which is 0.3 in our example. And again, I used a marker for a red dot to show me where this slope condition was True.
17:47 Ensign Howard: Note that the prior flag test for the swing size was saved in [3]. For this flag, I want it saved in the next sequential GV which is [4]. By having the two flags adjacent to each other in our array of global variables, I can then do Line H which is the AND operation between Boolean flags. The notation is AND[#] and the [#] always implies a set. The size of the set is in the number field, which is a 2
17:49 Ensign Howard: So this statement will AND together the flag in the Read GV which is [3] and the next flag in [4] to get a final result. When both flags are true, then the AND statement will also be True, and then the show marker of a light green zone will be put on the chart. The light green zone is in perfect correlation with the 2 markers of the square box and the red dot.
17:50 Ensign Howard: When both are present on the same bar, the zone is also colored green. When either marker is missing, the zone is uncolored and the chart background shows through.
17:51 Ensign Howard: Any questions about this fairly basic DYO that makes two tests and shows when both conditions are present?
17:52 Ensign Howard: Sorry if this is a bit elementary for some of you who are experts with DYOs already, but I am trying to have a class that is beneficial for everyone at all levels of experience.
Multiple Use of GV Numbers
17:53 scooter4: I have a stupid question, in DYO's can you only have for ex GV 1-6 on 1 DYO on your chart and if you put a second different DYO on the same chart can you use GV 1-6 again or do you have to start with 7-12 like I have been doing?
17:53 Ensign Howard: scooter, good question..... you can reuse the 1-6 GVs. The principle is this..... as long as you do not need a GV to retain its value between calculations you are save to reuse the GVs.
17:49 Ensign Howard: In the last example, we WROTE the GV content by one line before we ever READ it by a later line. Thus this DYO example is totally safe to use with other DYOs that might use the same GV numbers.
17:50 Ensign Howard: In fact, in my own DYO I reused a couple of the GVs once I was done with their use. Now if you need to remember a GV content because it might be a counter, then you probably need to have this GV be one that is owned by the chart, which is all GVs in the range of 240 through 255. That way the same DYO applied to different charts will keep their values separated.
17:52 Ensign Howard: GVs 0..239 are global to the whole program. GVs 240..255 are private to each chart, meaning each chart has this small set of GVs as a private array for holding personal information that the chart needs to protect.
17:53 scooter4: Now you confused me, if I use the same dyo on 2 charts on the same page then I have to change the GV?
17:53 Ensign Howard: Sorry for the confusion. You can use the same DYO on 2 charts.
17:53 Ensign Howard: If you write the GV before you read it you can use GVs 0..239
17:54 Ensign Howard: If you ever need to read a previously written value, then you better use a private GV in 240..255 so some other chart doesn't stomp on your precious answer
17:55 Ensign Howard: The vast majority of the GV use falls into the 0..239 category where the variable can be treated and temporary storage to pass a value from one DYO line to another in the manner of our first example.
17:53 scooter4: np, I confuse easily - okay thanks
17:49 Shar: Answers that for me too, scooter.
17:55 Ensign Howard: I will get to other more complex examples using 239..255 later in the class.
#1309-30MinColorBars
www.ensignsupport.com/email/1309.mhtml
17:53 Ensign Howard: Lets move on to this example where I used a DYO to color the bars for every 30 minute period a different color.
17:56 Ensign Howard: LIne A harvests for the bar the number of minutes this bar is from midnight. I like to use Minutes from Midnight because this is a nice incrementing number without the jump in clock time going from 9:59 to 10:00. If clock times in the form of hour and minute are used, then you see number of 959 jump to 1000 and that is a nasty 31 increment in the number.
17:58 Ensign Howard: The Minutes from Midnight has clock time converted into just minutes, so 10:00 would be 10x60 = 600 minutes. This time is divided by 30 so we get a count of half hour periods and the result is stored in GV[1]. The 10:00 time would be storing a value of 600 / 30 = 20.00
17:59 Ensign Howard: Line B will truncate off the fraction that might be present and resaves result in [1]. So at 10:00 a.m. we are in the 20th half hour period. 10:30 would be in the 21st half hour period.
18:01 Ensign Howard: Line C is very useful to convert these period numbers into sequences of 0, 1, 2, and 3, through the use of Modulo 4. Modulo is a math function for finding the remainder from the division by the number.
18:01 Ensign Howard: So 20 divided by 4 is 5 with a remainder of 0..... modulo answer will be 0
18:02 Ensign Howard: 21 divided by 4 is 5 with a remainder of 1..... so modulo answer is a 1.
18:03 Ensign Howard: Now that all time periods are converted into a sequence of 0,1,2 or 3, we use global flags to test this remainder stored in [2] and when the remainder matches a 0 we do a color bar marker in the color Green. When the remainder is a 1, we color the bar cyan, etc. This gives the four color rotation shown on our chart. Where as this is a 5-min chart, we see sequences of 6 bars having the same color.
18:05 Ensign Howard: Now this could also be used on tick charts, or range charts, etc, where the number of bars in a half hour period vary. And it will color them correctly according to their time stamp. If you wanted to have fewer colors in the rotation you would change the modulo number on Line C. If you want more colors in the rotation, such as 5, change the number on Line C to be a 5 and then
18:06 Ensign Howard: Add a Line H which is the color bar marker for the Value = # test when the remainder is a 4.
18:07 Ensign Howard: This example has a template of 1309-30MinColorBars which you can download
18:07 Ensign Howard: If you want a different period size for the coloring, you would edit the number on Line A to be a different division, such as 5 instead of 30.
18:07 Ensign Howard: Any questions about this example?
#1308
18:08 Ensign Howard: OK, lets move on to the 3rd example.
www.ensignsupport.com/email/1308.mhtml
18:09 Ensign Howard: This example is doing a similar period determination using Minutes from Midnight so we can group bars by timestamp. However, instead of coloring the bars, we want to use a private counter for the chart that is incremented with each additional bar in the same time period grouping, and reset the counter when we start a new period.
18:11 Ensign Howard: Line A and B determine the group number for the current bar.
18:11 Ensign Howard: Line C and D determine the group number for the prior bar..... this is accomplished by the Bar Offset being a -1 to reference the bar one bar back on the chart. First group number is saved in [2] and prior bar's group number is saved in [3]
8:12 Ensign Howard: Line F compares these 2 numbers... is Value in [2] greater then the number in [3]. This Boolean flag result (true or false) is saved in [4] and used by Line F. If the flag is True, we will plot a line to the counter size stored by the chart in its private GV [250]. More about the red line plot later.
18:14 Ensign Howard: Line G will also use the flag in [4] as a test. because the structure of the If statement is IF ( #, 0, Value). The first parameter is the test, which is the content of the number field which is the Boolean flag in [4]. When the test is true, the function returns the 2nd parameter which is a zero. When the test is False, the function returns the 3rd parameter, which is the GV referenced by Value which is the Read GV of [250]. So we get back a zero when the time period is changing because the flag is [4] is True. Otherwise, we get the current counter content in [250]. Now what do we do with the result.
18:16 Ensign Howard: Well, we turn around and write the value to the Write GV reference which is [250]. The net effect is we will zero out our counter in [250] when it is a new time stamp period or we will leave the contents of [250] as is by reading it and writing it right back out. Line G is just a clever way to conditionally reset the counter in [250] back to zero.8:18 Ensign Howard: Line H will increment our counter by reading it, adding 1 to it, and writing the answer back to [250]
18:18 Ensign Howard: And Line H provides the service of plotting this counter as a histogram style in blue.
18:19 Ensign Howard: See the chart example where the counter is stair stepping higher and higher by a uniform count of 1 for each adjacent bar until it gets reset because the time stamp is in a different 5-minute period.
18:20 Ensign Howard: Now a final comment about the red line, it is just illustrating the power of the statement IF Flag DO Plot #. This statement only plots on the first bar of the new period, and the value it plots to is the counter value before it is reset.
18:21 Ensign Howard: The clever part of this particular DYO statement is the line is connected as a straight line to the prior place it plotted to. So though it is does not plot on every bar, its image is connecting plot points when it does plot. This is in lieu of having blank space shown at the bar positions where the line normally would not plot because the condition is a false. This DYO needs to have the counter be a private chart variable...240-255.
18:24 Ensign Howard: See, we have here an example where we need to preserve the counter value between executions.... Line G reads the [250] before it is ever written.... which is exactly the principle I stated before. This DYO can be used on multiple chart, because each chart will have a private [250] it preciously keeps distinct from the other charts.
18:25 Ensign Howard: The GVs [1] through [4] were temporary use of GVs that were written by this calculation before they were used by a later line in this DYO.,
18:25 Ensign Howard: Has this been a good example to illustrate the answer to your question scooter?
18:25 scooter4: Yes excellent thanks Howard
18:26 Ensign Howard: Any questions about this speedometer example? It too has a template available you can download and play with.
DYO #1303
18:27 Ensign Howard: ok, we will move on to the final example in our class today, and this one is definitely advanced. However, it shows new capabilities added to Ensign in our spurt last month of adding lots of features to the program. So this class will help document the power of the new features of Looping and Bar Offset manipulation.
http://www.ensignsupport.com/email/1303.mhtml
18:28 Ensign Howard: This example is Knowledgebase article 1303 and comes with a template and needed 2 DYOs to implement, though the discussion of counting new High bars is applicable to counting new Low bars. The template does both and has twice as many line to do both as a result
18:30 Ensign Howard: First we need to understand what the user wanted. He wants to find the highest high in a set of 20 bars, and if this bar is setting the high we want to count it. Then he wants to count this New High condition across the preceding neighbors, which he also asked to be a scan of 20 prior neighbors. Hope the scan size of 20 and the set size of 20 is not too confusing.... either number could have been different.
18:32 Ensign Howard: To do the determination of a Highest high is easy to do with the Max High[#] and #=20 as shown on Line C. What makes this a complex example is the need to scan for this condition in the neighborhood ahead of the current bar to look for more counts to add to our counter.
18:33 Ensign Howard: Lets begin. The approach I took was to write a loop that will see if the bar under consideration is the high of its set.
18:34 Ensign Howard: Line A initializes the loop counter to a 20 and GV[1] will be the loop counter. This is similar to the loop count you would have in a FOR loop
18:34 Ensign Howard: Line B is initializing our counter in GV[2] to be a zero.
18:36 Ensign Howard: Lines C through H will be the body of our loop to accomplish our count determination of the number of times the bar set a new high in its set. Line C gets the Max High of the set of 20 bars and stores this high in [3]
18:36 Ensign Howard: Line D gets this bar's high and stores in [4]. If this bars high is the same as the Max High, then we need to count this bar as setting the new high.
18:37 Ensign Howard: So Line E is the clever counter control..... it tests the flag in [4] which was written by Line D
18:38 Ensign Howard: If the Flag is True, we will return the 2nd parameter which is the number field GV [2] and it will add 1 to this value. That is what the notation of #+1 means for the 2nd parameter, it reads and it adds 1.
18:39 Ensign Howard: If the Flag is False, this bar is not setting a new High, therefore return the 3rd parameter which is just the contents of our counter GV.
18:39 Ensign Howard: Line E rewrites the answer back in [2] so [2] either stays the same or it gets incremented
18:40 Ensign Howard: Any questions about our conditional incrementing our counter in [2]? Remember line B initialized the count to zero ahead of our loop.
18:41 Ensign Howard: So Line C, D, and E have counted the current bar, but we need to add to the count the neighboring bars on the left who were new high bars at the time.
18:43 Ensign Howard: So Line F and G are very clever in that they will modify the Bar Offset of Line C and D which get bar values at a particular bar position.
18:43 Ensign Howard: Line F and G say to Increment the Bar Offset on a particular line by the amount in the number field, and the number field has a -1. Thus the effect on the bar Offset is the decrement it to -1 and then on the next loop to -2, then on the next loop to a -3. The bar offset began at the start of the DYO with a 0 as shown on Lines C and D
18:45 Ensign Howard: Now line H is the loop control, it reads Value which is our loop counter in [1] and subtracts 1 from it and auto rewrites the counter back to Value. This is done in spite of Write GV not referencing [1]. The reason for this auto rewrite is because the result of this DYO line is going to be Boolean and not the loop counter decremented.
18:47 Ensign Howard: After decrementing our counter referenced by the Read GV setting, then this counter is compared to the # field. If the counter is greater than zero, the result of the Test will be True and the execution will loop back to Line C.
18:47 Ensign Howard: So on the first pass counter was at 20 and decemented to 19
18:48 Ensign Howard: on the 2nd pass counter was at 19 and decremented to 18
18:48 Ensign Howard: etc, on the 20th pass counter will be a 1, and decremented to 0 at which point the loop control on Line H will be false and we will terminate the DYO execution by going to Line I and J which do nothing. Thus the scanning loop executes 20 times and by manipulation of the Bar Offset, we did the identical test 20 times on 20 adjacent bars ahead of our starting point.
18:50 Ensign Howard: Thus our count in [2] will be the number of bars that set new highs in a view width of 20 bars.
18:50 Ensign Howard: 2nd DYO does the same thing in looping to find bars that set new lows. In the chart picture the arrows mark the bars that added to the high count to get to 1 and the low count to get to 5. The results of the DYO are shown using the section 1 message
18:52 Ensign Howard: The contents of the counter in [2] and [5] are shown in integer format because of the ` formatting character in the [2] reference in the message text
18:52 Ensign Howard: [2] would have shown 1.00 - [2`] shows instead a result of 1
18:53 Ensign Howard: Ok, your questions please?
18:53 dblue2: I have what I hope is a simple candle question.
18:53 dblue: Really like the flutes colored with buy/sell pressure, but miss candle wicks.. would it be possible to combine with perhaps a zebra type candle with wicks over the buy/sell pressure? or is it possible to reference the buy/sell pressure dividing line as a data point to be displayed at the scale of the bar?
18:53 Ensign Howard: ok. Well you strike out.... this is not a simple question. :-)
18:54 dblue2: ;))
18:54 Ensign Howard: However, the idea of a dividing line added to the bar display is a real possibility. So keep the existing candle style of Candlesticks, Solid Candles, Rockets or Zebras and let the DYO just add a dividing line.
18:55 dblue: If the data point is available... could use ma spread behind bar?
18:56 @Buffy2: It has been a great class Howard and will help with the understanding of dyo's.
18:56 Ensign Howard: Thx buffy.
18:56 scooter4: Thanks Howard, great class
AskBidRatio Template
18:57 Ensign Howard: Ok, on to dblue's request.... lets inventory the idea in mind and the tools to work with. We have an Ask Ratio and Bid Ratio and these will sum to 1.00. These ratios would be useful in locating a dividing line by working with the range of the bar. Add the percent of the range to the low of the bar and we should have the dividing price to mark. Let me show a DYO example that does these steps
18:59 Ensign Howard: 1 moment
18:59 @Buffy2: thanks for asking this dblue
19:00 dblue: ;))) I've been struggling with idea, but virt wouldn't help ;))
19:00 @Buffy2: lol
19:01 Shar: lol
19:01 Ensign Howard: here are the dividing line markers in the thick pink lines
19:01 dblue: So.. studies on top?
19:02 Ensign Howard: Yes, you are very observant
19:02 dblue: Occasionally :-)
19:02 Ensign Howard: This took 2 lines, Line A gets the bar's range and multiplies it by the Bid Ratio which is [$F] look up reference and saves this fraction of the range in [1]
19:03 Ensign Howard: Line B get the bar's low and adds the fraction of the range and plots it - so far looks good.
19:03 dblue: y
19:03 Ensign Howard: Now as dblue pointed out, if the Setup Chart property for Show Studies Behind the Bar is checked. Then the bars when they are wide end up hiding the divider marker. The marker will show if it falls on the wick but it is totally hidden by the candle body. So lets figure out a work around for this. How about if we have the DYO plot its own candle that is split at the divide point. So the divide point will be the low for one candle and the high for the 2nd candle plotted in the same position. This will take more cleverness, and I will need a couple of moments for that modification.
19:06 Ensign Howard: You all visit while I work on this - 2 moments
19:06 @Buffy2: Take as many as you need :-)
19:06 dblue: lol.. amazing -- doesn't even need Raymond lately
19:06 @Buffy2: Sure is. Howard has no problem thinking out of the box. lol nope he doesn't
19:09 Ensign Howard: I am upping my delay to 4 moments... brb
19:09 @Buffy2: lol
19:12 dblue: That doesn't really do it -- need the dividing line
19:12 @Buffy2: not really - the colors are right though right? If so, you can tell where many traded the wrong way
dblue: thinks so.. but have to ask virt ;))
19:14 @Buffy2: lol
19:15 Ensign Howard: Now do you want my black candles colored by Close vs Open relationship? 1 moment then
19:16 dblue: ;)))
19:19 Ensign Howard: Lets discuss this.
19:20 Ensign Howard: Line A initializes the DYO paint can to Green by the absence of any marker being plotted
19:20 Ensign Howard: Line B tests if the net is Down and changes color to Red.....
19:21 Ensign Howard: Line C, D, E and F accomplish the values for the Rockets marker, and with its color bucket being Black it uses the paint can instead which was left to be either green or red.
19:22 Ensign Howard: Line G and H do the ask/bid ration split on the bars range for a location of the pink divider line.
19:24 Ensign Howard:Will switch my paint can colors on A and B and use the test for Close> Open on Line B to set paint can color to Green and the Bars display is turned off because the DYO is plotting them. By being turned off they do not cover our DYO image regardless of the DYO plotting behind the bars or in front of the bars.
19:25 @Buffy2: :-) Neat trick
19:25 Ensign Howard: cool
19:25 @Buffy2: now that looks "normal" with the added information :-))
19:26 dblue: yup... great
19:26 Ensign Howard: Now dblue, it might be more mentally logical to expect the divider to be high on the bar when the trend is ascending and lower on the bar when the trend is descending. Therefore edit the [$F] marker to be [$E]. Use the Ask Ratio instead of the Bid ratio
19:27 Ensign Howard: yes, I kind of like that better.... little easier on the thinker
19:27 dblue: that is with E
19:27 Ensign Howard: yes, I recognized that immediately
19:27 @Buffy2: Yes and it is about 50% of bar for change
19:28 Ensign Howard: So when the divider floats high on the bar, it is an ascending bar with more trading at the ask than at the bid. I will have this uploaded for tomorrow as the AskBidRatio template. It is a good example, thanks for asking about such. Many will be pleased to have the template
19:29 dblue: Thank YOU!!!
19:30 @Buffy2: Yes thanks to you both
19:30 Ensign Howard: Well, lets wrap up the class. We have been at it for about 3 hrs and tired of typing
19:30 @Buffy2: That is exactly what I would like to look at.
19:30 Ensign Howard: I need to go home to rest and eat
19:30 @Buffy2: A well deserved rest Howard -- Thank you so much
19:30 Ensign Howard: You all have a great day
19:30 Shar: Thank you, Howard.
19:30 dblue: thanks again Howard
19:31 Ensign Howard: Welcome, thanks for attending and thanks for using Ensign Windows.
19:31 Ensign Howard: oh, as a side note -- I see posts on the Internet that AmeriTrade has bought out Jerry Medved's QuoteTracker. There may be some quotetracker tire kickers checking out Ensign this week since Ensign is frequently discussed as a great alternative. If such folks show up, I hope you will all give them a warm welcome and encourage them to seriously look at Ensign
19:33 @Buffy2: Thanks for heads up
19:33 Ensign Howard: thx
19:34 @Buffy2: The room is pretty good helping newbies and the videos make it easier for anyone to send someone where the answer is.
19:35 abc: nice!
19:35 Ensign Howard: Excellent, even more clever.
19:35 dblue: needs divider
19:39 Ensign Howard: OK, dblue, lets work together to tweak the implementation. Show me 1st DYO.
19:39 dblue: lol... thought you were going;))
19:39 Ensign Howard: You have me hooked - this is good stuff
19:39 @Buffy2: lol
19:39 Shar: Gosh, I was thinking how nice it would be to have the lines colored - and you are. lol
19:40 Ensign Howard: OK, that is fine, exactly as I would have done it myself.....lol. Please show me 1st ave
19:40 dblue: <--- blush
19:41 Ensign Howard: This we can improve on. I can envision the 2nd ave too. Please show me 2nd dyo
19:42 Ensign Howard: 1 moment for my touch
19:42 dblue: ;))) picturing dyo to do averages
19:43 @Buffy2: I learn a lot when he does this -- I have your last session with him too dblue that needs to get posted.
19:43 dblue: Good stuff.. great way to learn
19:50 dblue: hee hee same as those aren't bars ;))
19:50 @Buffy2: :-)
19:51 Ensign Howard: Done with 1 dyo and a line to spare..... ;-))
19:51 @Buffy2: :-)
19:52 dblue: cool
19:53 Ensign Howard: I doubled up lines as much as possible
19:53 Ensign Howard: Line A does the ratio of the range AND it initializes the paint can to red
19:53 Ensign Howard: Line B optionally changes paint can to Green
19:54 Ensign Howard: And if you want the divider line is the paint can color you can change the pink on Line I to be Black
19:54 dblue: Very nice. That was next ? ;)))
19:54 Ensign Howard: Line C does the back fill from Low to the divider
19:54 Ensign Howard: Line D does the divider to the high
19:54 Ensign Howard: Line E, F, G and H do the candle
19:54 Ensign Howard: Line I does the divider on top of the candle
19:55 dblue: Awesome H... thanks so much!!
19:56 dblue: Super
19:56 Ensign Howard: Not too shabby for a little bit of effort with the DYO
19:56 dblue: LOL
19:56 Shar: I like the red and green lines too.
19:56 Ensign Howard: The 1 DYO, of course, will be more efficient the 2 and 2 studies
19:57 Ensign Howard: OK, now I am really really leaving. Bye. Have a good evening
19:57 dblue: ;)) Bye. You too.
19:57 @Buffy2: Night Howard -- U 2
19:57 Shar: LOL Bye Howard. thx
19:57 dblue: You too
19:57 Shar: Will there be a template for that?
19:58 Ensign Howard: Yes, template I upload will be named AskBidRatio -- will do it tomorrow
19:58 Shar: Ok, thanks.
19:58 Ensign Howard: It has already evolved in the last 10 minutes......lol
19:58 @Buffy2: lol Amazing how that happens. The end result is better too
19:59 @Buffy2: thanks
19:59 dblue: Told you he couldn't do it ;)))
19:59 Ensign Howard: Thats the final DYO for the prior chart
19:59 Shar: Thanks!
19:59 Ensign Howard: Where's Raymond.... I need Raymond episode to recover
19:59 @Buffy2: LOL
19:59 dblue: LOL!!!!!!!