similar to: Plotting the occassional second label

I'm trying to select a subset of a dataframe while dropping some factors. While the dataset gets smaller all Factor levels remain and I need to get rid of them. Strangely enough, I am almost certain that the same code on the same data worked OK earlier today - and it is not the first time that I'm not able to replicate earlier results with this command (I know, I might just be going

So I've been an avid user of Left 4 Dead 1 and 2. This problem only seems to arise in L4D2, where the audio will cut out. Now, not completely, some things will drop but some stay, for instance, I can hear the noise my gun makes, the shots fired but I don't hear characters talking anymore or any special infected sounds. Another instance is I'll see my gun firing but I'll hear the

Hello everybody, I'm testing the randomForest package in order to do some simulations and I get some trouble with the prediction of new values. The random forest computation is fine but each time I try to predict values with the newly created object, I get an error message. I thought I was because NA values in the dataframe, but I cleaned them and still got the same error. What am I

Dear R-users, Does anyone knows how I can order my serie of boxplots from lowest to highest median (which is much better for visualization purposes). thanks in advance, willem [[alternative HTML version deleted]]

On Aug 13, 2015, at 12:45 PM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 > NUT is apparently 2.4.1 > It was installed by tar. > > Monitoring a lot of apc UPS units?mostly Smart-UPS of various flavors, also a Silcon DP380E. > > Normally works just fine? ?upslog? writes status log every 30 seconds with

[please keep the list CC'd, thanks] > On Aug 14, 2015, at 10:27 AM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Would it put NA in the log files if maxage was too short? I think so. I haven't tried it, but if snmp-ups polls every 30 seconds, and MAXAGE is 15, then with a random polling interval, 50% of the time the data would be more than 15 seconds old. In

Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 NUT is apparently 2.4.1 It was installed by tar. Monitoring a lot of apc UPS units-mostly Smart-UPS of various flavors, also a Silcon DP380E. Normally works just fine... "upslog" writes status log every 30 seconds with various parameters.. Every so often, one of the UPS units has a log entry of:

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS