search for: coarseness

I have two pairs of time intervals: coarse- and fine-grained. They're components of their respective dataframes, looking like, coarse: endtime starttime 1 t1_end t1_start 2 t2_end t2_start ... fine: is the same, except that its intervals presumably fall into the coarse's enclosing ones. The problem is to partition

Hello, Anyone else experiencing problems with the latest spandsp (pre3) and last libtiff beta? I'm getting 8 bytes long file, with the TIFF header only during such connection: -- Accepting call from 'XXXXXXX' to 'YYYYYY' on channel 0/2, span 1 -- Executing SetVar("Zap/2-1", "FAXFILE=/tmp/foch.tif") in new stack -- Executing

Hi all, in order to verify some results I did the following test in R (2.4.1., windows system): X <- cumsum(rnorm(1000000)) for (i in 1:1000) { tmp <- seq(1,length(X),by=i) X.coarse <- X[tmp] X.return <- diff(X.coarse) X.scale.mean[i] <- mean(X.return) } plot(X.scale.mean,type="l") As X is a random walk with

Hello, I found some code within the pool allocation project to identify parallelizable function calls. Unfortunately the functionality isn't part of the current release of poolalloc (in release 14 it was). My intention is to estimate the parallelization-potential of sequential applications concerning coarse-grained parallelism. Can you tell me... 1. Why are classes of pollalloc, like

Hi, I just sent this to Steve Underwood, but then found a bunch of posts on the mailing list about similar issues.. does anyone have the fix? I'm running asterisk CVS-HEAD-06/28/04-18:13:13, spandsp 0.0.1k, libtif 3.5.7 one thing i just noticed is that calls come in with format '72' which is G711A-law or LinearPCM.. it uses PCM for the call, i assume this is ok the results of RxFAX

Hi I try to implement a coarse-grained CFI in LLVM (CFI = Contorl Flow Integrity) I want to collect all address after call instructions address after a call equals to a valid return site in coarse-grained CFI I want to add a new section and write all the possible return address in the new section (and then, add the integrity check) I have some quetions: (1) Which part of LLVM code should

Sorry to bore you more with the clock issue, but have you check /proc/zaptel/<span> to make sure it's not missing interrupts? There's also an option to record the audio for the fax, you could listen to that vs a recorded file that will receive correctly on a fax machine and see whether there is an obvious difference? (Good luck, that'll be really scraping the barrel!!) Does it

Am 22.04.2011 um 18:03 schrieb Tobias Grosser: > On 04/20/2011 08:05 AM, Andreas Wilhelm wrote: >> Am 19.04.2011 um 16:44 schrieb John Criswell: >> >>> On 4/19/11 5:57 AM, Andreas Wilhelm wrote: >>>> Hello, >>>> >>>> I found some code within the pool allocation project to identify >>>> parallelizable function calls.

On 4/19/11 5:57 AM, Andreas Wilhelm wrote: > Hello, > > I found some code within the pool allocation project to identify > parallelizable function calls. > Unfortunately the functionality isn't part of the current release of > poolalloc (in release 14 it was). Can you tell me in what file(s) this is implemented? I wasn't aware that the poolalloc project had such an

Dear Steve after a lot of compile from spanDSP first version to K and after i have compile * HEAD and Stable i cant understand where im wrong... - Mandrake 9.2 - libtiff3-3.5.7-11mdk I have add Header from your FTP but the result is this error.. Can you give me your opinion? Thanks in advance Dimitri -------- -- Executing RxFAX("Zap/35-1", "/home/user/testfax.tif") in

Hi, Several people have reported problems sending faxes from spandsp-0.0.1k to Canon FAX machines. A spandsp user had the same problem with another make of FAX machine, and traced the problem to a bug in the file t30.c of spandsp. Line 542 says s->t4.rx_file[0] where it should say s->t4.tx_file[0]. This fixes his problem, and I suspect it will also fix the Canon fax machine problem.

On 04/20/2011 08:05 AM, Andreas Wilhelm wrote: > Am 19.04.2011 um 16:44 schrieb John Criswell: > >> On 4/19/11 5:57 AM, Andreas Wilhelm wrote: >>> Hello, >>> >>> I found some code within the pool allocation project to identify >>> parallelizable function calls. >>> Unfortunately the functionality isn't part of the current release of

On the /proc/zaptel it was lost interrupts, you haven't got any so that's good! On opencall.org there's a known issues link and that mentions some fax machines that have issues, might be worth a quick check there. I can receive from our fax machine this end, if you'd like I'll send you a test fax if you send me your fax number, if you can receive from us and tpc then it's

Hi, I have successfully compiled spandsp 0.0.2pre10 with * 1.05 which can accept inbound fax calls. However, all fax received are incomplete (the first 10% of an A4 page is fine, the remaining is either missing or garbled). I suspect this is due to 'training error' (see below) which, according to Steve Underwood's postings, cannot be resolved further. I wonder if it would help to

Am 19.04.2011 um 16:44 schrieb John Criswell: > On 4/19/11 5:57 AM, Andreas Wilhelm wrote: >> >> Hello, >> >> I found some code within the pool allocation project to identify parallelizable function calls. >> Unfortunately the functionality isn't part of the current release of poolalloc (in release 14 it was). > > Can you tell me in what file(s) this

Hi all, After a long time having no time, I have finally done some fresh work on my software fax machine. I have replaced the original carrier tracking with something more robust. I have also added 4800, and 2400 bits per second modes, and cleaned up a few bugs in areas like superfine mode operation. I apologise for this update taking so long. At ftp://ftp.opencall.org/pub/spandsp you will

I've been trying to set up incoming faxes using spandsp with a HFC card. Unfortunately, incoming faxes are of very poor quality, the pages are not transferred wholly (sometimes only a bit of a page is transferred etc.). From what I've read, I may have troubles with correct "timing" (and need to set up ztdummy etc.). On the other hand, it is impossible to set ztdummy if one

Hi, so far I had our PRI line connected via Digium TE410P and ZAP channel to asterisk which worked perfectly. I now have a second line coming in through a H.323 gateway and chan_oh323. rxfax() still works and receives faxes with G.711 alaw codec, but I always get one empty first page via H.323 - a one-page-fax becomes a two-page-fax with one empty page in front of it. It seems the empty page

On 10/22/2017 01:20 PM, Tetsuo Handa wrote: > Wei Wang wrote: >> The balloon_lock was used to synchronize the access demand to elements >> of struct virtio_balloon and its queue operations (please see commit >> e22504296d). This prevents the concurrent run of the leak_balloon and >> fill_balloon functions, thereby resulting in a deadlock issue on OOM: >> >>

Shows that as the MCU increases, the OpenMP extra overhead is amortized and OpenMP becomes as fast as the pthreads implementation. The last chart http://lampiao.lsc.ic.unicamp.br/~piga/gsoc_2008/systime.png Shows that both pthreads and OpenMP overhead decreases as what seems to be a logarithmic function of the MCU size. This was a great experiment, and from what I can conclude, the OpenMP