QChartist Forum - Tutorials and tips

Proper analysis of the trend and patience are keys

Thu, 28 Aug 2025 12:52:30 +0000

The lesson I’d like to teach you today is that when you are confident about the trend over a good period of time, thanks to spectral analysis and other powerful indicators, even if your positions fall into the red for a while, don’t cut your losses! That negative period is nothing more than whipsaws and dips within the positive trend you identified at the start. Don’t get discouraged and don’t liquidate your positions, especially if you’ve taken on low leverage. Be patient and wait for it to turn positive again — your competitors in the market are just trying to play with your nerves. It’s a game of patience, and in the end, the most patient one wins!

Spectrometer Hurst and FFT

Wed, 13 Aug 2025 13:06:28 +0000

First find a good signal with the System #4 QChartist's Magic Hat Trick System

Then here is an idea to confirm the entry :

Yes — combining a Fast Fourier Transform (FFT) with the Hurst Cycles Spectrometer can be more powerful than using either one alone, but they serve slightly different roles:
1. What FFT brings to the table

Broad-spectrum detection – FFT quickly identifies all periodic components in data, even weak ones, over a wide frequency range.
Mathematically rigorous – It decomposes the signal into precise sine and cosine waves, giving clear frequency peaks.
Fast computation – You can process large datasets quickly and spot new cycle candidates.

2. What Hurst’s method adds

Market-specific filtering – Hurst's approach is tailored to financial series, which are noisy and non-stationary, so it focuses on cycles that actually persist and matter for trading.
Phase and translation to trading context – It ties cycles to timing models, peak-trough forecasts, and “nominal model” cycle families.
Noise suppression – It tends to filter out meaningless peaks that FFT might still show.

3. Why combining them works

Use FFT as a scouting tool to identify candidate dominant frequencies.
Feed these frequencies into Hurst’s spectrometer for deeper analysis, smoothing, and validation against price action.
This two-step approach reduces false positives and gives both mathematical rigor and market relevance.

4. Potential workflow

FFT Stage – Run FFT on your price data → note the strongest frequency peaks.
Hurst Stage – Use those frequencies as starting points → refine them, track amplitude and phase over time, integrate into trading cycle forecasts.
Feedback loop – Re-run FFT periodically to catch emerging cycles and retire fading ones.

If you like, I can sketch out a practical hybrid FFT + Hurst workflow so you can see exactly how the steps fit together for trading cycle analysis.

If your FFT and Hurst Cycles Spectrometer outputs are synchronized—meaning they both highlight the same dominant cycle lengths at the same time—that’s a pretty strong signal in cycle analysis.
Here’s why:

1. Higher confidence in the cycle

FFT is purely mathematical: it doesn’t “care” about market theory—it just decomposes data into sinusoidal components.
Hurst’s spectrometer is market-aware and noise-tolerant, looking for persistent cycles.
When both agree, it suggests the cycle is not just a random spike in the spectrum but a structurally persistent rhythm in the market.

2. More reliable timing

FFT alone can’t tell you where in the cycle you are—it only identifies frequencies.
Hurst’s method tracks phase (peak/trough positions), giving actionable timing.
Synchronization means your frequency detection and your phase model are aligned, so your turning-point forecasts are more trustworthy.

3. Reduced false positives

FFT can be fooled by transient noise patterns.
Hurst can be biased by pre-set “nominal cycle” expectations.
When they independently lock onto the same cycle, the chance that it’s noise drops significantly.

4. Potential trading edge

You can trade with the cycle’s rhythm, entering near troughs and exiting near peaks with greater conviction.
You might also size positions more aggressively when both methods agree, since the statistical edge is higher.

In practice, people often set up something like:

FFT Spectrum → watch for strong peaks that persist for several bars of data.
Hurst Analysis → see if it confirms the same cycle length and shows favorable phase for entry.
Trade Filter → only act when both are in sync, plus price action agrees.

If you want, I can outline exactly how to run and sync these two analyses in a single charting workflow so they reinforce each other in real time. That’s where the real power comes in.

