Thanks for adding @FabianHofmann ! You are right, it's also cleaner to add a dedicated method for it.

I would just further move it around. We now have c.filter_active, c.get_active_assets and c.get_activity_mask, which is quite confusing. We can probably deprecatec.get_activity_mask and move it to using c.da.active instead. But c.filter_active and c.get_active_assets are very similar, and if you don't pass data which isn't clean method functionality anyway, you would retrieve the nearly same results (index vs sliced df). What about just renaming to filter_by_active_assets next to get_active_assets and maybe removing the default self.static for data? Alternatively, we could also fully move it to to a helper in common.py a la filter_by_active_assets(c, your_df).

sure thing! you are right about the three parallel methods (forgot about get_activity_mask).

What about just renaming to filter_by_active_assets next to get_active_assets and maybe removing the default self.static for data?

I like that, will do that