Closed npatki closed 1 year ago
Although this is not ideal, the workaround for now would be to drop any rows where either of the low or high columns are missing
# replace with the name of your datetime columns
training_data = real_data.dropna(subset=['datetime_low', 'datetime_high'])
model.fit(training_data)
This issue should be fixed in an upcoming release of the SDV.
Environment Details
Error Description
If there are 2 datetime columns involved in an
Inequality
constraint and those columns contain missing data, then the software crashes before I can get any synthetic data. Exactly where and how it crashes is dependent on the method I use to supply the constraint.Expected Behavior: Datetime columns in an
Inequality
constraint should behave the same as numerical columns. That is: The inequality comparison only happens when both values are non-missing. Otherwise, we can ignore the comparison and just proceed with modeling.Steps to reproduce
METHOD 1: Using an
Inequality
constraint object. We can do this when the columns are represented as datetime dtypes.Output:
METHOD 2: Inputting the constraint into the metadata itself. This is required when the datetime are represented as strings.
Output