{TDAvec} will be the workhorse for most if not all vectorizations in the first release of {tdarec}. The strict conventions of {TDAvec} should allow the automatic writing of R/step-vpd-*.R files based on information extracted from TDAvec::compute*() names and documentation. This will ensure that {tdarec} can be easily updated with new {TDAvec} vectorizations or new (but still standard) arguments in existing vectorizations.
See the layer-building script in {ordr} for a (not necessarily optimal) example of how this can be done.
{TDAvec} will be the workhorse for most if not all vectorizations in the first release of {tdarec}. The strict conventions of {TDAvec} should allow the automatic writing of
R/step-vpd-*.Rfiles based on information extracted fromTDAvec::compute*()names and documentation. This will ensure that {tdarec} can be easily updated with new {TDAvec} vectorizations or new (but still standard) arguments in existing vectorizations.See the layer-building script in {ordr} for a (not necessarily optimal) example of how this can be done.