Resolving a Missing Position Column in a BigQuant Backtest

Summary

This forum exchange addresses a BigQuant error reporting a missing “position” field. The response describes two changes: set the input mode of the feature-input module to SQL, and revise the weight variable used in the backtest function of the trading engine. These steps are offered as a debugging direction for a workflow where the position field is absent from a table.

The post points to shared code and says a resulting backtest curve is available, but it includes no code details, error trace, dataset schema, or performance figures in the text itself. The suggested changes are therefore difficult to assess or reproduce from this document alone, and the claimed curve does not establish strategy quality. The advice may depend on the original pipeline’s modules and variable definitions.

Key ideas

• The reported BigQuant issue is a missing position field in a table.
• The response recommends changing the feature-input module’s mode to SQL.
• It also recommends revising the weight variable in the trading engine’s backtest function.
• The post omits the underlying code and error context, limiting reproducibility.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.