search for: intervals

Displaying 20 results from an estimated 7685 matches for "intervals".

Did you mean: interval
2007 Jun 01
0
Branch 'as' - 2 commits - libswfdec/Makefile.am libswfdec/swfdec_as_strings.c libswfdec/swfdec_as_types.c libswfdec/swfdec_interval.c libswfdec/swfdec_interval.h libswfdec/swfdec_player_as.c libswfdec/swfdec_player.c
...++------------------------------ 7 files changed, 320 insertions(+), 132 deletions(-) New commits: diff-tree 89c4d90d1c31e4bba4b15f8419f7ebd13cd6cbb8 (from 4576fa2edfba68cb8edc199287ecf773a09cc7df) Author: Benjamin Otte <otte at gnome.org> Date: Fri Jun 1 21:32:43 2007 +0200 reenable intervals setInterval and clearInterval should work now diff --git a/libswfdec/Makefile.am b/libswfdec/Makefile.am index d9b7b68..d701d51 100644 --- a/libswfdec/Makefile.am +++ b/libswfdec/Makefile.am @@ -80,6 +80,7 @@ libswfdec_ at SWFDEC_MAJORMINOR@_la_SOURCES swfdec_graphic_movie.c \ swfdec_...
2006 Apr 10
7
te110p and interrupts
Guys. I have an issue with a te110p card and also some tdm04b cards on the same system: Zttest returns this for the tdm04b cards: [root@mollendo ~]# /usr/src/zaptel-1.2.4/zttest 38 -v Opened pseudo zap interface, measuring accuracy... 8192 samples in 8191 sample intervals 99.987793% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8223 sample intervals 99.621582% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8191 sample intervals 99.987793% 8192 samples in 8192 sample intervals 10...
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
Hi, I wrote a Function pass that requires the IntervalPartition pass in order to obtain the set of intervals for every function: virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.addRequired<IntervalPartition>(); } and get a handle to it in the runOnFunction method of my CustomPass: bool CustomPass::runOnFunction(Function& F) { IntervalPartition& iPart = getAnalysis<...
2012 Nov 30
1
help on "stacking" matrices up
...esents time in hours), and then each "segments" of the matrix  would  be added to the sum of the previous ones at a specific moment in time. Assuming a much shorter example this is what it should be like where according to the same equations above each value of CONCi was calculated at 1 h intervals: INTERVAL <=3 time points here where the values are calculated is 0:(3*INTERVAL) for CONC1, 0:(2*INTERVAL) for CONC2, and 0:(1*INTERVAL) for CONC3, all calculated at 1 hour intervals   and lets assume calculated values are:   CONC1 <-c(0,1,2,3,4,5,6,7,8,9) CONC2 <-c( 11,12,13,14,15,16,17)...
2007 Aug 06
4
[LLVMdev] Spillers
On Monday 06 August 2007 12:15, Anton Vayvod wrote: > Spill intervals must be precolored because they can't be spilled once more. > They are the shortest intervals precisely over each def/use of the original > interval. That is why they also have their weights set to #INF. Yes, that's true. But I wonder if we shouldn't be smarter about which regis...
2007 Aug 07
0
[LLVMdev] Spillers
On 8/7/07, David Greene <dag at cray.com> wrote: > > On Monday 06 August 2007 12:15, Anton Vayvod wrote: > > > Spill intervals must be precolored because they can't be spilled once > more. > > They are the shortest intervals precisely over each def/use of the > original > > interval. That is why they also have their weights set to #INF. > > Yes, that's true. But I wonder if we shouldn't...
2001 Feb 27
1
Patch to coplot.R
...|| index == nplots) && ((total.rows - ! i)%%2 == 1)) ! axis(4, xpd = NA) box() } if (have.b) { *************** *** 255,274 **** par(fig = c(0, f.col, f.row, 1), mar = nmar, new = TRUE) plot.new() nint <- nrow(a.intervals) ! pwoffs <- nint / 32 ! plot.window(c(min(a.intervals[is.finite(a.intervals)] + pwoffs), ! max(a.intervals[is.finite(a.intervals)]) - pwoffs), ! 0.5 + c(0, nint), log = "") ! rect(a.intervals[, 1], 1:nint - 0.5, a.inter...
2013 Mar 12
2
split data into columns from dataframe
Dear r-users,   Originally my data is in notepad.  I use data.frame(...) to convert the data into columns but it has no header.  The data below is what I got in R.  I would like to extract these data:   19710629        39.3  19701126  19720629        33.8  19720517 ... when I use data2_30min[1, cbind(1,3,5)] command the result is NULL.   Then I tried data2_30min[1], it gives me the whole set of
2011 Nov 13
0
Major opcode of failed request: 93 (X_CreateCursor)
Hi, I got selected for beta testing SW:TOR and managed to get the installer to work on wine but it keeps crashing when I try with the launcher. It opens for a smidgen then crashes. Here's all the script I get; fixme:iphlpapi:NotifyAddrChange (Handle 0x32e604, overlapped 0x8f8d58): stub fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:winsock:WSALookupServiceBeginW (0x32e628
2003 Mar 06
0
loop avoiding on time interval intersects
I am trying to optimize some code to take advantage of R loop-avoiding capabilities when working on vectors/arrays that contain time intervals. The calculation involves adding (for each time interval) the time portion (of events defined by their start and end times) that elapsed during time intervals. Any advice on how to improve this code. I searched the email archive and looked at the MASS book but did not find anything specific that...
2024 Aug 14
2
[Bug 1764] New: mapping IPv4 interval to IPv4 interval works for anonymous maps, but not for named maps
https://bugzilla.netfilter.org/show_bug.cgi?id=1764 Bug ID: 1764 Summary: mapping IPv4 interval to IPv4 interval works for anonymous maps, but not for named maps Product: nftables Version: git (please specify your HEAD) Hardware: x86_64 OS: All Status: NEW Severity: enhancement
2008 Feb 21
2
[LLVMdev] Bug? Coalescing & Updating Subreg Intervals
...wrote: > >> I discovered this through an assert I put into some of my own >> code. I want >> to know if that assert is bogus or if there's a bug here. > > A little more information: the assert checks that after coalescing > two nodes, > all subregister live intervals for the register coaelsced to now > interfere > with whatever the eliminated live interval interfered with, since the > superregister live interval now contains information from the > eliminated live > interval and thus it interferes with whatever the eliminated live > inter...
2012 May 15
2
pass objects into "..." (dot dot dot)
...common separation (like "x,y,z" when x, y and z are objects to be passed into "...")? Details: I'm working with this parameter list and function: interval_intersection(x, ..., check_valid = TRUE) To illustrate... This works and I get the expected interval: library('intervals') # create individual Intervals objects z = Intervals(c(1,10)) y = Intervals(c(5,10)) x = Intervals(c(4,6)) > interval_intersection(x,y,z) Object of class Intervals 1 interval over R: [5, 6] ...but at run time I don't know how many Intervals objects I will have so I can't list them...
2008 Feb 20
0
[LLVMdev] Bug? Coalescing & Updating Subreg Intervals
...nesday 20 February 2008 14:14, David Greene wrote: > I discovered this through an assert I put into some of my own code. I want > to know if that assert is bogus or if there's a bug here. A little more information: the assert checks that after coalescing two nodes, all subregister live intervals for the register coaelsced to now interfere with whatever the eliminated live interval interfered with, since the superregister live interval now contains information from the eliminated live interval and thus it interferes with whatever the eliminated live interval interfered with (and thuis s...
2007 Aug 07
2
[LLVMdev] Spillers
...August 2007 05:00, Anton Vayvod wrote: > > Yes, that's true. But I wonder if we shouldn't be smarter about which > > register we pick to color it. In Bill W's implementation, it was > > essentially random. What was your solution to this? > > I allocated spill intervals at the beginning of each iteration so all the > rest intervals (except of physreg intervals) were uncolored at the moment. > So the only difference in allocating regs for spills was what end to > choose: allocation_order_begin() or allocation_order_end(), I chose the > former. I underst...
2004 Oct 15
1
se.fit from predict.lm
hi, i noticed that se.fit from predict.lm is the same whether interval="conf" or interval="pred". it is not clear to me from ?predict.lm whether this is intended or not. i suggest that se.fit should match the type of interval requested, if interval is specified. suggested change in lm.R line 700 if(se.fit || interval != "none") se <- sqrt(ip) to if(se.fit
2018 Apr 17
2
Time intervals in a datframe
...column using "lubridate" package. I needed to convert my list of dataframes to be in a single dataframe for further analysis. I did this using the following syntax : SingleDataframe <- ldply (MylistofDFs,data.frame) The problem is that after this conversion, the the column with time intervals has been converted into numeric type with number of seconds during the time interval instead of the interval itself as follows : The column Before conversion looks like this: TimeInterval (class 'interval') 2012-12-13 UTC--2016-02-16 UTC but after conversion the list into dataframe, This...
2013 Jan 13
1
Extract data in word pad
Dear r-users,   I have saved data in word pad.  I would like to extract certain part of data only, for example   19710629 080000(PARTIAL) 39.3 at interval beginning 19701126 010326 19720629 080000(PARTIAL) 33.8 at interval beginning 19720517 144507 19730629 080000(PARTIAL) 32.2 at interval beginning 19720910 135747   and so on...   The original data set are given below:      
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
Hi Chris, Thanks for the reply. I am actually interested in using the Intervals Analysis mainly to be able to do Region based analysis. In fact, I found that the way Intervals are defined mirror exactly the definition of a Region in the second edition of the Dragon Book (Section 9.7 on Region-Based Analysis), so it will be great if the Intervals related code still lives on in...
2007 Aug 06
0
[LLVMdev] Spillers
Hi, David. Spill intervals must be precolored because they can't be spilled once more. They are the shortest intervals precisely over each def/use of the original interval. That is why they also have their weights set to #INF. Imagine that on a second iteration allocation algorithm figures out that some spilled interval...