Displaying 20 results from an estimated 1000 matches similar to: "[PATCH 1/2] readtable: add hook for type conversions per column"
2019 Mar 28
2
[RFC] readtable enhancement
Kurt,
Cool idea and great "seeing new faces" on here proposing things on here and
engaging with R-core on here.
Some comments on the issue of fallbacks below.
On Wed, Mar 27, 2019 at 10:33 PM Kurt Van Dijck <
dev.kurt at vandijck-laurijssen.be> wrote:
> Hey,
>
> In the meantime, I submitted a bug. Thanks for the assistence on that.
>
> > and I'm not
2019 Mar 27
3
[RFC] readtable enhancement
This has some nice properties:
1) It self-documents the input expectations in a similar manner to
colClasses.
2) The implementation could eventually "push down" the coercion, e.g.,
calling it on each chunk of an iterative read operation.
The implementation needs work though, and I'm not convinced that coercion
failures should fallback gracefully to the default.
Feature requests
2019 Mar 28
0
[RFC] readtable enhancement
Hey,
In the meantime, I submitted a bug. Thanks for the assistence on that.
> and I'm not convinced that
> coercion failures should fallback gracefully to the default.
the gracefull fallback:
- makes the code more complex
+ keeps colConvert implementations limited
+ requires the user to only implement what changed from the default
+ seemed to me to smallest overall effort
In my
2019 Mar 28
0
[RFC] readtable enhancement
On wo, 27 mrt 2019 22:55:06 -0700, Gabriel Becker wrote:
> Kurt,
> Cool idea and great "seeing new faces" on here proposing things on here
> and engaging with R-core on here.
> Some comments on the issue of fallbacks below.
> On Wed, Mar 27, 2019 at 10:33 PM Kurt Van Dijck
> <[1]dev.kurt at vandijck-laurijssen.be> wrote:
>
> Hey,
>
2019 Mar 26
2
[PATCH 1/2] readtable: add hook for type conversions per column
You need admin assistance, someone will probably see your request here
and fulfill it.
It might be helpful to read this question/answer on StackOverflow
discussing the context of proposing patches to base R functionality ...
https://stackoverflow.com/questions/8065835/proposing-feature-requests-to-the-r-core-team
cheers
Ben Bolker
On 2019-03-26 4:20 p.m., Kurt Van Dijck wrote:
> On
2019 Mar 26
3
[PATCH 1/2] readtable: add hook for type conversions per column
Please file a bug on bugzilla so we can discuss this further.
On Tue, Mar 26, 2019 at 11:53 AM Kurt Van Dijck <
dev.kurt at vandijck-laurijssen.be> wrote:
> Hello,
>
> I want to find out if this patch is ok or not, and if not, what should
> change.
>
> Kind regards,
> Kurt
>
> ______________________________________________
> R-devel at r-project.org mailing
2012 Dec 11
0
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi again,
I can confirm r169783 fixes the problem. My testbench segfaulted in r169782
but works after your commit.
We can close the issue.
Thanks,
Carlos
2012/12/11 Carlos Sánchez de La Lama <csanchezdll at gmail.com>
> Hi Anshu,
>
> I got a testbench which fails (and segfaults) consistently with an
> environment (gcc + os) conveniently preserved in a virtual machine. I
2012 Dec 10
0
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Carlos,
I committed a fix in r169783. Thanks for catching this.
However, I could not reproduce an invalid read or a segfault even with
fadd.ll. Is there a test case you can check in that reproduces this bug?
Even if the segfault occurs intermittently, that's better than no test
case at all.
Thanks
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by
2012 Dec 10
0
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi Carlos,
Thanks for identifying the bug. I'll confirm and fix. Is there a bug
report open for this?
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
On 12/10/2012 4:48 AM, Carlos Sánchez de La Lama wrote:
> Hi all,
>
> I have found what I think it is a bug in DFAPacketizer::ReadTable.
>
> When finding
2012 Dec 10
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi all,
I have found what I think it is a bug in DFAPacketizer::ReadTable.
When finding NextStateInTable to cache all transitions belonging to a state
into CachedTable, ReadTable does not check bounds:
unsigned ThisState =
DFAStateEntryTable[state];
|
unsigned NextStateInTable = DFAStateEntryTable[state+1];
which makes NextStateInTable get a random value when state == <last state
in
2012 Dec 11
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi Anshu,
I got a testbench which fails (and segfaults) consistently with an
environment (gcc + os) conveniently preserved in a virtual machine. I will
confirm that it is gone there and report.
Thanks for the fix :)
Carlos
2012/12/10 Anshuman Dasgupta <adasgupt at codeaurora.org>
> Carlos,
>
> I committed a fix in r169783. Thanks for catching this.
>
> However, I could
2012 Dec 10
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi Anshu,
no, I did not fill a bug report. It is not so easy to make the code fail
noticeably; during Hexagon CodeGen tests it happens silently and tests
pass. I am working on another VLIW backend which uses DFAPacketizer and
compiling llvm with gcc-4.4 makes it segfault, but with gcc-4.7 the bug
gets hidden again (it still happens, but values after DFAStateEntryTable in
memory are such that
2019 Mar 27
0
[RFC] readtable enhancement
Thank you for your answers.
I rather do not file a new bug, since what I coded isn't really a bug.
The problem I (my colleagues) have today is very stupid:
We read .csv files with a lot of columns, of which most contain
date-time stamps, coded in DD/MM/YYYY HH:MM.
This is not exotic, but the base library's readtable (and derivatives)
only accept date-times in a limited number of possible
2020 Jan 23
2
Centos 7 32 Bits install. Answer to Johnny Hughes.
On Wed, 22 Jan 2020 16:45:02 +0100, Johnny Hughes <johnny at centos.org>
wrote:
> On 1/12/20 9:54 AM, Ger van Dijck wrote:
>>
>> Hi all,
>>
>>
>>
>> Question : Can I install Centos7 32 Bits on a computer i386 32 bits
>> little indian pentium III Copermine Model8 Cpufamily 6 CpuMhz 863.979
>> (lscpu) grep -i pae /proc/cpuinfo gives a flag
2019 Nov 27
7
Upgrade Centos 6 (32 Bits) to Centos 7 (32 Bits)
Hi all ,
I have a very old PC ( Acer2000) 32 Bits. On this machine I am running (Do
not laugh) SCO Unix in an antique version : So Centos6 probes with the
bootloader on this OS and other OS s.
Is there a way to opgrade Centos 6 to Centos 7 in the 32 Bits architecture
?
Any help would be usefull.
Regards.
Ger van Dijck.
--
Using Opera's mail client:
2018 Mar 18
3
Upgrade Centos 6 to Centos 7 32 Bits i686 architecture.
Hi ,
I am running Centos 6 on an old Acer S2000 PC 1Mb memory and i686 32 bits
architecture.
Question : Is there a possibility to upgrade to Centos 7 32 bits ?
Regards ,
Ger van Dijck.
--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
2019 Nov 27
2
Upgrade Centos 6 (32 Bits) to Centos 7 (32 Bits)
On Wed, Nov 27, 2019 at 6:31 AM Mauricio Tavares <raubvogel at gmail.com>
wrote:
> On Wed, Nov 27, 2019 at 9:18 AM Ger van Dijck <ger.vandijck at edpnet.be>
> wrote:
> >
> > Hi all ,
> >
> >
> >
> >
> > I have a very old PC ( Acer2000) 32 Bits. On this machine I am running
> (Do
> > not laugh) SCO Unix in an antique version : So
2019 Jan 02
1
Problem Webinstall Centos 7 on Acer S2000 32 Bit.
Hi Centos World ,
I am trying to install Centos 7 (i686) on an Acer 2000 PC and I get
following message(s) :
[0117110] ACPI : SCI (ACPI GSIG) not registered .
[26.532360] systemd [1] : caught <ILL> , dumped core as pid 76.
[26.532956] systemd [1] : Freezing execution.
My question is : What is wrong and how can I solve this problem ?
Maybe a fresh
2020 Jan 12
5
Centos 7 32 Bits install.
Hi all,
Question : Can I install Centos7 32 Bits on a computer i386 32 bits little
indian pentium III Copermine Model8 Cpufamily 6 CpuMhz 863.979 (lscpu)
grep -i pae /proc/cpuinfo gives a flag pae .
I am very curieus,
Ger van Dijck.
--
Using Opera's mail client: http://www.opera.com/mail/
2017 Jul 05
4
Help with reshape/reshape2 needed
Hi all:
I'm struggling with getting my data re-formatted using functions in
reshape/reshape2 to get from:
1957 0.862500000
1958 0.750000000
1959 0.300000000
1960 0.287500000
1963 0.675000000
1964 0.937500000
1965 0.025000000
1966 0.387500000
1969 0.087500000
1970 0.275000000
1973 0.500000000
1974 0.362500000
1976 0.925000000
1978 0.712500000
1979 0.337500000
1980 0.700000000
1981 0.425000000