From v4.2alfam2() could be run without TAN applicationrate, but this did not work when theconf.int argument wasused. That problem was fixed.
Minor change to description in DESCRIPTION and correction of year formost recent paper (2025).
The latest default parameter set was revised slightly to reflect newresults after making corrections to the parameter estimation procedure.Resulting predictions will be slightly different than in v4.1.11 andearlier. In some cases the change may be around 1% of applied TAN, butis typically smaller.
Thealfam2() function can now be run without a columnfor TAN applcation rate (app.name argument). If omitted (orif default argument name is not present) only relative emission will bereturned with a warning.
Available default parameter sets are now documented in a separatehelp file. View it with?alfam2pars or?alfam2pars03 etc.
A new paper describing recent developments in the package has beenpublished and is now listed in the help files and vignette.
alfam2() function now checks that allpass.col are in thedat data frame (see issue#92).
Fix a phantom incorporation effect on the r3 parameter that couldshow up with inconsistent user inputs (see issue#87).
A NEWS.md file (this file) has been added.
conf.int in thealfam2() functionno longer returns incorrect message about user-defined parametersconf.int = 'all' thealfam2()function will now return a parameter set index column in the output,which is convenient for further processing (e.g., for relativeeffects)alfam2() help (documentation) file, where additionaldetails were addedpurl=FALSE (thanks toBenBolker andIvanKrylov)First version on CRAN. For differences from earlier versions see thenotes given with previousreleases.