MétaCan
Menu
Back to cohort
Record W3095988102 · doi:10.1142/s2010139220500159

Do Algorithmic Traders Improve Liquidity When Information Asymmetry is High?

2020· article· en· W3095988102 on OpenAlex
Archana Jain, Chinmay Jain, Revansiddha Basavaraj Khanapure

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueQuarterly Journal of Finance · 2020
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicFinancial Markets and Investment Strategies
Canadian institutionsOntario Tech University
Fundersnot available
KeywordsMarket liquidityInformation asymmetryEarningsEquity (law)Algorithmic tradingHigh-frequency tradingBusinessMonetary economicsFinancial economicsProxy (statistics)Order (exchange)Liquidity crisisEconomicsFinanceComputer science

Abstract

fetched live from OpenAlex

Hendershott et al. (2011, Does Algorithmic Trading Improve Liquidity? Journal of Finance 66, 1–33) show that algorithmic traders improve liquidity in equity markets. An equally important and unanswered question is whether they improve liquidity when information asymmetry is high. We use days surrounding earnings announcement as a period of high information asymmetry. First, we follow Hendershott et al. (2011, Does Algorithmic Trading Improve Liquidity? Journal of Finance 66, 1–33) to use introduction of NYSE autoquote as a natural experiment. We find that increased algorithmic trading (AT) as a result of NYSE autoquote does not improve liquidity around earnings announcements. Next, we use trade-to-order volume % and cancel rate as a proxy for algorithmic trading and find that abnormal spreads surrounding the days of earnings announcement are significantly higher for stocks with higher AT. Our findings indicate that algorithmic traders reduces their role of liquidity provision in markets when information asymmetry is high. These findings shed further light on the role of liquidity provision by algorithmic traders in the financial markets.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.453
Threshold uncertainty score0.815

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.021
GPT teacher head0.199
Teacher spread0.178 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it