similar to: Performance problems

Has anyone here done this? I got it compiled just fine but when I make a call I do not get any audio going either way. The * box is not behind any sort of firewall or nat. My H323 client (gnomemeeting) is behind NAT but I have it set up properly to work through NAT and it will talk correctly with my other regular x86 box running H323. One odd thing I note is that when looking at the UDP traffic

To summarise this thread, there are basically three ways of handling int64 in R: * coerce to character * coerce to double * store in double There is no ideal solution, and each have pros and cons that I've attempted to summarise below. ## Coerce to character This is the easiest approach if the data is used as identifiers. It will have some performance drawbacks when loading and will

Hi, I do have < INT_MAX. This looks attractive but since they are unique identifiers, storing them as factor will be likely to be counter-productive. (a string version + an int32 for each) I was looking to https://cran.r-project.org/web/packages/csvread/index.html This looks like a good feet for my needs. Any chances such an external package for int64 would be integrated in core ? Le 20

Well I definitely cannot use them as numeric because join is the main reason of those identifiers. About int64 and bit64 packages, it's not a solution, because I am releasing a dataset for external users. I cannot ask them to install a package in order to exploit them. I have to be very carefull when releasing the data. If a user just use read.csv functions, they by default cast the

Gracias Carlos, Me lo ha solucionado, pero.. ¿Por que es necesario instlara ese paquete? Un saludo Jesús ________________________________ De: Carlos Ortega <cof en qualityexcellence.es> Enviado: viernes, 6 de octubre de 2017 14:51 Para: Jesús Para Fernández Cc: r-help-es en r-project.org Asunto: Re: [R-es] Importando mal los datos Instala el paquete "bit64".... Saludos, Carlos

Dear package maintainers, Dear users of packages `bit`, `bit64`, `ff`, Everyone interested in sustainable sorting algorithms, I submitted updated versions for the upcoming R 4.5.0. The are only minor changes (see the NEWS files) but there is one important change in bit64: ??? o setting options(integer64_semantics="new") ????? gives the better semantics suggested by Ofek Shilon.

Dear package maintainers, Dear users of packages `bit`, `bit64`, `ff`, Everyone interested in sustainable sorting algorithms, I submitted updated versions for the upcoming R 4.5.0. The are only minor changes (see the NEWS files) but there is one important change in bit64: ??? o setting options(integer64_semantics="new") ????? gives the better semantics suggested by Ofek Shilon.

Dear R Developers, I would like to pick up back again the issue of 64 bits integers with R: http://r.789695.n4.nabble.com/Re-R-support-for-64-bit-integers-td2320024.html *** CURRENT SITUATION *** At the moment, as regards integers, all the following are the same type: * length of an R vector * R integer type * C int type (Fixed at 32 bits: In practice) * Fortran INTEGER type (Fixed at 32

Dear R-Core team, Dear Rcpp team and other package teams, Dear R users, The new package 'bit64' is available on CRAN for beta-testing and code-reviewing. Package 'bit64' provides fast serializable S3 atomic 64bit (signed) integers that can be used in vectors, matrices, arrays and data.frames. Methods are available for coercion from and to logicals, integers, doubles,

Dear R-Core team, Dear Rcpp team and other package teams, Dear R users, The new package 'bit64' is available on CRAN for beta-testing and code-reviewing. Package 'bit64' provides fast serializable S3 atomic 64bit (signed) integers that can be used in vectors, matrices, arrays and data.frames. Methods are available for coercion from and to logicals, integers, doubles,

We are in urgent need of some help getting Asterisk to gateway between an incoming H323 connection and SIP to a Lucent TNT. We have the incoming H323 already set up and the SIP going to the TNT but the media stream is getting lost somewhere as no audio is heard. We are willing to pay $$$ for an extra set of eyes to get this resolved fast. It's probably something quick and easy and we are just

Dear R community, The new version of package 'bit64' - which extends R with fast 64-bit integers - now has fast (single-threaded) implementations of the most important univariate algorithmic operations (those based on hashing and sorting). Package 'bit64' now has methods for 'match', '%in%', 'duplicated', 'unique', 'table',

Dear R community, The new version of package 'bit64' - which extends R with fast 64-bit integers - now has fast (single-threaded) implementations of the most important univariate algorithmic operations (those based on hashing and sorting). Package 'bit64' now has methods for 'match', '%in%', 'duplicated', 'unique', 'table',

Hello all. I'm new to asterisk and have been using and testing it for about a week now. My initial hope has been to use it as a sip<->h323 gateway to tie SIP & H323 based ip phones together with my Cisco AS5300 and Lucent MaxTNT/MVAM networks. I am currently running Asterisk 0.5.0 under Redhat 9 on a single PIII 800 with 256megs RAM. I have tried a couple CVS version from the past

Entendido... El otro dia lei un artículo sobre el efecto 2031 que versaba justo sobre eso.... Una duda mas. En la columna ID hay alguna fila que esta mal metida y tiene un caracter o algo que esta hacinedo que toda esa columna me la importe como un factor y no como un numero. ¿Como detecto esas filas que me están jo...? Gracias Carlos!!! ________________________________ De: Carlos Ortega <cof

Hello r users, I have to deal with int8 data with R. AFAIK R does only handle int4 with `as.integer` function [1]. I wonder: 1. what is the better approach to handle int8 ? `as.character` ? `as.numeric` ? 2. is there any plan to handle int8 in the future ? As you might know, int4 is to small to deal with earth population right now. Thanks for you ideas, int8 eg: human_id

Thank you Martin for giving to know and developing 'Rmpfr' library for unlimited size integers (GNU C GMP) and arbitrary precision floats (GNU C MPFR): https://cran.r-project.org/package=Rmpfr My question is: In the long term (For R3.7.0 or R3.8.0): Does it have sense that CMP substitutes INTSXP, and MPFR substitutes REALSXP code? With this we would achieve that an integer is always an

Buenas chicos, Estoy intentando importar el csv que adjunto y que tiene la siguietne forma: "a";"b" 11092740;0 8978056137;0 Usando la funcion fread. Necesito usar la función fread por velocidad (lo que envio es un ejemplo simplificado pero que replica el error). El problema es que al importar los datos, usando: datos<-fread(datos.csv,sep=";") el campo a no lo

Dear list, During the last two months, I spent a lot of time trying to remove the following warnings of my package randtoolbox: congruRand.c:180:3: warning: ISO C does not support the 'I64' ms_scanf length modifier [-Wformat=] sscanf(params[0], "%" PRIu64 "\n", &inp_mod); Please see

How many unique idenfiiers do you have? If they are large (in terms of bytes) but you don't have that many of them (eg the total possible number you'll ever have is < INT_MAX), you could store them as factors. You get the speed of integers but the labeling of full "precision" strings. Factors are fast for joins. ~G On Fri, Jan 20, 2017 at 9:47 AM, Nicolas Paris