Re: [R-pkg-devel] MAP-DP Clustering Algorithm package
A complete sentence ends in a period. On Tue, Jul 11, 2017 at 4:19 AM, Thorsten Wagner wrote: > Hi, > > I’ve implemented the MAP-DP clustering algorithm in R following MatLab > scripts of this paper: > http://journals.plos.org/plosone/article/citation?id=10.1371/journal.pone.0162259 > > Here is the repository: > https://github.com/thorstenwagner/R-ClustMAPDP > > I would like to add the package to CRAN but something seems to be wrong with > my description file: > "Malformed Description field: should contain one or more complete sentences.” > > I would be happy if someone could tell me the reason. > > Best, > Thorsten > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee http://www.functionaldiversity.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] How to write example results to a tempdir()?
Don't change the working directory! That has all kinds of unpleasant
side effects for the unsuspecting user, possibly even more so than
writing to a file.
Instead, write the file to the temp directory, and read it from there, with e.g.
wd <- tempdir()
write(dat, file.path(wd, 'Ttest_1981-2000.dat'))
Using file.path() means that the appropriate path delimiter for that
OS will be used.
Sarah
On Wed, Apr 25, 2018 at 12:30 PM, Jose A Guijarro wrote:
> Dear all,
>
> I am struggling to update my package climatol from version 3.0 to 3.1.
> The old version had all examples under a "dontrun" section because they
> needed files created by other examples that the user had to run first.
>
> As this is not acceptable anymore, I made the examples runnable and
> prepared small ad-hoc datasets, but then writing files to the user space
> is against the CRAN policy rules, and I was suggested to run them on a
> temporal directory. Therefore I changed all my examples to read/write
> files to a tempdir(), as in:
>
> \examples{
> #Set a temporal working directory and write input files:
> wd <- tempdir()
> setwd(wd)
> data(Ttest) #(This loads matrix 'dat' and data.frame 'est.c')
> write(dat,'Ttest_1981-2000.dat')
> write.table(est.c,'Ttest_1981-2000.est',row.names=FALSE,col.names=FALSE)
> rm(dat,est.c) #remove loaded data from memory space
> #Now run the example:
> dd2m('Ttest',1981,2000)
> #Input and output files can be found in directory:
> print(wd)
> }
>
> But now CRAN checks return this warning ten times (one for every example
> in the package):
>
> Warning: working directory was changed to ‘/tmp/RtmpWSRK2F’, resetting
>
> Any hint on how to solve the problem will be highly appreciated...
>
> Jose
>
--
Sarah Goslee
http://www.functionaldiversity.org
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] R package submission: does not pass the incoming checks automatically,
It's normal and expected, and nothing to worry about. It's a NOTE to ensure that the package comes from the designated maintainer. See for instance: https://stackoverflow.com/questions/23829978/checking-cran-incoming-feasibility-note-maintainer Sarah On Mon, Oct 1, 2018 at 8:45 AM Müller, Bernd wrote: > Dear Sir or Madam, > > On Friday, I submitted my packae epos_0.1.0 via the web submission system > https://cran.r-project.org/submit.html without any further errors, > warnings, and notes except this one: > > * checking CRAN incoming feasibility ... NOTE > Maintainer: ‘Bernd Mueller ’ > > I don't know how to resolve this note. Previously I used the German > special charater "ü" in my name. Then, I tried again with "ue" instead of > "ü". But somehow, I am stucked at this point becaause I don't know how to > proceed any further. The log files can be found here: > > > https://win-builder.r-project.org/incoming_pretest/epos_0.1.0_20180928_204638/Windows/00check.log > > and here: > > > https://win-builder.r-project.org/incoming_pretest/epos_0.1.0_20180928_204638/Debian/00check.log > > Please assist me in this case about my R-package submission. > > Kind regards, > > Bernd Müller > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] pdflatex is not available
It sounds like you're on a Mac? Then you need to install MacTeX, http://www.tug.org/mactex/ to get pdflatex. Sarah On Fri, Dec 13, 2019 at 7:11 PM Cathy Lee Gierke wrote: > Does anyone know why I might get this error? > > Hmm ... looks like a package > > Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : > > pdflatex is not available > > Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : > > * pdflatex is not available* > > *Error in running tools::texi2pdf()* > > You may want to clean up by 'rm -Rf > > /var/folders/0m/41bxx35j5x9f_tks7zrd7jh0gn/T//Rtmpuv00M5/Rd2pdf8f2a123193cb' > > * checking for detritus in the temp directory ... OK > > * DONE > > > > There are no clues in the Rdlatex.log > I have attached the ...manual.tex file. Is there a way to check it for > non-ascii or non-printing characters on a Mac? I have had that problem > before, but I'm not finding any now. Maybe I have the wrong command? > > > find /Users/user/CATkit/CATkit/man | perl -ne 'print if /[^[:ascii:]]/' > > find /Users/user/CATkit/CATkit/man/CatCall.rd | perl -ne 'print if > /[^[:ascii:]]/' > > > Should there be a pdf file somewhere? > > Thanks, > Cathy Lee Gierke > > > <http://www.goodreads.com/author/show/23924.Martin_Luther_King_Jr_> > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > -- Sarah Goslee (she/her) http://www.sarahgoslee.com [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Unable to post messages to this group
Clearly you can post messages to this group, since this message was received. R-package-devel requires that the first time someone posts, their message is approved by a human. After that first post, they may post normally. It's not a problem, or anything you've done - this policy applies to everyone, and cuts down enormously on spam since the moderators only approve relevant posts. Since your post appeared here, you've been cleared. The policy is on the about page where you signed up: https://stat.ethz.ch/mailman/listinfo/r-package-devel You have to be a subscriber to the list in order to post any message. Even then, your first messages are only posted after one manual moderator approvement. The moderation team are all volunteers, and sometimes they are busy or away from the computer, especially on weekends. Sarah On Mon, Jul 13, 2020 at 5:28 AM Binit Kumar wrote: > > Hi Team, > I am unable to post messages to this group and keep getting "waiting for > moderator" message from bounce email i.e. "R-package-devel > ". > Is there any criteria of sending the message to devel group? > > > Thanks & Regards, > > Binit Kumar > -- Sarah Goslee (she/her) http://www.numberwright.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] how to add .Rd in man folder for inst/ext file?
Hi, Well, at the most basic, you create an appropriately-named and formatted text file in the man directory. The Writing R Extensions manual is full of information: https://cran.r-project.org/doc/manuals/R-exts.html Roxygen is an alternative approach to creating the Rd files yourself. https://cran.r-project.org/web/packages/roxygen2/vignettes/roxygen2.html The package.skeleton() function is a helper for the do it yourself approach. Sarah On Mon, Dec 19, 2022 at 9:17 AM Sanjeev Sariya wrote: > > Hi devel team, > > I have recently added one file in the inst/extdata folder. > > I'd like to add details about it in the man folder by creating a .Rd file > for the respective file. > > I created .Rd files for other datasets long time back, however, I do not > remember the steps now. Their skeleton looks like the attached file. > > I am using conda environment (not R studios) > Kindly guide me further. > best > > -- > Sanjeev M > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.sarahgoslee.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] (no subject)
Hi, The Writing R Packages manual is the main documentation, specifically: https://cran.r-project.org/doc/manuals/R-exts.html#The-DESCRIPTION-file As for indentation, don't. Just use a newline. I don't know of any templates, but the source code for many/most packages is on RForge and/or github, so you can look at as many DESCRIPTION files as you'd like to find the solutions you need. If that doesn't help, then please share actual examples of what isn't working in your file. Sarah On Mon, Apr 17, 2023 at 8:15 PM Socorro Dominguez wrote: > > Hello! > > I need some help. > > Could you explain how to write the *Description* field in the *Description* > file when we need to add links? I don't find any rules on how to write it > when it includes links such as > > Also, whenever I try to do a new line in the *Description* field with the > four spaces for indentation, I get an error from the R CMD > > If you could provide me with some sort of template example, I would be > extremely grateful. > > Best, > > Socorro > > -- > Best regards, > > Socorro E. Dominguez-Vidaña > s.doming...@ht-data.com > > [[alternative HTML version deleted]] > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.numberwright.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] What to do when a package is archived from CRAN
Hi, You can generally see what the reason is from the archive page, where it says: A summary of the most recent check results can be obtained from the check results archive. On that page, https://cran-archive.r-project.org/web/checks/2023/2023-08-19_check_results_prqlr.html is the note: Version: 0.5.0 Check: installed package size Result: NOTE installed size is 18.5Mb sub-directories of 1Mb or more: libs 18.2Mb This is too big for CRAN, see https://cran.r-project.org/web/packages/policies.html quoted here: Packages should be of the minimum necessary size. Reasonable compression should be used for data (not just .rda files) and PDF documentation: CRAN will if necessary pass the latter through qpdf. As a general rule, neither data nor documentation should exceed 5MB (which covers several books). A CRAN package is not an appropriate way to distribute course notes, and authors will be asked to trim their documentation to a maximum of 5MB. Where a large amount of data is required (even after compression), consideration should be given to a separate data-only package which can be updated only rarely (since older versions of packages are archived in perpetuity). Similar considerations apply to other forms of “data”, e.g., .jar files. Source package tarballs should if possible not exceed 10MB. It is much preferred that third-party source software should be included within the package (as e.g. a vendor.tar.xz file) than be downloaded at installation: if this requires a larger tarball a modestly increased limit can be requested at submission. Sarah On Sat, Aug 26, 2023 at 4:26 PM SHIMA Tatsuya wrote: > > Hi, > > I noticed that my submitted package `prqlr` 0.5.0 was archived from CRAN > on 2023-08-19. > <https://CRAN.R-project.org/package=prqlr> > > I submitted prqlr 0.5.0 on 2023-08-13. I believe I have since only > received word from CRAN that it passed the automated release process. > <https://github.com/eitsupi/prqlr/pull/161> > So I was very surprised to find out after I returned from my trip that > this was archived. > > The CRAN page says "Archived on 2023-08-19 for policy violation. " but I > don't know what exactly was the problem. > I have no idea what more to fix as I believe I have solved all the > problems when I submitted 0.5.0. > > Is there any way to know what exactly was the problem? > (I thought I sent an e-mail to CRAN 5 days ago but have not yet received > an answer, so I decided to ask my question on this mailing list, > thinking that there is a possibility that there will be no answer to my > e-mail, although I may have to wait a few weeks for an answer. My > apologies if this idea is incorrect.) > > Best, > Tatsuya > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.sarahgoslee.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
