Re: [Rd] How to efficiently share data (a dataframe) between R and Java
Thank you for the example. Based on my recent experiments, this solution
is the most efficient.
Cheers,
Jaroslav
On 2015-12-15 23:15, Simon Urbanek wrote:
> You can pass the entire df, example:
>
>> data(iris)
>> iris$sp = as.character(iris$Species)
>> o=.jarray(lapply(iris, .jarray))
>> .jcall("C",,"df",o)
> df, 6 variables
> [0]: double[150]
> [1]: double[150]
> [2]: double[150]
> [3]: double[150]
> [4]: int[150]
> [5]: String[150]
>
>
> Java code:
>
> public class C {
>static void df(Object df[]) {
> int n;
> System.out.println("df, " + (n = df.length) + "
> variables");
> int i = 0;
> while (i < n) {
> if (df[i] instanceof double[]) {
> double d[] = (double[]) df[i];
> System.out.println("["+i+"]: double["+d.length+"]");
> } else if (df[i] instanceof int[]) {
> int d[] = (int[]) df[i];
> System.out.println("["+i+"]: int["+d.length+"]");
> } else if (df[i] instanceof String[]) {
> String s[] = (String[]) df[i];
> System.out.println("["+i+"]: String["+s.length+"]");
> } else {
> System.out.println("["+i+"]: some other type...");
> }
> i++;
> }
> }
> }
>
> Normally, you wouldn't pass the entire df but instead have methods for
> the types you care about as the modeling function - that's more
> Java-like approach, but either is valid and there is no difference in
> efficiency.
>
> Cheers,
> Simon
>
>
>
>> On Dec 15, 2015, at 12:50 PM, Ing. Jaroslav Kuchař
>> wrote:
>>
>> Dear all,
>>
>> thank you for your hints. I would prefer to do not use Rserve as Dirk
>> mentioned.
>>
>> @Simon
>> I have full control over the Java implementation - I can adapt the code
>> that I use for the communication R <-> Java.
>>
>>> You can natively access structures on each side. The fastest way is to
>>> use R representation (column-oriented) in Java - that is much faster
>>> than any kind of serialization or anything you mention above since you
>>> pass the variables as a whole.
>>
>> Could you please send any reference to more examples or documentation
>> that can help me?
>> The main goal is to copy a full dataframe from R to Java.
>>
>> Best regards,
>> Jaroslav
>>
>> On 2015-12-07 03:19, Simon Urbanek wrote:
>>> On Dec 6, 2015, at 12:36 PM, Ing. Jaroslav Kuchař
>>> wrote:
>>>
Dear all,
in our ongoing project we use Java implementations of several
algorithms. We also provide a “wrapper” implemented as an R package
using rJava (https://github.com/jaroslav-kuchar/rCBA). Based on our
recent experiments, the significant portion of time is spent on copying
a dataframe from R to Java. The Java implementation needs access to the
source dataframe.
I have tested several approaches: calling Java method row-by-row;
serialize the whole data-frame to a temp file and parsing in Java; or
row binding to a single vector and calling a single Java method. Each
approach has its limitations e.g. time-consuming row-by-row copying,
serialization and parsing performance or memory limitations of a single
vector.
Is there an efficient approach how to copy a dataframe from R to Java
and another one from Java to R?
Thanks for any help you can provide...
>>>
>>> You can natively access structures on each side. The fastest way is to
>>> use R representation (column-oriented) in Java - that is much faster
>>> than any kind of serialization or anything you mention above since you
>>> pass the variables as a whole.
>>>
>>> Typically, the bottleneck are Java applications which may require very
>>> inefficient data structures. If you have control over the algorithms,
>>> you can simply use proper data structures and avoid that problem. If
>>> you don't have control, you'll have to add Java code that converts to
>>> whatever structure is needed by the Java code form the data frame
>>> pushed to the Java side. The main point here is that you do NOT want
>>> to do any conversion on the R side.
>>>
>>> Cheers,
>>> Šimon
>>
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Building R in 64-bit mode
On 2015-12-16 16:02, Michael Felt wrote:
tools:::sysdata2LazyLoadDB("/data/prj/cran/R-3.2.3/src/library/tools/R/sysdata.rda","../../../library/tools/R")
Error: Line starting 'Package: tools ...' is malformed!
> warnings()
Warning messages:
1: package "methods" in options("defaultPackages") was not found
2: package 'datasets' in options("defaultPackages") was not found
3: package 'utils' in options("defaultPackages") was not found
4: package 'grDevices' in options("defaultPackages") was not found
5: package 'graphics' in options("defaultPackages") was not found
6: package 'stats' in options("defaultPackages") was not found
7: package 'methods' in options("defaultPackages") was not found
8: Setting LC_CTYPE failed, using "C"
9: Setting LC_COLLATE failed, using "C"
10: Setting LC_TIME failed, using "C"
11: Setting LC_MESSAGES failed, using "C"
12: Setting LC_MONETARY failed, using "C"
> q()
I guess I would like a suggestion on how to expand/create debug
messages. This is being started --vanallia --clone.
Also, I am wondering the Duplicate Symbols are 'harmless' in 32-bit
mode, but causing confusion in the 64-bit mode.
Other suggestions? Ideas?
Thanks,
Michael
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Question about bug reporting, and the followup process
On 2015-12-16 16:40, Duncan Murdoch wrote: We generally ignore it, so your current practice is fine. The problem is that none of the core developers use AIX, so it's unlikely anyone will be able to test and fix your problems. You'll need to find an AIX expert, or fix them yourself. Duncan Murdoch I have answered this twice, but still do not see it. A) I am an AIX expert, not an R expert. I am willing to assist, longish-term for matters re: R on AIX. B) If I fix something (e.g., the suggestions in the bug-reports, in particular for configure.ac related "stuff" - how do I submit a patch? (Did not find anything suitable in R-forge.) C) Bug 16633 - https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16633 is all platforms, not just AIX. And I am not attempting to fix it on my own, because there is an architectural element involved (namely, does the library, or libR own the symbol. Thanks, Michael p.s. Duncan, maybe my previous replies were to you only - my mistake and please forgive the double emails. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Question about bug reporting, and the followup process
On 16/12/2015 12:31 AM, Michael Felt wrote: Hi, I sent in three bug-reports (maybe should have been 4, because the second contains an "enhancement" as well as well as a bug). I do not set "Importance", ever - or, is that the custom here? We generally ignore it, so your current practice is fine. The problem is that none of the core developers use AIX, so it's unlikely anyone will be able to test and fix your problems. You'll need to find an AIX expert, or fix them yourself. Duncan Murdoch Regards, Michael p.s. - maybe related - is it best practice to add [Rd] in the subject line, or is there a program doing that instead? __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Mystifying SEGFAULT on 3.2.3 but not 3.2.2
Gert,
On 16 December 2015 at 12:06, Gert van Valkenhoef wrote:
| I recently upgraded to 3.2.3 and am getting mystifying errors with my
| in-development code (available at
| https://github.com/gertvv/gemtc/tree/feature/regression). Every few hundred
| LPs that I solve using the rcdd package will result in a SEGFAULT in the
| garbage collector (address 0x10, cause 'memory not mapped') or an error
| about a list not existing. Downgrading to 3.2.2 works, but *only* after
| completely removing my local R packages and re-installing them. A
I wish I could tell you something more encouraging -- but this _sometimes_
happens with prebuilt R, or prebuilt packages. We try try chase this, and
when we do batch runs of R CMD check over all reverse depends we end up
rebuilding.
I was just bitten by this when upgrading to Ubuntu 15.10 as it brings in
g++-5.2 which has a _known_ ABI transition for C++11/14. About 15% of
packages got 'random' (but repeatable) seg.faults when there were none
before. And that went away with a proper R version also built with a gcc-5.2
toolchain.
So in short: check your toolchain. Things may then go away. If they don't
then there may be a real bug.
| subsequent upgrade to 3.2.3 will again be broken, and even more
| mysteriously it will also break a re-downgrade to 3.2.2 until I again purge
| my local packages and re-install them.
|
| To downgrade I am using (with the CRAN ubuntu mirror enabled):
| sudo apt-get purge r-base-core
| sudo rm -rf ~/R
[ I am mildly opposed to ~/R. I unset R_LIBS_USER in /etc/R/Renviron and just
make sure I am part of the group owning /usr/local/lib/R/site-library. Then
an ordinary users can install there. ]
| sudo apt-get install r-base-core=3.2.2-1trusty0 r-base-dev=3.2.2-1trusty0
| r-recommended=3.2.2-1trusty0
| sudo apt-get install r-cran-rjags
| R -e "install.packages(c('devtools','igraph','meta','truncnorm','rcdd'))"
[ I am very partial to using 'install.r devtools igraph meta truncnorm rcdd'
on the command-line where install.r is a part of r-cran-littler, or littler
now on CRAN, which I link into /usr/local/bin. ]
| The code that produces a SEGFAULT (usually after 5-15 iterations) under
| 3.2.3, but not 3.2.2:
| library(devtools)
| load_all('gemtc')
| for (i in 1:100) { print(i); mtc.model(thrombolytic) }
| (note that the SEGFAULT also happens without devtools)
|
| The sessionInfo() in 3.2.2:
|
| R version 3.2.2 (2015-08-14)
| Platform: x86_64-pc-linux-gnu (64-bit)
| Running under: Ubuntu 14.04.3 LTS
We have a dedicated list for running R on Debian/Ubuntu/... systems:
r-sig-debian. Consider lurking/posting there.
Cheers, Dirk
| locale:
| [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
| [3] LC_TIME=nl_NL.UTF-8LC_COLLATE=en_US.UTF-8
| [5] LC_MONETARY=nl_NL.UTF-8LC_MESSAGES=en_US.UTF-8
| [7] LC_PAPER=nl_NL.UTF-8 LC_NAME=C
| [9] LC_ADDRESS=C LC_TELEPHONE=C
| [11] LC_MEASUREMENT=nl_NL.UTF-8 LC_IDENTIFICATION=C
|
| attached base packages:
| [1] stats graphics grDevices utils datasets methods base
|
| other attached packages:
| [1] gemtc_0.8 coda_0.16-1 lattice_0.20-33 devtools_1.9.1
|
| loaded via a namespace (and not attached):
| [1] Rcpp_0.12.2 roxygen2_5.0.1 rcdd_1.1-9 digest_0.6.8
| [5] truncnorm_1.0-7 grid_3.2.2 plyr_1.8.3 meta_4.3-2
| [9] magrittr_1.5stringi_1.0-1 rjags_4-4 tools_3.2.2
| [13] stringr_1.0.0 igraph_1.0.1memoise_0.2.1
|
| A core dump is here:
|
https://drive.google.com/a/rug.nl/file/d/0BxhVLNPmwLrycTYtOHNxNXZTMEk/view?usp=drive_web
|
| I have tried debugging this but am stumped. Any help would be greatly
| appreciated!
|
| Kind regards,
|
| Gert van Valkenhoef
|
| [[alternative HTML version deleted]]
|
| __
| R-devel@r-project.org mailing list
| https://stat.ethz.ch/mailman/listinfo/r-devel
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Building R in 64-bit mode
I have been looking further and need some help with:
tools:::sysdata2LazyLoadDB("/data/prj/cran/R-3.2.3/src/library/tools/R/sysdata.rda","../../../library/tools/R")
Error: Line starting 'Package: tools ...' is malformed!
Details:
root@x065:[/data/prj/cran/64/R-3.2.3/src/library/tools]export | egrep
"PATH|HOME"
HOME=/
LIBPATH=/data/prj/cran/64/R/lib:/opt/lib
LOCPATH=/usr/lib/nls/loc
NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
PATH=/opt/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/vacpp/bin:
R_HOME=/data/prj/cran/64/R
root@x065:[/data/prj/cran/64/R-3.2.3/src/library/tools]/data/prj/cran/64/R-3.2.3/bin/exec/R
R version 3.2.3 (2015-12-10) -- "Wooden Christmas-Tree"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: powerpc-ibm-aix5.3.7.0 (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
Natural language support but running in an English locale
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
During startup - There were 12 warnings (use warnings() to see them)
>
tools:::sysdata2LazyLoadDB("/data/prj/cran/R-3.2.3/src/library/tools/R/sysdata.rda","../../../library/tools/R")
Error: Line starting 'Package: tools ...' is malformed!
> warnings()
Warning messages:
1: package "methods" in options("defaultPackages") was not found
2: package 'datasets' in options("defaultPackages") was not found
3: package 'utils' in options("defaultPackages") was not found
4: package 'grDevices' in options("defaultPackages") was not found
5: package 'graphics' in options("defaultPackages") was not found
6: package 'stats' in options("defaultPackages") was not found
7: package 'methods' in options("defaultPackages") was not found
8: Setting LC_CTYPE failed, using "C"
9: Setting LC_COLLATE failed, using "C"
10: Setting LC_TIME failed, using "C"
11: Setting LC_MESSAGES failed, using "C"
12: Setting LC_MONETARY failed, using "C"
> q()
Save workspace image? [y/n/c]: n
However, in 32-bit mode I see NULL warnings...
root@x065:[/data/prj/cran/32/R-3.2.3/src/library/tools]/data/prj/cran/32/R-3.2.3/bin/exec/R
R version 3.2.3 (2015-12-10) -- "Wooden Christmas-Tree"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: powerpc-ibm-aix5.3.7.0 (32-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
Natural language support but running in an English locale
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> warnings()
NULL
q()
Ideas?
Thanks,
Michael
On 16-Dec-15 13:03, Michael Felt wrote:
Hope I am not sounding too much like a broken record - as far as
64-bit build on AIX is concerned.
** Short - 32-bit builds complete normally, 64-bit builds stop at
"installing 'sysdata.rda'" with message:
Error: Line starting 'Package: tools ...' is malformed!
Execution halted
*** Longer...
I could file a bug - Importance, showstopper - but I would prefer to
better understand how to dig a bit deeper into why it is failing - and
work with (or for) you to make R easier to install and use on AIX.
As there are at least two ways to find 64-bit shared libraries
(AIX-way; GNU/Linux-way; "Solaris-way .so files"?) I am trying to keep
it simpler and and starting with the recently released R-3.2.3
distribution.
I made the following changes - to clean up many Duplicate Symbol
warnings :happy me!:
diff -ru R-3.2.3.orig/configure R-3.2.3/configure
--- R-3.2.3.orig/configure 2015-12-02 23:16:46 +
+++ R-3.2.3/configure 2015-12-16 10:52:15 +
@@ -26339,11 +26339,11 @@
##ADD: However, for example, symbol in libc of memcpy is
__memmove,__memmove64.
##ADD: This black magic puts lc before lR and pockets this.
if test "x${OBJECT_MODE}" = "x64"; then
- main_ldflags="${wl}-brtl ${wl}-bexpall ${wl}-bpT:0x1
${wl}-bpD:0x11000 -lc"
+ main_ldflags="${wl}-brtl ${wl}-bpT:0x1
${wl}-bpD:0x11000 -lc"
else
- main_ldflags="${wl}-brtl ${wl}-bexpall -lc"
+ main_ldflags="${wl}-brtl ${wl}-bmaxdata:0xd000/dsa -lc"
fi
-shlib_ldflags="${wl}-brtl ${wl}-G ${wl}-bexpall ${wl}-bnoentry -lc"
+shlib_ldflags="${wl}-G ${wl}-bnoentry -lc"
SHLIB_LIBADD="\$(LIBM)"
shlib_cxxldflags="${shlib_ldflags}"
if test "$
[Rd] Building R in 64-bit mode
Hope I am not sounding too much like a broken record - as far as 64-bit
build on AIX is concerned.
** Short - 32-bit builds complete normally, 64-bit builds stop at
"installing 'sysdata.rda'" with message:
Error: Line starting 'Package: tools ...' is malformed!
Execution halted
*** Longer...
I could file a bug - Importance, showstopper - but I would prefer to
better understand how to dig a bit deeper into why it is failing - and
work with (or for) you to make R easier to install and use on AIX.
As there are at least two ways to find 64-bit shared libraries (AIX-way;
GNU/Linux-way; "Solaris-way .so files"?) I am trying to keep it simpler
and and starting with the recently released R-3.2.3 distribution.
I made the following changes - to clean up many Duplicate Symbol
warnings :happy me!:
diff -ru R-3.2.3.orig/configure R-3.2.3/configure
--- R-3.2.3.orig/configure 2015-12-02 23:16:46 +
+++ R-3.2.3/configure 2015-12-16 10:52:15 +
@@ -26339,11 +26339,11 @@
##ADD: However, for example, symbol in libc of memcpy is
__memmove,__memmove64.
##ADD: This black magic puts lc before lR and pockets this.
if test "x${OBJECT_MODE}" = "x64"; then
- main_ldflags="${wl}-brtl ${wl}-bexpall ${wl}-bpT:0x1
${wl}-bpD:0x11000 -lc"
+ main_ldflags="${wl}-brtl ${wl}-bpT:0x1
${wl}-bpD:0x11000 -lc"
else
- main_ldflags="${wl}-brtl ${wl}-bexpall -lc"
+ main_ldflags="${wl}-brtl ${wl}-bmaxdata:0xd000/dsa -lc"
fi
-shlib_ldflags="${wl}-brtl ${wl}-G ${wl}-bexpall ${wl}-bnoentry -lc"
+shlib_ldflags="${wl}-G ${wl}-bnoentry -lc"
SHLIB_LIBADD="\$(LIBM)"
shlib_cxxldflags="${shlib_ldflags}"
if test "${GCC}" = yes; then
diff -ru R-3.2.3.orig/src/include/Defn.h R-3.2.3/src/include/Defn.h
--- R-3.2.3.orig/src/include/Defn.h 2015-08-25 22:15:24 +
+++ R-3.2.3/src/include/Defn.h 2015-12-16 10:53:08 +
@@ -1271,7 +1271,7 @@
void invalidate_cached_recodings(void); /* from sysutils.c */
void resetICUcollator(void); /* from util.c */
void dt_invalidate_locale(); /* from Rstrptime.h */
-int R_OutputCon; /* from connections.c */
+extern int R_OutputCon; /* from connections.c */
extern int R_InitReadItemDepth, R_ReadItemDepth; /* from serialize.c */
void get_current_mem(size_t *,size_t *,size_t *); /* from memory.c */
unsigned long get_duplicate_counter(void); /* from duplicate.c */
A 32-bit build completes
...
make[3]: Leaving directory '/tmp/RtmpcvzNTA/R.INSTALL7e05458d74e28/mgcv/src'
installing to /data/prj/cran/32/R-3.2.3/library/mgcv/libs
** R
** data
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** testing if installed package can be loaded
* DONE (mgcv)
make[2]: Leaving directory
'/data/prj/cran/32/R-3.2.3/src/library/Recommended'
make[1]: Leaving directory
'/data/prj/cran/32/R-3.2.3/src/library/Recommended'
make[1]: Entering directory '/data/prj/cran/32/R-3.2.3/src/library'
'pdflatex' is needed to make vignettes but is missing on your system.
make[1]: Leaving directory '/data/prj/cran/32/R-3.2.3/src/library'
root@x065:[/data/prj/cran/32/R-3.2.3]
The same command, but as 64-bit stops at:
gcc -maix64 -mcpu=power5 -std=gnu99 -shared -Wl,-G -Wl,-bnoentry -lc
-L../../../../lib -L/opt/lib -o tools.so text.o init.o Rmd5.o md5.o
signals.o install.o getfmts.o http.
o gramLatex.o gramRd.o -lm -L../../../../lib -lR /opt/lib/libintl.a
/opt/lib/libiconv.a -lpthread -lc
ld: 0711-224 WARNING: Duplicate symbol: Rf_yylval
ld: 0711-224 WARNING: Duplicate symbol: Rf_yychar
ld: 0711-224 WARNING: Duplicate symbol: Rf_yynerrs
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
make[6]: Entering directory '/data/prj/cran/64/R/src/library/tools/src'
make[6]: Warning: File 'Makefile' has modification time 5.9 s in the future
mkdir ../../../../library/tools/libs
make[6]: warning: Clock skew detected. Your build may be incomplete.
make[6]: Leaving directory '/data/prj/cran/64/R/src/library/tools/src'
make[5]: Leaving directory '/data/prj/cran/64/R/src/library/tools/src'
make[4]: Leaving directory '/data/prj/cran/64/R/src/library/tools'
make[4]: Entering directory '/data/prj/cran/64/R/src/library/tools'
installing 'sysdata.rda'
Error: Line starting 'Package: tools ...' is malformed!
Execution halted
/data/prj/cran/R-3.2.3/share/make/basepkg.mk:150: recipe for target
'sysdata' failed
make[4]: *** [sysdata] Error 1
make[4]: Leaving directory '/data/prj/cran/64/R/src/library/tools'
Makefile:30: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/data/prj/cran/64/R/src/library/tools'
Makefile:36: recipe for target 'R' failed
make[2]: *** [R] Error 1
make[2]: Leaving directory '/data/prj/cran/64/R/src/library'
Makefile:28: recipe for target 'R' failed
make[1]: *** [R] Error 1
make[1]: Leaving directory '/data/prj/cran/64/R/src'
Makefile:60: recipe for target 'R' failed
make: *** [R]
[Rd] Mystifying SEGFAULT on 3.2.3 but not 3.2.2
Dear R developers,
(Apologies about previous incomplete e-mail, I fat-fingered a keyboard
shortcut)
I recently upgraded to 3.2.3 and am getting mystifying errors with my
in-development code (available at
https://github.com/gertvv/gemtc/tree/feature/regression). Every few hundred
LPs that I solve using the rcdd package will result in a SEGFAULT in the
garbage collector (address 0x10, cause 'memory not mapped') or an error
about a list not existing. Downgrading to 3.2.2 works, but *only* after
completely removing my local R packages and re-installing them. A
subsequent upgrade to 3.2.3 will again be broken, and even more
mysteriously it will also break a re-downgrade to 3.2.2 until I again purge
my local packages and re-install them.
To downgrade I am using (with the CRAN ubuntu mirror enabled):
sudo apt-get purge r-base-core
sudo rm -rf ~/R
sudo apt-get install r-base-core=3.2.2-1trusty0 r-base-dev=3.2.2-1trusty0
r-recommended=3.2.2-1trusty0
sudo apt-get install r-cran-rjags
R -e "install.packages(c('devtools','igraph','meta','truncnorm','rcdd'))"
The code that produces a SEGFAULT (usually after 5-15 iterations) under
3.2.3, but not 3.2.2:
library(devtools)
load_all('gemtc')
for (i in 1:100) { print(i); mtc.model(thrombolytic) }
(note that the SEGFAULT also happens without devtools)
The sessionInfo() in 3.2.2:
R version 3.2.2 (2015-08-14)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 14.04.3 LTS
locale:
[1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
[3] LC_TIME=nl_NL.UTF-8LC_COLLATE=en_US.UTF-8
[5] LC_MONETARY=nl_NL.UTF-8LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=nl_NL.UTF-8 LC_NAME=C
[9] LC_ADDRESS=C LC_TELEPHONE=C
[11] LC_MEASUREMENT=nl_NL.UTF-8 LC_IDENTIFICATION=C
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] gemtc_0.8 coda_0.16-1 lattice_0.20-33 devtools_1.9.1
loaded via a namespace (and not attached):
[1] Rcpp_0.12.2 roxygen2_5.0.1 rcdd_1.1-9 digest_0.6.8
[5] truncnorm_1.0-7 grid_3.2.2 plyr_1.8.3 meta_4.3-2
[9] magrittr_1.5stringi_1.0-1 rjags_4-4 tools_3.2.2
[13] stringr_1.0.0 igraph_1.0.1memoise_0.2.1
A core dump is here:
https://drive.google.com/a/rug.nl/file/d/0BxhVLNPmwLrycTYtOHNxNXZTMEk/view?usp=drive_web
I have tried debugging this but am stumped. Any help would be greatly
appreciated!
Kind regards,
Gert van Valkenhoef
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Question about bug reporting, and the followup process
Hi, I sent in three bug-reports (maybe should have been 4, because the second contains an "enhancement" as well as well as a bug). I do not set "Importance", ever - or, is that the custom here? Regards, Michael p.s. - maybe related - is it best practice to add [Rd] in the subject line, or is there a program doing that instead? __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
