lverweijen/piargus

Python wrapper for TauArgus

piargus's Issues

Safety rules definition

Currently safety rules can be defined on three classes:

• InputData
• Table
• Job

For simplification, it's probably better to only define them on tables and remove the other two ways.

This also solves the following problems:

• Less code duplication
• TableData inherits from both inputdata and table and inherits safety_rules twice. This works in practice because both definitions are equivalent.
• We need a way to define safety rules on holdings. Simplifying safety rules will probably make it easier to extend them to holdings.

It's a little less convenient when all tables need to use the same safety_rules. However, I found that I often want to make a freq table anyway, which doesn't support safety_rules, so in those cases I end up refactoring to have safety_rules per table anyway.