Closed benthestatistician closed 3 years ago
Closing because:
.[
methods for ISMs, one could address the problem in the example by subsetting mo1
, down to observations found in nuke.nopt
, before passing it to match_on()
through the within=
argument.
In some workflows one ISM ("aISM", say) might be built in the process of whittling down the sample toward a subsample that will be used for fitting an index score (eg propensity score) model, which will in turn be used to create another ISM ("bISM") for matching. (See statement of #142 for a bit more description.) In this context it would be helpful if when
ismOpHandler
saw ISMs e1 and e2 of different dimension, rather than quitting it just got rid of the rows and columns not common to both ISMs. Or something along those lines. As opposed to this:(Speaking of #142, addressing this seems likely to require addressing it also.)