Closed smjenness closed 3 years ago
@smjenness for this would this supercede or compliment part.X.window
parameter (part.X.window
would at minimum be dependent on truncate.plist
)?
EDIT: I believe the two parameters should work as such:
truncate.plist = X < Inf
then there should be a check within param_msm
to ensure that part.X.window <= truncate.plist
for all input identification timings.truncate.plist = Inf
then part.X.window
controls subsetting of eligible partnerships.Yes, there is a logical relation between these parameters, but you do not need to impose a restriction on the truncate.plist parameter in the code (this truncate.plist functionality may be used outside of the partner notification model we are building right now). So truncate.plist
would neither supersede nor compliment (in the specific way that you have described above) part.X.window
. Please verify this makes sense here, and then implement it.
Yes that makes sense; the above would have been too restrictive. And thinking on it it isn't needed as a part.X.window
greater than truncate.plist
would just be default pulling everyone which is fine. Apologies for confusion.
Closed with EpiModel/EpiModelHIV-p#38
Instead of TRUE/FALSE, it would retain all partnerships that have stopped within X number of time steps. For example, if X was 12, then we would keep all active partnerships and those that have ended within the past 12 time steps. This will improve model efficiency.