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
This function will probably act as sewing function, that sews all the initially created functions and run a full Pathway synthesis, for a given database and event cohorts.
The text was updated successfully, but these errors were encountered:
@TheCedarPrince This function is supposed to do a sewing job to all the functions, For which this is the chain of functions execution, I am imagining as of now : period_prior_to_index ---> calculate_era_duration ---> minPostCombinationDuration_filter ---> create_treatment_history --->EraCollapse ---> combination_Window .
Do let me know what are your thoughts and recommendations for the same !
Hey @Jay-sanjay , this sounds entirely reasonable to me. Can you try drafting a PR for this, testing it out and showing me the results, and then I can review? I think the approach makes sense but I would want to see it in action to add more comments/thoughts. Some other questions:
What do you envision as the API?
Should we enable logging or information of some kind?
It may be nice to have the ability to pull out intermediate pieces from the processesing (i.e. pull out the durations, histories, etc.) so folks can audit each part of the execution.
This function will probably act as sewing function, that sews all the initially created functions and run a full Pathway synthesis, for a given database and event cohorts.
The text was updated successfully, but these errors were encountered: