Diagnosing Empty Data After Dropping Missing Values

Summary

The post describes a feature-data issue in a quantitative research workflow. A request failed with an error indicating that no observations remained after missing values were removed. Changing the feature lookback period, as suggested by common troubleshooting guidance, did not fix it, so the author reduced the feature set until isolating the cause.

The identified feature, a ranked average money-flow net amount measure, returned only missing values for dates before 2018, while later data worked. The post reports this as a suspected data or platform bug, but offers no confirmed cause, repair, or independent verification. It is a useful debugging example: isolate inputs to find a feature whose missing history can empty the sample, then check the feature’s coverage over the requested date range. The observation is specific to one feature and platform context, so it does not establish a general behavior.

Key ideas

• Reducing the feature set helped isolate the input causing the empty-after-dropna error.
• The identified money-flow feature had missing values before 2018.
• Changing the lookback period did not resolve the reported issue.
• The author suspected a bug but did not confirm its cause or describe a fix.

Tags

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