Displaying 20 results from an estimated 80 matches similar to: "percent data being treated as categorical"
2010 Jan 06
2
problem with strptime and 2010 dates
Hi, I'm reading data from a text file and transforming it in R and my date
column seems to be getting corrupted. Can someone point out what's wrong?
This code worked fine until I added a new date in 2010.
thank you.
To load the data I run:
work_table = read.table(datafilename,header=TRUE) #read the
data file
attach(work_table)
2006 Aug 15
0
file object treated as a string
I am trying to implement the uploading of a file to a remote server
My upload form looks like this:
<%= start_form_tag(:action => "save_image", :multipart => true) %>
<td><b>Description</b> </td>
<td><%= text_area("image", "descript", "cols" => 33, "rows" => 5) %></td>
2009 Jun 03
0
Treated - KernSmooth pckg - dpik function gives numeric(0) for kernel="epanech"
Epanechnikov kernel works if option canonical=TRUE, however it would
be good to know why it does not for for canonical=FALSE (default).
Sorry for craetaing maybe useless thread.
Best regards,
Ondra.
[[alternative HTML version deleted]]
2008 Mar 13
0
printk: cc1 warnings being treated as errors
Hi,
I was trying to write printk statements in x86_emulate.c and I am getting
following error.
cc1: warnings being treated as errors
x86_emulate.c: In function ''x86_emulate'':
x86_emulate.c:2913: warning: ISO C90 forbids mixed declarations and code
x86_emulate.c:2939: warning: ISO C90 forbids mixed declarations and code
Yes, I know probably I can make changes in Makefile to
2008 Mar 13
0
printk: cc1 warnings being treated as errors
Hi,
I was trying to write printk statements in x86_emulate.c and I am getting
following error.
cc1: warnings being treated as errors
x86_emulate.c: In function ''x86_emulate'':
x86_emulate.c:2913: warning: ISO C90 forbids mixed declarations and code
x86_emulate.c:2939: warning: ISO C90 forbids mixed declarations and code
Yes, I know probably I can make changes in Makefile to
2003 Mar 15
0
configure, IBM AIX and checking whether leap seconds are treated according to POSIX...
Hi,
I am trying to compile R for 64 bits on a mainframe running
IBM AIX. Setting the environment variable OBJECT_MODE=64
leads to hanging while checking whether leap seconds are treated according to POSIX...
Interestingly, it works fine when OBJECT_MODE=32...
Any pointer would help me much...
Thanks,
L.
--
--------------------------------------------------------------
currently at the
2002 Mar 26
0
[Bug 189] New: pam_setcred() failures should not be treated as fatal
http://bugzilla.mindrot.org/show_bug.cgi?id=189
Summary: pam_setcred() failures should not be treated as fatal
Product: Portable OpenSSH
Version: 3.1p1
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2006 Mar 23
0
Compile Error xen 3.0.1 on FC5 "cc1: warnings being treated as errors"
Hello,
To get the binary vmxloader on FC5 i need to compile this from xen source
with "make KERNELS=linux-2.6-xen world".
There is a error "cc1: warnings being treated as errors" and compile aborts.
---
make[3]: Entering directory `/tmp/xen-3.0.1/xen''
tools/figlet/figlet -d tools/figlet Xen 3.0.1 > include/xen/banner.h.new
__ __ _____ ___ _
\ \/
2013 May 01
1
[LLVMdev] are non-byte-multiple integers treated as exact?
If I create an integer size which is not a native size on the target
platform is it nonetheless treated as though it were that size? That is,
do all the basic operations (add, mul, shift, etc.) do the proper
treatment to ensure it behaves as an exactly sized integer value?
I'm looking at the native assembly output of several examples and it
does appear that some limited handling is done. For
2013 Sep 23
2
[LLVMdev] [lld]Native reader/writer is not called, treated as Dead Code!
Hi Nick,
When changes were brought from lld core to the Universal Driver, calls
to NativeReader/NativeWriter code was stripped away.
Was this by accident ?
Thanks
Shankar Easwaran
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
2013 Sep 23
0
[LLVMdev] [lld]Native reader/writer is not called, treated as Dead Code!
On Sep 23, 2013, at 10:02 AM, Shankar Easwaran <shankare at codeaurora.org> wrote:
> Hi Nick,
>
> When changes were brought from lld core to the Universal Driver, calls to NativeReader/NativeWriter code was stripped away.
This needs to be fixed. Originally, ever run of the linker would have a step were it wrote to native and read that back in. That makes sense for test cases,
2002 Apr 01
2
[Bug 189] pam_setcred() failures should not be treated as fatal
http://bugzilla.mindrot.org/show_bug.cgi?id=189
------- Additional Comments From stevesk at pobox.com 2002-04-01 17:49 -------
why should pam_setcred() failures not be treated as fatal?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2003 Jan 07
1
[Bug 189] pam_setcred() failures should not be treated as fatal
http://bugzilla.mindrot.org/show_bug.cgi?id=189
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From djm at mindrot.org 2003-01-07 17:40
2020 Sep 22
0
Dovecot virtual folders usage: seen in Tbird client if subscribed, treated as _real_ folders -- and archived to local/offline storage? How to prevent?
i run a dovecot v2.3.10 server.
config includes virtual folders,
dovecot.conf
mail_plugins = virtual
mail_location = maildir:/data/mail/%d/%n/Maildir:LAYOUT=fs:UTF-8
imap_capability = +SPECIAL-USE
namespace inbox {
inbox = yes
type = private
separator = /
prefix =
hidden = no
list = yes
subscriptions = yes
...
mailbox virtual/All {
special_use = \All
2015 Dec 02
0
Is every node being treated equally in tinc?
Hi Guys,
I have a general question, traffic wise, is every node from tinc being
treated equally? Say every tinc node is a pc(with same condition)
connectting to same carrier signal (say AT&T), after a certain amount of
time(say one week), will every node(pc) consume the same amount of data? If
there will be a difference, why so?
Thanks.
-------------- next part --------------
An HTML
2006 Nov 03
1
question of one matrix column being treated as list rather than vector
Hi,
I have one matrix derived from my function. It is as following:
Browse[1]> each.uaa.data
[,1] [,2]
[1,] 33 152.3530
[2,] 33 264.7059
[3,] 51 583.3333
[4,] 33 323.3333
[5,] 50 292.549
[6,] 33 300
[7,] 56 104.1176
[8,] 52 246.6667
[9,] 53 242.5490
[10,] 33 212.9412
when I tried to get each.uaa.data[,2], it gave me a list, when I expect a
vector so that
2023 Jun 24
1
Why is WebRTC treated differently from regular SIP in Asterisk
I'm learning about WebRTC clients, and am wondering why Asterisk treats them
differently from any other SIP client.
The media (RTP) should be no different, so the only difference should be on
the signaling side. I noticed that the Asterisk wiki mentions the need for
res_pjsip_transport_websocket, so does that mean Asterisk requires the
signaling to occur over a websocket?
If I used
2008 Aug 07
1
'"ts" treated as a registered S3 class, but keep its "structure" behaviour' ?
Dear all,
In R-devel I have noticed the new approach for the "ts" class in the
package "methods".
the "structure" behaviour of "ts" is not always kept when one uses
"ts" objects and objects of classes which extend the virtual class
"structure".
As a short example:
## this works fine
setClass("foo", representation(header =
2018 Jun 10
1
[Bug 13467] New: an xattr filter rule is treated as a file filter rule on the remote side
https://bugzilla.samba.org/show_bug.cgi?id=13467
Bug ID: 13467
Summary: an xattr filter rule is treated as a file filter rule
on the remote side
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
Component: core
2018 Apr 29
3
bug: xattr filter rule treated as file filter rule on the remote side
Summary: an xattr filter rule (e.g. --filter='-x! user.*’, which is suggested by the documentation) is treated as a file filter rule on the remote side.
Repro #1, sender is local:
host1$ rsync --filter=‘-x! user.*' -avvvHX --delete /tmp/test/. host2:test
...
[Receiver] add_rule(-! user.*)
Repro #2, sender is remote:
host1$ rsync --filter=‘-x! user.*' -avvvHX --delete host2:test/.