Get started

PROFILING

HTF Candle Profile & Dealing RangeBuilt around the concept of HTF candle profiling and dealing ranges. When a new HTF candle opens, the open line gives you an immediate reference point to profile price from. For a bullish candle formation, price typically trades lower first to form its wick before expanding higher and then closing. You are looking to spot the protraction phase (aka wick formation) of the HTF candle you are trading to then align yourself with the body (aka the expansion phase of the candle). The open line is your reference for validating the profile and confirming the candle is behaving as expected. For bearish it is the mirror. Price trades high first to form the wick, then expands lower to create the candle body and then closes. The EQ of the previous candle's dealing range acts as your continuation/invalidation level. In a true expansion, price should not make deep retracements back into the prior range. A breach of EQ questions the move. If price holds and continues, you stay in and target the prior swing high or low along with whatever HTF draws you have mapped beyond that. The dealing range, wick high to wick low of the previous HTF candle, gives you the full boundary of where price came from and what it needs to respect or break to confirm the next move. Auto-detects your chart timeframe. No manual setup needed. Pairings: M1/M15 · M3/M30 · M5/1H · M15/4H · M90/6H · 1H/1D · 4H/1W
Pine Script® indicator
by nevelstrades
Profiling: array of UDTs vs UDT of arraysUsing Stopwatch Library by PineCoders, I am trying to test which is faster, an array of user-defined type (UDT) objects vs an object with many child arrays. The task is to store and manipulate array of objects having total 9 values: 4 floats, 4 strings and 1 int. Option 1: create a UDT with 9 fields and store an array of such UDT objects. Option 2: create a UDT with 9 arrays individually for each value. The test task is of three stages: Populate array(s) with some (timenow) values - in the options you can choose how many values to push into the array/arrays. Note that max size of array(s) is set independently, so you can push 1000 of elements into an array capped at 100 max size and as new elements will be pushed (added to the end) the old exceeding elements will be shifted (removed from the beginning) Write - write to random elements of the array. Two options for writing to a UDT object: (1) assign to each field independently, (2) create a UDT object and use array.set() function. Read - read from random elements of the array. In the options you can how many times per bar to run each of the steps (same number for each step). I tested by adding three indicators to the chart and choosing different options for each: 1. Array of UDT's where writing is done by creating a new UDT from the values and then using set(udt) 2. Array of UDT's where writing is done by assigning the value of each of the properties of the UDT individually (saving time on creating of a new object). 3. UDT of arrays. As of 16 Arpil 2023 the UDT of arrays seems about 20-30% faster than the array of UDT's with setting each property without creating new UDT object.
Pine Script® indicator
by moebius1977
1