Skip to main content

Introduction to candlestick analysis

 We will start with the fundamentals of technical analysis and then progress step by step to the advanced concepts so that, at the end of this book, we will be able to interpret and trade with any kind of chart. 

Even those who have prior experience in trading should not skip the following section. It contains a different approach that is not often addressed in conventional technical analysis and it is a prerequisite for a successful price analysis.

Line charts

For most people, line charts usually provide the first impression of the world of financial markets because we see them frequently when we open the newspaper or turn on the television.

A line chart can describe the price development of a stock, a currency pair, a cryptocurrency, a commodity and any other financial value. The advantage of a line chart is that the information is highly compressed. One glance at the line chart tells you all that you want to know for a first elementary analysis.

If we see a rising line chart, it indicates a rally or a bull market (a bull thrusts its horns in the air). If the line chart shows a falling price, it indicates a bear market (the bear swipes his paws down).

The closing prices for a day are usually plotted and joined together in a line chart. Every day, we move one time unit to the right on the scale. This kind of chart is also called a daily chart.

The disadvantage of a line chart is that the price fluctuations within a day – or any chosen time period - cannot be recorded since the line chart shows only the closing prices. However, we all know that there can be strong price fluctuations in the financial markets and neglecting them can be a disadvantage for the precise technical analysis.

Candlestick charts

Candlestick charts are further developed line charts that serve to compensate for the disadvantage of less information. Candlestick charts have their origin in 17th century Japan. Today, candlestick charts are the preferred tool of analysis for traders and most investors since they provide all the required information at a glance.

The candlestick

As the name suggests, a candlestick chart is made up of so-called (price) candlesticks. These candlesticks are made up of different components to describe the price movements of financial instruments.

Two sample candlesticks are shown in figure candlestick consists of a solid part, the body, and two thinner lines which are called candle wicks or candlestick shadows.

The candlesticks are color-coded to illustrate the direction of the price movements. A white candlestick represents rising prices, whereas a black candlestick shows that the price fell during the period.

The length of the shadows shows how much the price has moved up and down with respect to a candlestick within a specific duration. If we set our charts so that one candlestick corresponds to one day, then we can read the daily fluctuations in the financial market using the shadows of a candlestick.
The candlestick body describes the difference between the opening and closing prices for the corresponding time period.
The body of the white, rising candlestick in figure 6 shows that the price opened at $10 and closed at $20 in the selected time interval, but has fluctuated between $25 and $5 in the meantime, as indicated by the shadows.







Comments

Popular posts from this blog

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to_native_string   File "/usr/lib/python2.

tag