Re: [R-pkg-devel] trying to understand an error

2018-06-05 Thread Steven Scott
Thanks Uwe. Will do. On Tue, Jun 5, 2018 at 1:55 PM, Uwe Ligges wrote: > Please ask the Mac maintainer, Simon Urbanek, in such a case where it is > not obvious what is going on. > > Best, > Uwe Ligges > > > > > > On 05.06.2018 18:45, Steven Scott wrote: > >> If there's anyone willing to take

Re: [Rd] Byte-compilation failure on different architectures / low-memory systems

2018-06-05 Thread Dirk Eddelbuettel
On 4 June 2018 at 20:06, Tomas Kalibera wrote: | thanks for the report. Access to the test system is not necessary, the | memory requirements of the byte-code compiler are usually | platform-independent and specifically with this package I can reproduce | they are very high. We'll have a look

[Rd] histoRicalg -- project to document older methods used by R and transfer knowledge

2018-06-05 Thread J C Nash
After some thought, I decided r-devel was probably the best of the R lists for this item. Do feel free to share, as the purpose is to improve documentation and identify potential issues. John Nash The R Consortium has awarded some modest funding for "histoRicalg", a project to document and

Re: [R-pkg-devel] trying to understand an error

2018-06-05 Thread Steven Scott
If there's anyone willing to take a look at the build errors I would appreciate it. I'm trying to work a bug report from a downstream user, and I think the OSX build has an issue that I don't understand. Thanks. On Thu, May 31, 2018 at 1:49 PM, Steven Scott wrote: > Looking at the Boom package

Re: [Bioc-devel] Reverting to older version

2018-06-05 Thread Turaga, Nitesh
Hi Samsiddhi, Yes, you can do that. Make sure to bump the version even in the RELEASE_3_7 branch if you decide to take that option. Best, Nitesh P.S: I’m moving this thread to bioc-devel because it’s useful to the community. > On Jun 5, 2018, at 11:59 AM, Samsiddhi Bhattacharjee wrote:

Re: [Bioc-devel] "Reviving" an existing workflow

2018-06-05 Thread Shepherd, Lori
Excellent news! The RAM requirement was a legacy from the old builders and we have since improved the capabilities so you should be alright with the package as is. I will look at updating the documentation on the website and thank you for bringing it to our attention. We look forward to

Re: [Rd] encoding argument of source() in 3.5.0

2018-06-05 Thread Tomas Kalibera
Thanks for the report, fixed in R-devel (74848). Best Tomas On 06/04/2018 02:41 PM, NELSON, Michael wrote: On R 3.5.0 (Mac) The issue appears when using the default (libcurl) method and specifying the encoding Note that using method='internal' causes a segfault if used in conjunction with

Re: [Bioc-devel] "Reviving" an existing workflow

2018-06-05 Thread Bernd Klaus
Hello Lori, following up on this, we have now finished the  revision of the workflow and are ready to submit it to Bioc: https://github.com/Steffireise/maEndToEnd However, using a call to gc() at end of the  workflow and rendering it via rmarkdown::render  gives a memory usage of ~ 4.5 GB,