The Lab

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

Aggressive vs  Resting Orders

Orders may be:

  • Aggressive - These orders are matched against existing Resting orders held in the order book. Once submitted these orders typically cannot be cancelled or modified.
  • Resting - These orders are submitted at price levels away from the prevailing market, i.e.  buying at a price below or selling at a price above the market.

Time In Force

Details of the TimeInForce values supported by Whisperer Enterprise for both categories are provided below.

The time in force instruction may optionally be refined by the specification of order activation and expiry times:

  • Activation - A specific order activation time may be specified via tag 168/EffectiveTime.
  • Expiry - Order expiry may be specified as a specific time via tag 126/ExpireTime, or as a duration via tag 1629/ExposureDuration. The two representations may not be used together. 


NameNatureDescription59/TimeInForce168/EffectiveTime126/ExpireTime1629/ExposureDuration
Immediate Or CancelAggressiveThe Order must be executed immediately, at least in part (Partial fills are allowed), otherwise the Order is cancelled. AKA 'Fill and Kill'.
IOCOptional--
Fill Or KillAggressiveThe Order must be executed immediately, in full (no Partial fills), otherwise the Order is cancelled.FOKOptional--
Good For AuctionRestingTODOGFAOptionalOptionalOptional
Good For DayRestingThe Order expires automatically on close of the trading day, if it is still unfilled.GFDOptionalOptionalOptional
Good For TimeRestingOrder is active for a specified duration. TODO TWAP?GFTOptional-Mandatory
Good 'Til DateRestingOrder is active until a specified time. TODO TWAP?GTDOptionalMandatory-
Good 'Til CanceledRestingThe Order remains active until it is either executed or cancelled. NOTE: Maximum possible duration is one trading week, but is equivalent to DAY for most Venues that reset daily.GTCOptional--
At Market OpenRestingTODOAMOOptional--
At Market CloseRestingTODOAMCOptional--

Order Types

There are three broad categories of order type:

  • Market - these are aggressive orders that are instructions to deal immediately at the best possible price. When buying, a market order will be filled at the currently prevailing Offer price; when selling, a market order will be filled at the currently prevailing Bid price.
  • Limit - these are resting orders visible to the market - hence the existence of Central Limit Order Book (CLOB) ECNs. They are instructions to deal if a market moves to a specific (more favourable) price or better. Limit orders remain open until they are either entirely filled, or the client submits an order cancel request, or the order expires.
  • Stop - these are resting orders that are not visible to the market and will activate once a specified Stop price has been met.

When matched in a CLOB ECN, Limit orders are said to be 'aggressed' by Market orders.

Details of the OrderType values supported by Whisperer Enterprise for all categories are provided below.


NameCategoryDescription 40/OrdType44/Price99/StopPrice210/MaxShow110/MinQty389/DiscretionOffsetValue211/PegOffsetValue836/PegOffsetType




Limit priceStop priceIceberg tip size
Added to Bid or subtracted from Offer limit price to specify the allowed slippage for the order.

Previously QuotedMarketAn order to hit an individual quote. To hit multiple quotes, aka sweeping, the user must submit individual orders from best to worst price.PreviouslyQuotedMandatory---'TODO--
MarketMarketAn instruction to deal immediately at the best possible price (the current rate).Market----TODO--
Dark MarketMarket
Market--ZeroOptionalTODO--
Market To LimitMarketOrder that starts as a Market order and executes any leaves quantity as a Limit order.MarketWithLeftOverAsLimit----TODO--
Market If TouchedMarket
IfTouched-Mandatory--TODO--
LimitLimitAn instruction to deal if a market moves to a more favourable level.LimitMandatory---TODO--
Dark LimitLimitAKA "Hidden Limit", "Ghost".
Mandatory-ZeroOptionalTODO--
Limit To MarketLimit
FunariMandatory---TODO--
Limit If TouchedLimitOrder will be submitted to market when a specified price is reachedIfTouchedMandatoryMandatory--TODO--
VwapSweepLimitAn order that can hit/lift one or multiple quotes by submitting an order with the desired amount and the Volume Weighted Average Price (VWAP) of the total amount.VWAP Sweep???TODOTODO`-TODOTODO--
TWAPLimitTODOLimitTODOTODO`-TODOTODO--
IcebergLimitTODOLimitMandatory-Mandatory-TODO--
PeggedLimitAn order with an optional offset to the prevailing market rate. The displayed quantity will float with the market up to the limit price of the order.PegOptional-Optional-TODOOptionalOptional
StopStopAKA "Stop Loss". An instruction to deal if a market moves to a less favourable level.Stop-Mandatory--TODO--
Stop LimitStopExecutes an exposure-reducing limit order when market exceeds order's price.StopLimitMandatoryMandatory--TODO--
Trailing Stop LimitStopA Stop Limit order where the stop trigger price at a fixed amount below the market price, based on the user-defined "trailing" amount. The limit order price is also continually recalculated based on the limit offset.
----MandatoryMandatory-
Stop limit at riseStopDetermined by Side?StopLimitTODOTODOTODOTODOTODOTODOTODO
Stop limit at fallStopDetermined by Side?StopLimitTODOTODOTODOTODOTODOTODOTODO
Stop-TrailingStopThe Stop Price follows the market by a specified offset.Trailing StopTODOTODOTODOTODOTODOTODOTODO
Limit Take Profit
A Limit Order will be placed when the market reaches the Trigger Price
TODOTODOTODOTODOTODOTODOTODO
Fixing


