population as a mandatory column is unclear

[abhishek-ch]

A necessity of population named column is not logical for every usecase, make it data driven

[sprivite]

Can you give me a use case in which population is not needed?

[abhishek-ch]

If I create dummy dataset for impact of lifestyle choices like Smoking, Exercise, Blood pressure level etc, the target column seems to be Treatment or Is_Patient etc, I couldn't related population column for such scenario

Dataset Sample

[sprivite]

You're saying you want a different name for the column?

[abhishek-ch]

Will it be possible/logical to make any column Populations, I can always make sure to have a column name called population but not sure abt the value

[sprivite]

Does this solve your issue?

https://bayer-group.github.io/pybalance/03_api.html#pybalance.utils.MatchingData

Note that init can take population_col as an argument.