similar to: package Spcmdr

After installation of R into VineLinux2.1.5, I started to enjoy statistics following some instruction, and found it very useful. One of my main purpose to use R is to try spatial statistics. Since library named "spatial" has already installed, I just tried ... > library(spatial) > towns <- ppinit(test.dat) ------- test.dat ------- x,y 4,7 5,7 5,8 5,9 6,7 6,8 6,9 7,8

Per the message from Alexander Nervedi, 29 April 2006: > I have to be making a riddiculously silly ommission. > when I run the fillowing i get the cloud plot ok. But I cant figure > out what I am missing out when I call wireframe. > Any help would be appreciated. > x<-runif(100) > y<-rnorm(100) > z<-runif(100) > temp <-data.frame(x,y,z) >

Full_Name: Larry Layne Version: 2.4.0 OS: MS Windows 2000 Submission from: (NULL) (129.24.91.249) All of the following libraries loaded just fine in version 2.3.1: > utils:::menuInstallLocal() package 'tripack' successfully unpacked and MD5 sums checked updating HTML package descriptions > library(tripack) Error in dyn.load(x, as.logical(local), as.logical(now)) : unable

Probably a simple question, but I can't find the answer to it ... In the 'ppinit' code it describes how it takes a 'file in standard format' and creates a point process object with it. Can anyone enlighten me as to what this 'standard format' is? The example given doesn't allow me to view the '.dat' file that apparently is in this format. Thanks, Suzie

Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups

I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite information I can help with, let me know. David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com> Sent: Sunday, December 8, 2019 8:36 PM To: Layne Fowler

Thanks Ken. I'll plan to sit down and look up the protocol information over the next week or so and follow up. ________________________________ From: Ken Olum <kdo at cosmos.phy.tufts.edu> Sent: Tuesday, January 14, 2020 1:35:10 PM To: David Zomaya Cc: kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser]

If you'd like, shoot me over your serial number and the corner-cases you don't have answers for and I can look into it. Thank you, David Zomaya Tripp Lite david_zomaya at tripplite.com -----Original Message----- From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> On Behalf Of Ken Olum Sent: Tuesday, January 14, 2020 11:24 AM To: Layne

Your suggestion of rebuilding the driver fixed the issue of the UPS turning back during a power failure. Now the UPS shuts down the clients, then powers off appropriately. If power returns it turns back on also. The only bug is if power returns before the UPS has turned the load off. In that case the UPS will remain off until it is manually turned on. This might just be a limitation of this

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

Thanks Marco, I may try this if I can't get David's udev rules to work. On Mon, Dec 9, 2019 at 12:58 AM Marco Walther <marco at sonic.net> wrote: > On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite > information I can help with, let me know. > > We had that discussion about the

On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp > Lite information I can help with, let me know. > We had that discussion about the SMART1500LCDT  & USB a long time ago:-( I bought mine in 2013 (still going strong on the second set of batteries) and in August 2016 we had some discussions about the USB

Charles, thank you for that link to David's earlier message. I tried adding those udev rules and changing the pollinterval. I need to do some tinkering but I don't think the part RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl start" is working right. If I manually run the commands then the USB disconnects stop and there are no kernel messages. Running "sudo /lib/nut/usbhid-ups

Hello, Does anyone test ZFS on Linux and ACLs? I can't setup POSIX ACLs and any extended even using acl_xattr or acl_tdb. Is any way to use ACLs with ZFS on Linux (Samba 3 or 4)? Best regards /Adrian Berlin --

On Dec 8, 2019, at 5:46 PM, Layne Fowler <layne.fowler at gmail.com> wrote: > > My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. > > I have tried using a different USB port and using a brand new USB cable. I have not had success by

From: Layne Fowler <layne.fowler at gmail.com> Date: Fri, 3 Jan 2020 16:22:10 -0500 I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? I didn't, because I don't use that functionality, though it does look as though it should be modified in just the same way. This might

My serial # is 2835BY0SM886900639, model # SMART1500LCD. Using stock nut, my UPS will turn back on after load off, even with no power connected. Servers boot up and fail when the UPS finally dies. Using my patched nut, the UPS will fail to turn on if the power returns after the shutdown command but before actual load off. It seems like this UPS is missing the "load.on" and/or

Hello Everybody. i am installing rgeo in R-2.13 on debian lenny. i am getting following error. Can anybody help me why i m not able to compile rgeos. rgeos_misc.c: In function ‘rgeos_hausdorffdistance’: rgeos_misc.c:55: error: ‘GEOSHausdorffDistance_r’ undeclared (first use in this function) rgeos_misc.c:55: error: (Each undeclared identifier is reported only once rgeos_misc.c:55: error: for

Hi, David. Thanks for the offer of help. I have BCPERS450 serial number 2701DVHBC809300177. Unfortunately I'm about to go on a trip and will be away until the end of the month, so I don't have much time to discuss these things at the moment, but maybe Layne will have something to say. My understanding from when I was working on this a couple years ago is that the main problem in

My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. I have tried using a different USB port and using a brand new USB cable. I have not had success by changing config parameters like pollfreq/pollinterval/etc. What is causing the UPS to keep disconnecting?