Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Seth: "If you really want to get fancy you can take advantage of some of C#'s unique features to add GUI elements to the chart, or create an pop out window for it."
Yep, I know that; but surely you're not saying that getting involved
with a WPF or even a WinForms Gui (using the WPF Winforms hosting
control) is EASIER than a simple file you can edit?
What's simpler than a Properties file?
I'll attach my User Interface to my Interactive Order Entry and
Analytics Strategy, by way of establishing my "bona fides" in the
area of User Interface; yes, I know that's possible... thanks.
If anybody's wanting to do a User Interface, and it's going to
be "dense" and "complex" then Winforms is the way to go...
WPF is really not up to the task that I needed for my Order
Entry and Analytics Integrated Triggering system, pic attached.
[edit] That custom facility is capable of handling many dozens of simultaneous
staggered positions, with independent automatic target profit taking; and achieving
"limit entry; limit exit" for near wholesale pricing; with LIFO accounting so partial
profits offset open losses in a complex multi-position "aggregate" trading "frame"...
Pretty much impossible to describe, and not for sale...
hyperscalper
Can you help answer these questions from other members on NexusFi?
Adding a text box to a chart or a popup window is a few dozen lines. Yes, it would be quite a bit easier than the code we currently have to parse text. It would also be compatible with existing NinjaTrader tools, and be easier for new programmers to understand. I have my own advanced solutions for this stuff, but if it's about helping others do similar things and collaborate I think its better to strip it down to base NinjaTrader functionality.
My objectives were to encourage Traders to get into coding; as
well as contributing a simple but fully functional solution.
Controversy is just fine; yours is the mainstream perspective.
So, why don't you put up your proposed code solution so everyone
can see how you think it should be done? What would be the
harm in doing that? I know that you do have advanced
coding abilities... So?..... Why not?
My code would have to be converted to a "Virtual Time" based on
incoming data, everywhere in the code; and then it could work
on both Historical and RealTime data; not a huge task...
[edit] of course any allocated objects would need to be carefully
dismantled so resource leaks would be avoided on re-activations
of the Indicator, when a Property was changed; or when a run was
made in some sort of Backtester... maybe I should do it myself,
as an exercise... but I'm not making the commitment to do it yet.
OK, so let's take this thing in at least 2 Phases.
Just processing data during the "backfill" State.Historical
phase turns out to be a "shyte show" using NinjaTrader.
Among other things, you may have to use a weird Data Series
which has the characteristics of a "Bid/Ask Series"; and also
in Realtime, data appears on OnMarketData; but that seems
not to be the case in the Historical phase.... it seems the
action has to take place in OnBarData... Hey, I'm not
an Indicator expert; so you can "dis me" all you want.
But, it's kind-of a a mess when you want the Indicator
to work that way...
However, I'm committed to at least doing backfill; which means
that when the Indicator is restarted, it will at least do a
decent job of characterizing Historical data; instead of just
starting with RealTime data.
It's fun looking at these things, which I don't use, since I only
use Realtime data processing...
So I'm sure y'all are "wishing me Luck" in at least getting
the Historical backfill working, before we transition into
Realtime... I did learn some things by researching this; so
it never hurts to experiment !!
I had been capturing Bid and Ask on those callbacks to the
OnMarketData overload; but the Last event carries with
it the Bid and Ask pricing; so that's good to know, and
the Last event may be the only event you have in certain
runtime phases... Good to know.
Hey, get into some coding !! That was the reason for doing
this thing... Meanwhile, back to hacking...
The TradeFlowRisk indicator (2 instances) is shown here; and
note the situation before the "classic dive" which NQ/MNQ
performs toward the close of Tuesday's session (today).
Note the Short Risk at the top; and significant Short Inventory
prior to the dive.
I've said before that this is a "situational analysis" but it is warning
us that a dive is entirely possible...
Params are:
comment line
RISK_THRESHOLD=10
RETENTION_SECONDS=120
MULTIPLIER=2.5
BIGLOT_MINIMUM=2
TAPER_SIZE=True
SUPER_SPIKE_THRESHOLD_RATIO=4
and...
# comment line
RISK_THRESHOLD=10
RETENTION_SECONDS=900
MULTIPLIER=1
BIGLOT_MINIMUM=2
TAPER_SIZE=True
SUPER_SPIKE_THRESHOLD_RATIO=6
Note the 2 Indicator instances are set to Left margin; dragged over Price,
and also Zero is Cntl-Dragged to middle, and vertical scale is
dragged to suit; plus one of them is using a MULTIPLIER to make
it relatively bigger in swings up/down... etc. lol
The system shown is just a demonstration of what MNQ
micro scalping might look like. We can discuss key
features, for those who are interested; but this is
not available; so please don't ask.
Listen, nearly everyone that trades does it in their own, unique way and if this order entry and trade management tool works for your trading then more power to you (especially if you programmed it yourself, that's next level!).
I've never had to use more than a buy, sell, close, and reverse button with my trading, so perhaps not finding a use for these tools says something negative about my trading (or at least the sophistication of my order management)?
When the Nasdaq futures swings +/-40 POINTS = 160 TICKS
then it's hard to predict; however...
As you can see from the screen shot, even though this may
be only what I've called a "situational variable" you can
see strong correlations between Inventory/Risk and Price
swings...
Runs like this really FORCE the Trader to "chase" trend; so
at least there's some reason why the trend may be
changing... ? Just sayin' LOL
[EDIT] The Devil is in Details... Notice that the Screenshot is running on
MNQ, the micro contract; and it is possible, though not that likely, that
the same analysis side by side on the larger eMini NQ contract could show
differences in the patterns. We are looking at Time and Sales based
information here... Just sayin'... Mileage could vary...?
