search for: tangling

Hi, Recently I saw a couple of cases in which the package vignettes were somewhat complicated so that Stangle() (or knitr::purl() or other tangling functions) can fail to produce the exact R code that is executed by the weaving function Sweave() (or knitr::knit(), ...). For example, this is a valid document that can pass the weaving process but cannot generate a valid R script to be source()d: \documentclass{article} \begin{document} Assign 1...

Do the "at" and "labels" components of the "scales" list argument to xyplot not do what you want? Cheers, Bert On Thu, Sep 5, 2024 at 4:05?AM Gerrit Draisma <gdraisma at xs4all.nl> wrote: > Dear R-helpers, > > In the plot below I would like to have labels at positions 2^(3*(0:10)), > and keep the labels in the exponential format. > I tried

Hello List, I have been using Sweave for my homework this last quarter and have been very impressed at how much time and effort it saves me. I, however, have run up against a problem which I have not been able to solve using any of the Sweave/LaTeX tricks I know. I work through my homework one problem at a time, typesetting equations and writing R code, etc. and occasionally use

Dear R-helpers, In the plot below I would like to have labels at positions 2^(3*(0:10)), and keep the labels in the exponential format. I tried using yscale.components.default. *This* gives the right format of the labels: -------- > yscale.components.default(lim= c(0,30),log=2) .... $num.limit [1] 0 30 ... [1] 0 5 10 15 20 25 30 ... $left$labels$labels [1] "2^0" "2^5"

retitle 571634 xen-utils-common vif-common.sh still using --physdev-out, --state found 571634 4.0.0-1 thanks Hi, That link to upstream patch in the last message is apparently broken, a working one is: http://xenbits.xen.org/hg/xen-unstable.hg/rev/b0fe8260cefa but also more importantly for the current stable package: http://xenbits.xen.org/hg/xen-4.0-testing.hg/rev/af7110f4f803 Because the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 24 May 2014, Stanislas SABATIER wrote: > Dovecot is handling the final delivery, through mail-filter plugin as > follow : > > 1. both users contexts are created from user_db queries > 2. mail-filter plugin is init for user2 > 3. /mail_user_created/ for user2 > 4. mai-filter plugin arguments are parsed for user2 > 5.

...Error: processing vignette 'diveMove.Rnw' failed with diagnostics: missing values and NaN's not allowed if 'na.rm' is FALSE Execution halted ---<--------------------cut here---------------end--------------------->--- There are no problems running the R code resulting from tangling the vignette. Specifically, the code referred to in the error is a single function call, which returns with no warnings or errors, so I have little to hold on to. How can I get more verbose debug from "R CMD build"? -- Seb

I have two questions about packaging up code. 1) Weave/tangle advisable? In the course of extending some C code already in S, I had to work out the underlying math. It seems to me useful to keep this information with the code, using Knuth's tangle/weave type tools. I know there is some support for this in R code, but my question is about the wisdow of doing this with C (or Fortran, or other

System installed : Dovecot 2.2.12 as IMAP server and Postfix as MTA. Dovecot and Postfix connected via LMTP + Dovecot mail plugin 'mail-filter' to encrypt/decrypt emails on the fly with public/private users' RSA keys. Case study : You have 3 (virtuals) users belonging to 3 different domains, all managed by your Dovecot server. One of these users is connected to Dovecot with MUA

Dear list Getting very frustrated with this simple-looking problem > m1 <- lm(x~y, data=mydata) > outliers <- abs(stdres(m1))>2 > plot(x~y, data=mydata) I would like to plot a simple x,y scatter plot with labels giving custom information displayed for the outliers only, i.e. I would like to define a column mydata$labels for the mydata dataframe so that the command >

Kind of a whole set of general questions - pardon for one more, please! I've read some of the thinking behind not having a DC also be a file server. But it's not a "rule" - just a suggestion. But here's a wrinkle on things. In more than a few setups, I'll have DC's on VM's - and they won't be serving files they'll be purely DC's. Then on dedicated

So far you haven't provided a reproducible example yet. I wonder what exactly the object `sample_analysis` is. Sounds like it is an environment. If that is the case, devtools::build_vignettes() will tangle (for the meaning of "tangle", see ?tools::buildVignette) your vignette into an invalid R script. Environments cannot be represented via dput(), so knitr's purl() (eventually

On 04/24/2013 07:39 PM, Chris Lattner wrote: > On Apr 24, 2013, at 6:27 PM, Reed Kotler <rkotler at mips.com> wrote: >> I would really push towards doing this in LLVM IR as the next step. > What makes you say that? > Partly for the reasons Dan stated. For me, the IR is definitely way more friendly too and not tangled up in lots of undocumented obscurity as selection DAG is

...requently, especially for documenting code. But the syntax is slightly awkward for me (<<name>>= ... @), and I was thinking if there would be a way of importing the type of code extracted from an Rnw file back into an Rnw file? The advantage would be that the code could run in R without tangling. Obviously, sweave options could not be imported, but that would be fine for me. Below an example of the code generated by Rtangle, which I would like to import into a sweave file. Cheers Rainer ################################################### ### chunk number 1: a ###########################...

thanks for the reply, Phil It would, were udev not inserting USB and/or eSATA drives at /dev/sdb1 and/or /dev/sdc1 and exposing the array to the udev rule intended to handle only removable devices (at sdc or sdd). The array then mounts unpredictably in /media/xxx-sdc1 or sdd1 - not what is wanted - depend on how many removable devices are plugged at the time of rebooting. Of course, a single

Interesting, yesterday I had exactly this problem, but today I solved it (see the R-pkg-devel list) by _installing_ R-devel and > update.packages(checkBuilt = TRUE) I also tried it on Martin's Fedora 26 example below. Worked fine (had to install some packages...) On ubuntu 16.04. G?ran Brostr?m On 2017-12-06 11:29, Martin Maechler wrote: >>>>>> Pearce, Robert

Hi all, I'm writing a test compiler to understand the overall structure of LLVM and I managed to produce IR for expressions, functions and function calls. I'm following the Kaleidoscope example and had a hard time de-tangling the language specifics from LLVM syntax. Anyhow, I got here and I'd like some more specific help to finish my example. My very simple language has global variables and static functions only, so I can focus on the code generation. My problems are below. 1. Kaleidoscope uses function calls, whi...

I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829). I build 'httk' from the command prompt using 'R CMD build httk' after installing the required packages. Then when the vignettes are being created, it crashes. Today I installed the latest versions of Rtools,

...te 'diveMove.Rnw' failed with diagnostics: > missing values and NaN's not allowed if 'na.rm' is FALSE > Execution halted > ---<--------------------cut here---------------end--------------------->--- > > There are no problems running the R code resulting from tangling the > vignette. Specifically, the code referred to in the error is a single > function call, which returns with no warnings or errors, so I have > little to hold on to. How can I get more verbose debug from "R CMD > build"? > Are you sure that the complete R code of the...

Dear List, Sorry if I'm overlooking something simple here but I have gotten a bit tangled. I am trying to print the next five values(with their dates), which occur after a certain condition is met. I have a series of data in zoo format, call it "A". From this series I have created a subset (also in zoo format) based on a certain condition, call this series "B". I