VIDEO: How to find stocks with a high risk-reward-ratio by looking at the
More from Julian Komar
More from Screeners
I use 4 scanners:
1) Volatility, Volume & daily range compression scanner
2) Punch-Drunk-Love
3) GE Ratio - to track fundamentally strong stocks
4) Recently created one to track Power Play setups.
I get around 150-200 stocks daily & choose the ones with the most potential.
1) Volatility, Volume & daily range compression scanner
2) Punch-Drunk-Love
3) GE Ratio - to track fundamentally strong stocks
4) Recently created one to track Power Play setups.
I get around 150-200 stocks daily & choose the ones with the most potential.
Sir, How do u find a set up - Do you track chart of each stock daily ? Or do u have filters , that lead you to a number of stocks , after which you scan them.
— AKASH GUPTA (@lockdownmurti) August 25, 2021
VWAP for intraday Trading Part -2
A small thread.
PART 1 - https://t.co/ooxepHpYKL
Traders show your support by like & retweet to benefit all
@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @RajarshitaS @Puretechnicals9 @AnandableAnand @Anshi_________ @ca_mehtaravi
Chart 1
Chart 2
Chart 3
Chart 4
A small thread.
PART 1 - https://t.co/ooxepHpYKL
Traders show your support by like & retweet to benefit all
@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @RajarshitaS @Puretechnicals9 @AnandableAnand @Anshi_________ @ca_mehtaravi

VWAP for intraday Trading Part -1
— Learn to Trade (@learntotrade365) August 28, 2021
A small thread PART -2 will be released tomorrow
Traders show your support by like & retweet to benefit all@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @ArjunB9591 @CAPratik_INDIAN @RajarshitaS @Stockstudy8 @vivbajaj @Prakashplutus pic.twitter.com/y8bwisM4hB
Chart 1

Chart 2

Chart 3

Chart 4

You May Also Like
Keep dwelling on this:
Further Examination of the Motif near PRRA Reveals Close Structural Similarity to the SEB Superantigen as well as Sequence Similarities to Neurotoxins and a Viral SAg.
The insertion PRRA together with 7 sequentially preceding residues & succeeding R685 (conserved in β-CoVs) form a motif, Y674QTQTNSPRRAR685, homologous to those of neurotoxins from Ophiophagus (cobra) and Bungarus genera, as well as neurotoxin-like regions from three RABV strains
(20) (Fig. 2D). We further noticed that the same segment bears close similarity to the HIV-1 glycoprotein gp120 SAg motif F164 to V174.
https://t.co/EwwJOSa8RK
In (B), the segment S680PPRAR685 including the PRRA insert and highly conserved cleavage site *R685* is shown in van der Waals representation (black labels) and nearby CDR residues of the TCRVβ domain are labeled in blue/white
https://t.co/BsY8BAIzDa
Sequence Identity %
https://t.co/BsY8BAIzDa
Y674 - QTQTNSPRRA - R685
Similar to neurotoxins from Ophiophagus (cobra) & Bungarus genera & neurotoxin-like regions from three RABV strains
T678 - NSPRRA- R685
Superantigenic core, consistently aligned against bacterial or viral SAgs
Further Examination of the Motif near PRRA Reveals Close Structural Similarity to the SEB Superantigen as well as Sequence Similarities to Neurotoxins and a Viral SAg.
The insertion PRRA together with 7 sequentially preceding residues & succeeding R685 (conserved in β-CoVs) form a motif, Y674QTQTNSPRRAR685, homologous to those of neurotoxins from Ophiophagus (cobra) and Bungarus genera, as well as neurotoxin-like regions from three RABV strains
(20) (Fig. 2D). We further noticed that the same segment bears close similarity to the HIV-1 glycoprotein gp120 SAg motif F164 to V174.
https://t.co/EwwJOSa8RK

In (B), the segment S680PPRAR685 including the PRRA insert and highly conserved cleavage site *R685* is shown in van der Waals representation (black labels) and nearby CDR residues of the TCRVβ domain are labeled in blue/white
https://t.co/BsY8BAIzDa

Sequence Identity %
https://t.co/BsY8BAIzDa
Y674 - QTQTNSPRRA - R685
Similar to neurotoxins from Ophiophagus (cobra) & Bungarus genera & neurotoxin-like regions from three RABV strains
T678 - NSPRRA- R685
Superantigenic core, consistently aligned against bacterial or viral SAgs

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.