Trady.Analysis 2.1.0-beta2

This is a prerelease version of Trady.Analysis.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Trady.Analysis --version 2.1.0-beta2                
NuGet\Install-Package Trady.Analysis -Version 2.1.0-beta2                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Trady.Analysis" Version="2.1.0-beta2" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Trady.Analysis --version 2.1.0-beta2                
#r "nuget: Trady.Analysis, 2.1.0-beta2"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Trady.Analysis as a Cake Addin
#addin nuget:?package=Trady.Analysis&version=2.1.0-beta2&prerelease

// Install Trady.Analysis as a Cake Tool
#tool nuget:?package=Trady.Analysis&version=2.1.0-beta2&prerelease                

Analysis module of Trady, a handy library for computing technical indicators, based on .NET Standard 1.4

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp1.0 was computed.  netcoreapp1.1 was computed.  netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard1.4 is compatible.  netstandard1.5 was computed.  netstandard1.6 was computed.  netstandard2.0 was computed.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen30 was computed.  tizen40 was computed.  tizen60 was computed. 
Universal Windows Platform uap was computed.  uap10.0 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Trady.Analysis:

Package Downloads
InverseFisherTransformOnStochastic

Inverse Fisher Transform on STOCHASTIC About John EHLERS: From California, USA, John is a veteran trader. With 35 years trading experience he has seen it all. John has an engineering background that led to his technical approach to trading ignoring fundamental analysis (with one important exception). John strongly believes in cycles. He’d rather exit a trade when the cycle ends or a new one starts. He uses the MESA principle to make predictions about cycles in the market and trades one hundred percent automatically. In the show John reveals: • What is more appropriate than trading individual stocks • The one thing he relies upon in his approach to the market • The detail surrounding his unique trading style • What important thing underpins the market and gives every trader an edge About INVERSE FISHER TRANSFORM: The purpose of technical indicators is to help with your timing decisions to buy or sell. Hopefully, the signals are clear and unequivocal. However, more often than not your decision to pull the trigger is accompanied by crossing your fingers. Even if you have placed only a few trades you know the drill. In this article I will show you a way to make your oscillator-type indicators make clear black-or-white indication of the time to buy or sell. I will do this by using the Inverse Fisher Transform to alter the Probability Distribution Function ( PDF ) of your indicators. In the past12 I have noted that the PDF of price and indicators do not have a Gaussian, or Normal, probability distribution. A Gaussian PDF is the familiar bell-shaped curve where the long “tails” mean that wide deviations from the mean occur with relatively low probability. The Fisher Transform can be applied to almost any normalized data set to make the resulting PDF nearly Gaussian, with the result that the turning points are sharply peaked and easy to identify. The Fisher Transform is defined by the equation Whereas the Fisher Transform is expansive, the Inverse Fisher Transform is compressive. The Inverse Fisher Transform is found by solving equation 1 for x in terms of y. The Inverse Fisher Transform is: The transfer response of the Inverse Fisher Transform is shown in Figure 1. If the input falls between –0.5 and +0.5, the output is nearly the same as the input. For larger absolute values (say, larger than 2), the output is compressed to be no larger than unity . The result of using the Inverse Fisher Transform is that the output has a very high probability of being either +1 or –1. This bipolar probability distribution makes the Inverse Fisher Transform ideal for generating an indicator that provides clear buy and sell signals.

MostDLL

MOST : Moving Stop Loss Indicator Developed by economist Anıl ÖZEKŞİ for MATRİKS TRADER platform. This indicator is like a trailing stop indicator but differs in two ways. First, trailing stops often uses price bars to determine the stop level, but MOST uses an adjustable percent of the Exponential Moving Average of the price which smooths the sudden price moves. The second thing is that MOST gives BUY and SELL signals instead of giving one way signals for price action. MOST has an EMA and a trailing percent stop level of EMA that can be adjusted by changing the length of the EMA and %percent of the stop level. DLL Created and Developed by Melih Tuna https://twitter.com/crypto_melih

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
3.2.8 106,615 2/22/2020
3.2.6 1,768 1/11/2020
3.2.5 616 1/11/2020
3.2.4 598 1/11/2020
3.2.3 606 1/11/2020
3.2.2 631 1/7/2020
3.2.1 673 12/26/2019
3.2.0 4,404 9/16/2018
3.1.1 1,624 7/21/2018
3.1.0-beta2 706 7/9/2018
3.1.0-beta1 1,394 2/22/2018
3.1.0-beta0 842 11/14/2017
3.0.0 1,859 9/25/2017
2.1.0-beta6 701 9/19/2017
2.1.0-beta5 744 9/15/2017
2.1.0-beta4 691 9/14/2017
2.1.0-beta3 740 8/29/2017
2.1.0-beta2 733 8/24/2017
2.0.1 1,045 6/26/2017
2.0.0 1,133 6/25/2017
1.2.0 1,149 3/22/2017
1.1.0 1,002 2/26/2017

[17/8/2017] (Breaking Change) Makes clear between computation with tuples and computation with candles. Tuple input -> Tuple output, Candle input -> Tuple with datetime output
[26/6/2017] Multiple Culture Support, Extended ClosePricePercentageChange and ClosePriceChange (Thanks to @fernaramburu for the contribution)
[25/6/2017] Various breaking changes, please refer to https://github.com/lppkarl/Trady
[22/3/2017] Some breaking changes, fix indicators: BbWidth, Adxr, IchimokuCloud, Atr, indicators added: Er, Kama, Mema, Sd
[26/2/2017] System structure refinement, merged with Trady.Strategy project
[24/2/2017] Removed the needs of adding RegisterDependencies, added TickProviderBase class to help constructing tick provider for value retrieval      
[23/2/2017] Renamed some classes and methods, some bug fix on indicator computation
[21/2/2017] First release