similar to: x-axis with month and year

Hi all, I was wondering if you can help me with the following situation: I have a data frame that includes weather station data for 30 years in the form: YEAR, MONTH, DAY, TEMP 1970, 01, 01, -15 ... 1999, 12, 31, -21 I would like to add another variable "JULIAN" that assigns the integers 1 to 365 (and 1 to 366 for leap years) for each day of a year over multiple years. Here is what

Dear list, I cannot figure out why, after sub-setting my data, that particular item which I don't want to plot is still in the newly created subset (please see example below). R somehow remembers what was in the original data set. A work around is exporting and importing the new subset. Then it's all fine; but I don't like this idea and was wondering what am I missing here? Thanks!

Dear List! When I'm using "plot(lm(y~x))" R shows me 4 different plots. They pop-up individually by clicking on the graph. How can I save for example the 2nd plot? I've found a camera button that says "copy to the clipboard as a metafile" once you place the mouse pointer on it. I tried, though it's not working. Any other suggestions? Thanks!! Stefan

Hey list! It looks simple, though it's not possible for me to plot the following properly: (some made-up data) GrSe Clone1 Clone2 Clone3 Clone4 Clone... G1999 2 3 6 5 G2000 2 5 7 4 G2001 5 3 7 3 G2002 4 5 8 3 G... GrSe=Growing Season. I've read the file as "x" and then tried: plot(x$GrSe,x$Clone1) The output is 4 horizontal bars. Even if I write

Hi there, I hope you guys can help me with the following: If have a file like this: year clone code height 1995 4 4-1 1 1996 4 4-1 2 1997 4 4-1 3 1995 4 4-2 1 1996 4 4-2 2 1997 4 4-2 3 1995 5 5-1 1 1996 5 5-1 2 1997 5 5-1 3 1995 5 5-2 1 1996 5 5-2 2 1997 5 5-2 3 . . . . . . . . . . . . 1. I want to analyze the growth of 52 different clones replicated 25 times over a period of 19 years. Now

[This email is either empty or too large to be displayed at this time]

Just did a git pull to the below commit (to get the latest version 1.25.37) and did a local build, this is what I see: Error: The files ../ocaml/guestfs.cmi and perl_edit.cmi make inconsistent assumptions over interface Guestfs Haven't investigated further, thought I'd post it here first: $ git rev-parse --short HEAD 838a3c9 $ ./autogen.sh $

The ocaml.opt compiler defaults to building things in the same directory as its input; we need explicit -o options to build in a VPATH $(builddir) when $(srcdir) is read-only (as is the case during 'make distcheck'). We also have to build any side effect files explicitly in cases where we can't directly use -o to control those outputs alongside the final product. Thanks: Richard W.M.

On Sun, Nov 17, 2019 at 7:03 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Sun, Nov 17, 2019 at 06:07:48PM +0200, Nir Soffer wrote: > > Looks like virt-v2v cannot be built now, since it requires non-existing version > > of libguestfs-devel. > > > > Based on (no README or any instructions in virt-v2v) > >

I am encountering a make error on an AIX 5.2 with R-2.3.0 and R-patched_2006-05-10 after successfully configuring them using gcc-4.1.0, gnu make, and the following configure options CC=/usr/local/bin/gcc F77=/usr/local/bin/gfortran CXX=/usr/local/bin/g++ MAIN_LDFLAGS=-Wl,-brtl SHLIB_LDFLAGS=-Wl,-G CFLAGS='-g -O' FFLAGS='-O' CXXFLAGS='-g -O' bash-3.00$ ./configure

Once ocamlfind is installed, 'make' failed for me with: ocamlfind ocamlc -g -annot -safe-string -warn-error CDEFLMPSUVYZX+52-3 -ccopt '-gdwarf' -package unix -c NBD.ml -o NBD.cmo File "NBD.ml", line 1: Error: Could not find the .cmi file for interface NBD.mli. make[2]: *** [Makefile:823: NBD.cmo] Error 2 I'm not positive that this is the perfect fix, but it at least

Package: xen-api-libs I cannot backport xen-api-libs to an oldstable system. It fails with: $ dpkg-buildpackage -rfakeroot -us -uc dpkg-buildpackage: source package xen-api-libs dpkg-buildpackage: source version 0.5.2-3.1 dpkg-buildpackage: source changed by St?phane Glondu <glondu at debian.org> dpkg-buildpackage: host architecture amd64 dpkg-source --before-build xen-api-libs-0.5.2

I am getting a build error after doing a "make update" and then running "make clean all": gmake[4]: *** No rule to make target `/home/ryan/llvm/llvm_core/trunk/Release+Asserts/lib/ocaml/llvm.cmi', needed by `/home/ryan/llvm/llvm_core/trunk/bindings/ocaml/transforms/ipo/Release+Asserts/llvm_ipo.cmi'. Stop. gmake[4]: Leaving directory

--- builder/Makefile.am | 18 +++++++++++++- configure.ac | 2 ++ mllib/Makefile.am | 60 +++++++++++++++++++++++++++++++--------------- ocaml/Makefile.am | 28 +++++++++++++++------- ocaml/examples/Makefile.am | 13 ++++++++++ resize/Makefile.am | 18 +++++++++++++- sparsify/Makefile.am | 18 +++++++++++++- sysprep/Makefile.am | 18

hej i'm plotting time-series and label the x-axis as follows: r <- as.POSIXct(round(range(p1$time), "month")) to define the time range for labeling the xaxis plot(p1$time,p1$ p1, type="l", xaxt="n") plots p1 against time axis.POSIXct(1, at=seq(r[1], r[2], by="month"), format="%m") labels the axis in mothly steps. what I want do do

Hi Greg, The only reason I included the staxlab function in the plotrix library was to fit all the dates onto the axis. If you want to try it: install.packages("plotrix") Jim On Sun, May 6, 2018 at 9:02 AM, Gregory Coats <gregcoats at me.com> wrote: > Jim, Thanks for responding! > I am using the official R 3.5.0 for Mac OS X. > This apparently does not include library

Jim, That you very much! How do I instruct staxlab to label once every n days, rather than labeling every day? Greg > On May 5, 2018, at 6:50 PM, Jim Lemon <drjimlemon at gmail.com> wrote: > > staxlab(1,at=x_yyyymmdd,labels=format(x_yyyymmdd,"%Y-%m-%d")) [[alternative HTML version deleted]]

Hi Greg, By default, the "axis" function puts the labels on one line and drops labels that would overlap. When you have labels that are all the same length, this usually results in every second, or third, or fourth label being displayed. So you can probably get what you want by not using staxlab. However, if you really want to use staxlab, try this:

Look at par(las=2) in the graphics package. You will almost certainly have to increase the bottom margin, e.g.: par(mar=c(6,4,4,2) to accomodate the vertical labels. Jim On Mon, May 7, 2018 at 2:11 PM, Gregory Coats <gregcoats at me.com> wrote: > Thanks. Regarding > axis(1,at=x_yyyymmdd,labels=format(x_yyyymmdd,"%Y-%m-%d")) > > How do I get the text for YYYY-MM-DD

Hi Greg, This is because both plots have equally spaced x values. To see the difference, try this: plot (x_yyyymmdd, y_duration, type="l", xaxt="n", yaxt="n", ylim=range(240,480), xlab="", ylab="", col="blue") axis(1) plot ( y_duration, type="l", xaxt="n", yaxt="n", ylim=range(240,480),