similar to: Examples for Markov Chain in Economics

Hi, I have an nxp data set of time series. For my final year project, I would like to partition this data set into a smaller number of units ( < n). Where each of the units contains time series that move closely together (i.e. in unison), and the "simmilarity" (in terms of occurence & amplitudes of peaks and troughs) between the segregated units is "low". I know

On 12 August 2017 at 15:10, luke-tierney at uiowa.edu wrote: | As the Python posts poitns out, it is possible to use alternate malloc | implementations, either rebuilding R to use them or using LD_PRELOAD. | On Ubuntu for example, you can have R use jemalloc with | | sudo apt-get install libjemalloc1 | env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1 R | | This does not seem to hold

Dear all, Can anybody tell me how to export a 3d figure made with the plot3d function? I'm careless about whether it's still interactive or not in another format, as long I can get it out of R. Thanks! Alejandro Gonz?lez Departamento de Biodiversidad y Conservaci?n Real Jard?n Bot?nico Consejo Superior de Investigaciones Cient?ficas Claudio Moyano, 1 28014 Madrid, Spain Tel +0034

Michael, This looks rather like a 'compile-time versus run-time' question to me. If you look at etc/Renviron.in in the R sources you see a number of choices, some of them with configure-time determined values (which I tend to override with values for the Debian package). For 'EDIT' it is ## Default editor EDITOR=${EDITOR-${VISUAL-vi}} giving us two env vars to override eg

There is a central assertion to this argument that I don't follow: > At the end of the day most published results obtained with R just won't be reproducible. This is a very strong assertion. What is the evidence for it? I write a lot of Sweave/knitr in house as a way of documenting complex analyses, and a glm() based logistic regression looks the same yesterday as it will

It looks like R has defaulted to using 'vi' for file.edit() (via EDITOR since ~24 years ago[1][2]. These days I think it is much more common to write code from lightweight environments, e.g. Docker files which strip all unnecessary commands. On such machines, it is not safe to assume 'vi' is installed, and it's not uncommon to encounter an issue like I did again today[3] where

Strange because in my all my experiments calling malloc.trim always helped - memory reported by top decreased to the level it supposed to be. Do you have in mind case when calling malloc.trim won't do anything? Also shouldn't MALLOC_TRIM_THRESHOLD_ env variable has impact on malloc.trim calls? At the moment seems any value is ignored... 12 ???. 2017 ?. 6:09 ?? ???????????? "Simon

Very interesting information about switching glibc malloc to jemalloc. So I see action plan as following: 1. set up some benchmark (need to think about design) 2. Run it on ubuntu machine with default glibc malloc 3. Run it with malloc_trim passed with reg.finalizer() 4. Run it with jemalloc 5. Review results and if they will look better than with glibc malloc - possibly

On Saturday, August 12, 2017 5:36:36 PM EDT Dirk Eddelbuettel wrote: > On 12 August 2017 at 15:10, luke-tierney at uiowa.edu wrote: > | As the Python posts poitns out, it is possible to use alternate malloc > | implementations, either rebuilding R to use them or using LD_PRELOAD. > | On Ubuntu for example, you can have R use jemalloc with > | > | sudo apt-get install