Both indicators are available for QChartist (separate canvas)

Include new c++ library flags in the compilation

Wed, 13 Aug 2025 07:17:13 +0000

Hello everybody,

i use the RQPC RapidQ Pre Compiler from Jacques and i compile C++ code in my RapidQ program.
But the problem is that i don't know how to link new libraries (flags) for the mingw G++ compiler that is used by RQPC.
For example if i want to link C++ OpenGL library in need to use the -lGL flag with G++
Can anybody add this functionality to RQPC that will allow to use custom flags for the compiler, this would help me a lot for example to use python code in my RapidQ programs. Jacques didn't share the source code of his RQPC unfortunately.

Thank you for your help!

In fact, to run a python code, i want to link the python library to g++, include my python code to example.cpp
#include "Python.h"
Py_Initialize();
and so on....
and then use rqpc to compile example.bas with example.cpp
compile example: g++ art_wrapper.c main.cpp -o main -lpython2.8
I know this is technically possible, so that i can use values of the variables of my python calculations directly in my rapidq.bas program
But to do that rqpc should be able to accept the option to include custom libraries to link with g++ (-lpython2.8)

I found a way to do what i want without modifying rqpc but it's a bit tricky.
For the moment, the only workaround i found is to rename g++ to g++2.exe and create a new g++ executable that will collect the command line arguments of itself (after %0 (g++ itself)) and that will execute g++2.exe with all the collected arguments + -lpython2.8
Then, when RQPC will call g++, g++2 (the original file) will be executed with the new flag -lpython2.8

Hello Jacques, thank you for your code of the g++.bat
I managed to make it work !

In fact RQPC needs a g++.exe so i had to convert my g++.bat to g++.exe with a bat2exe converter

I found this converter which works fine : https://github.com/tokyoneon/B2E
https://qchartist.net/files/utils/Bat_To...verter.zip

My g++.bat for example contains this line :
c:\myprogram\mingw\bin\g++2.exe %* -lopengl32 -lglu32 -lglut
rem So we add opengl C++ support to our RapidQ program

i rename the original g++.exe to g++2.exe and
i create a g++.exe with the B2E tool from my g++.bat

myprogram.bas contains the rapidq code:
''pre cmd FBVERSION=017 FBLANG=deprecated run enc noopt exe con NoDone icon myprogram.ico kill includes\cppincludes.cpp
''pre end
'Compiler Directives
$APPTYPE console 'GUI
$OPTIMIZE on
$TYPECHECK on
dim cpptmpfuncreturn as string
myvar = VAL(mytext.Text)
defstr myvarstr=str$(myvar):cpptmpfuncreturn=varptr$(setsomething(varptr(myvarstr))) ' we interact with c++ this way
and so on...

includes\cppincludes.cpp contains the c++ source code of our opengl program to include to our rapidq myprogram.bas :
// ''RQEXPORT function setsomething(parameter)
#include "includes\myopenglprogram.cpp"

then i compile my program with
rqpc\rqpc myprogram.bas

bingo

How to create a custom indicator

Sun, 01 Jun 2025 11:40:42 +0000

Here is a simple diagram to explain how works the file structure and flow:

Code:
+------------------+        +---------------------+        +-------------------+

|  indicatorname.qtp| -----> |   indicatorname.qtr  | -----> |  indicatorname.cpp | 

|  (Settings GUI)   |        | (Runtime & Drawing)  |        | (Calc & Buffers)   |

+------------------+        +---------------------+        +-------------------+

                                    |                             |

                                    |                             |

                                    v                             v

                           +------------------+        +---------------------+

                           |  getbufferdata.cpp| <---- |  indicatornamebuffer  |

                           | (Buffer Access)   |       |   (Static arrays)     |

                           +------------------+        +---------------------+

Additionally:

+------------------+

| indicatorname.ini |

| (Meta Settings)   |

+------------------+

+------------------+

|   cppincludes.cpp |

| (Include cpp file)|

+------------------+