Dear Soren, I hope this message finds you well!
I believe there is a minor issue (I will not call it a bug since it does not prevent functionality) in the LSmeans function. When we assign the LSmeans function to an object, the following output is automatically printed to the console:
## List of 2
## $ new.fact.lev:List of 1
## ..$ A: chr [1:3] "1" "2" "3"
## $ grid.data :'data.frame': 3 obs. of 1 variable:
## ..$ A: chr [1:3] "1" "2" "3"
Obviously, printing an object should be done explicitly via print or implicitly by repeating the object’s name. It is likely that there is still a return, print, or something similar left in the internal programming of the LSmeans function. In automated reports with Sweave or knitr, this causes a problem. Since our packages (TukeyC and ScottKnott) depend on yours, I am using this channel to report this occurrence. In the package documentation itself (see the link: https://cran.r-project.org/web/packages/doBy/vignettes/linest_lsmeans.pdf) the mentioned output appears. Thank you for your attention, and have an excellent day.
Best regards,
Dear Soren, I hope this message finds you well!
I believe there is a minor issue (I will not call it a bug since it does not prevent functionality) in the
LSmeansfunction. When we assign theLSmeansfunction to an object, the following output is automatically printed to the console:Obviously, printing an object should be done explicitly via
printor implicitly by repeating the object’s name. It is likely that there is still areturn,print, or something similar left in the internal programming of theLSmeansfunction. In automated reports withSweaveorknitr, this causes a problem. Since our packages (TukeyC and ScottKnott) depend on yours, I am using this channel to report this occurrence. In the package documentation itself (see the link: https://cran.r-project.org/web/packages/doBy/vignettes/linest_lsmeans.pdf) the mentioned output appears. Thank you for your attention, and have an excellent day.Best regards,