TODOTODOTODOTODOTODOTODOTODO
Mid


TODOTODOTODOTODOTODOTODOTODO



Treat as Alog strategies:

From QUOD(!!!)

AlgoCategoryDescription
Adaptive Liquidity SeekingLiquidity SeekingAn algorithm which reacts to market events such as market data, execution and a set of other criteria to dynamically update the decision tree to seek liquidity on lit and dark venues.
Adaptive TWAPExecutionA slicing algorithm that submits equal size slices over a certain timeframe. Maximum participation rate can also be taken into account
Adaptive VWAPExecutionA benchmarking algorithm that slices an order according to the historical volume reparation over a certain time horizon. Every slice benefits from the adaptive execution that takes into account the current market conditions and the aggressivity of the algorithm.
Arrival Price / Implementation ShortfallExecutionAn algorithm that regularly adapts its participation based on estimated market impact in order to remain within a given price band. Participation is increased when the probability of high market impact is low and decreased when the probability is high. Adaptation of the participation is based both on historical behaviour and real-time data
Auto-hedgingTradingCross-asset class rule-driven autohedger based on position and real-time market data (greeks, delta, vega) for single trades or accrued positions.
Participation Volume (PoV)ExecutionTo execute a given percentage of visible liquidity in the market (for instance no more than 30%) in order to limit market impact
Pegged OrderTradingAn order to the bid or ask with, or without an offset. The display quantity will float with the bid or ask, up to the ultimate limit price of the order.
Pegged Order - with priceTradingAn enhanced pegged order that pegs to the BBO using an offset (in ticks or price) as defined by the users. Additional conditions such as limit price, min/max quantity or a-would-price (which for buy and Above which for sell) are available to hunt for liquidity
Random Distribution IcebergExecutionA slicing algorithm which randomly sends child orders onto the market, so it is not initially being recognised as a child order
SnipingTradingTakes a set of predefined triggers such as the bid/offer trigger price and quantity/child order slice to hunt for liquidity
Statistical Adaptive Liquidity SeekingLiquidity seekingA liquidity seeking algorithm which integrates real-time / near-time statistical analysis to enrich the adaptive decision making process
Synthetic OCOTradingCancels an order when another one is fully filled
Synthetic OTOTradingTriggers an order when another order is fully filled
Synthetic StopTradingA limit sell order for a given instrument which is managed by the system and triggered by falling price
Synthetic Take ProfitTradingA limit sell order for a given instrument which is managed by the system and triggered by raising the price
Synthetic time-in-forceTradingA Good-Till-Date (GTD) or Good Till-Cancel (GTC) order type which is held away from the market and able to execute on a range of venues meeting the trade criteria


Instead of dedicated or overloaded fields in the Schema, use:


847TargetStrategyThe target strategy of the order
Component(-)StrategyParametersGrpStrategy parameter block
Repeating Group 957NoStrategyParametersIndicates number of strategy parameters
958StrategyParameterNameName of parameter
959StrategyParameterTypeDatatype of the parameter.
960StrategyParameterValueValue of the parameter
end Repeating Group



OrdStatus vs ExecType


OrdStatusExecTypeDescription
PendingNewPendingNewVenue acknowledgement of receipt of Order.
NewNewVenue notification of acceptance of Order by it's matching engine.
ReplacedVenue notification of acceptance of a replacement Order by it's matching engine.
PartiallyFilledPendingMatchVenue notification of a potential match. E.g. EBS and Reuters MAPI.
TradeVenue notification of a done trade.
FilledPendingMatchVenue notification of a potential match. E.g. EBS and Reuters MAPI.
TradeVenue notification of a done trade.
PendingCancelPendingCancelVenue acknowledgement of receipt of OrderCancelRequest.
CanceledCanceled

Venue notification of Order cancellation.

CanceledLastLook-
PendingReplacePendingReplaceVenue acknowledgement of receipt of OrderCancelReplaceRequest.
RejectedRejected-
CalculatedCalculatedVenue notification of a Drop-copy STP trade.
ExpiredExpiredVenue notification of the expiry of a Limit Order.
ErrorError-



  • No labels