You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dummy data generation is currently deterministic in one sense as we used a fixed PRNG seed. However, when we generate dates we do so as offsets from today's date which means that, while the pattern of dates we generate is deterministic, the actual dates produced change every day:
# TODO: I dislike using today's date as part of the data generation because it
# makes the results non-deterministic. However until we're able to infer a
# suitable time range by inspecting the query, this will have to do.
self.today=todayiftodayisnotNoneelsedate.today()
Ideally, we'd inspect all the various date filters used in a given dataset definition and then, based on that, come up with a suitable date range for generating dummy events.
The text was updated successfully, but these errors were encountered:
Dummy data generation is currently deterministic in one sense as we used a fixed PRNG seed. However, when we generate dates we do so as offsets from today's date which means that, while the pattern of dates we generate is deterministic, the actual dates produced change every day:
ehrql/ehrql/dummy_data/generator.py
Lines 182 to 194 in f5b0d5f
This was done as the quickest way of generating "reasonable" looking dates but we've always known its inadequate:
ehrql/ehrql/dummy_data/generator.py
Lines 42 to 45 in f5b0d5f
Ideally, we'd inspect all the various date filters used in a given dataset definition and then, based on that, come up with a suitable date range for generating dummy events.
The text was updated successfully, but these errors were encountered: