search for: subregions

dear all, i'm just about to do some straightforward contingency tables using ftables (and ctab() for percents). the problem: factor "a" are regions, factor "b" are subregions. every region "a" consists of some subregions "b", but obviously not every subregion "b" is part of every region "a". if i use the ftable() function, the table contains a lot of zero rows which i don't want in my output. minimal example: a <- c(1,1,...

Hi, Im trying to thumbnail a swf file based on this found at http://www.mail-archive.com/swfdec at lists.freedesktop.org/msg00821.html. #include <stdlib.h> #include <stdio.h> #include <swfdec/swfdec.h> #include <cairo.h> void swfdec_player_save (SwfdecPlayer *player, guint width, guint height, const char *filename) { cairo_surface_t *surface; cairo_t *cr;

...but here goes. I have a data frame with 2 geographical factors. One is the major region the other is the component regions. I am trying to process all the regions at the same time without using "for". So I need (think, I do) a list of matrices each structured according to the number of subregions within each region. So is there a way of using lapply with xtabs or is there a better way to achieve my desired output? Using the Titanic data as an example t1 <- as.data.frame(Titanic) t2 <- split(t1,t1$Class) # I would then drop any unused levels in the factors for the geography creatin...

...mportant part is that dropping the metadata, and moving instructions to which that metadata is attached, must not cause miscompiles. For example: - Instructions with unknown side effects or dependencies must not be moved from outside a parallel region to inside a parallel region. - Serialized subregions inside of parallel regions cannot be deleted without deleting the enclosing parallel region. The outstanding proposals have ways of dealing with these things. In the case of my proposal, it is though cross-referencing the metadata sufficiently and using function boundaries to prevent unwanted c...

...> I got a bit confused there, TBH. How do you guarantee that that part > of memory will be allocated? On 32-bit, the shadow region is: [0x28000000, 0x3fffffff]HighShadow[0x24000000, 0x27ffffff]ShadowGap[0x20000000, 0x23ffffff]LowShadow This is 0.5G total. So, I mmap all these three shadow subregions and 'mprotect' the ShadowGap. This is done at startup. If the mmap fails, an assert will fire. On 64-bit, the shadow looks like this: [0x0000140000000000, 0x00001fffffffffff]HighShadow[0x0000120000000000, 0x000013ffffffffff]ShadowGap[0x0000100000000000, 0x000011ffffffffff] LowShadow This...

On Mon, Oct 1, 2012 at 9:26 PM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 1, 2012, at 6:16 PM, greened at obbligato.org wrote: > >> Sanjoy Das <sanjoy at playingwithpointers.com> writes: >> >>> In short, I propose a intrinsic based approach which hinges on the >>> concept of a "parallel map". The immediate effect of using

Hello, I am trying to run an ordinal logistic regression (polr) using the package 'MASS'. I have successfully run other regression classes (glm, multinom) without much problem, but with the 'polr' class I get the following error: " Error in svd(X) : infinite or missing values in 'x' " which appears when I run the "summary" command. The data file is

...ing > the metadata, and moving instructions to which that metadata is > attached, must not cause miscompiles. For example: > > - Instructions with unknown side effects or dependencies must not be > moved from outside a parallel region to inside a parallel region. > - Serialized subregions inside of parallel regions cannot be deleted > without deleting the enclosing parallel region. > > The outstanding proposals have ways of dealing with these things. In > the case of my proposal, it is though cross-referencing the metadata > sufficiently and using function boundari...

...t use a function call. Much simpler for > documentation purposes. Sounds good. On 32-bit, the shadow region is: > [0x28000000, 0x3fffffff] HighShadow [0x24000000, 0x27ffffff] ShadowGap [0x20000000, > 0x23ffffff] LowShadow > > This is 0.5G total. So, I mmap all these three shadow subregions and > 'mprotect' the ShadowGap. > This is done at startup. If the mmap fails, an assert will fire. > I see. On embedded platforms that won't work with all cases. Most implementations have fragmented memory, memory mapped I/O, secure zones, etc. Depending on what you're tr...

...me kind of nested structures, so both a loop and a region could have parent or childrens 3. both of them have a BasicBlocks(header of a loop and "entry" of a region) that dominates all others and the Region class will have the most stuffs very similar in LoopBase, like: ParentRegion, SubRegions, Blocks, getRegionDepth(), getExitBlock(), getExitingBlock() ...... so, could us just treat "Loop" as some kind of general "Region" of BasicBlocks, and make Loop and Region inherit from "RegionBase"? [1] http://llvm.org/doxygen/LoopInfo_8h-source.html best regard...

...ping > the metadata, and moving instructions to which that metadata is > attached, must not cause miscompiles. For example: > - Instructions with unknown side effects or dependencies must not be > moved from outside a parallel region to inside a parallel region. > - Serialized subregions inside of parallel regions cannot be deleted > without deleting the enclosing parallel region. > > The outstanding proposals have ways of dealing with these things. In > the case of my proposal, it is though cross-referencing the metadata > sufficiently and using function boundari...

Hi Hal, > My rationale for proposing the self-consistent metadata solution was > that it seemed to be the safest option. If we simply insist that all > relevant passes use the ParallizationMetadata pass, without any > verification, then we could end up with parallelization-unaware passes > silently miscompiling code when parallelization is enabled. Do you have > a way of

...res, so both a loop and > a region could have parent or childrens > 3. both of them have a BasicBlocks(header of a loop and "entry" of a > region) that dominates all others > > and the Region class will have the most stuffs very similar in LoopBase, > like: ParentRegion, SubRegions, Blocks, getRegionDepth(), > getExitBlock(), getExitingBlock() ...... > > so, could us just treat "Loop" as some kind of general "Region" of > BasicBlocks, and make Loop and Region inherit from "RegionBase"? > > > [1] http://llvm.org/doxygen/LoopIn...

...ite and size is encoded in the function name --kcc > > > On 32-bit, the shadow region is: >> [0x28000000, 0x3fffffff] HighShadow [0x24000000, 0x27ffffff] ShadowGap [0x20000000, >> 0x23ffffff] LowShadow >> >> This is 0.5G total. So, I mmap all these three shadow subregions and >> 'mprotect' the ShadowGap. >> This is done at startup. If the mmap fails, an assert will fire. >> > > > I see. On embedded platforms that won't work with all cases. Most > implementations have fragmented memory, memory mapped I/O, secure zones, > e...

Hello R community, I am attempting to run multiple logistic regressions (multinomial, via package 'nnet'), with Automated Model Selection (dredge, package 'MuMIn'). The aim is to reduce the number of predictor variables by assessing relative performance of each variable, which can be done in a coarse fashion using the Automated Model Selection option in package 'MuMIn'

...ta, and moving instructions to which that metadata is >> attached, must not cause miscompiles. For example: >> >> - Instructions with unknown side effects or dependencies must not be >> moved from outside a parallel region to inside a parallel region. >> - Serialized subregions inside of parallel regions cannot be deleted >> without deleting the enclosing parallel region. >> >> The outstanding proposals have ways of dealing with these things. In >> the case of my proposal, it is though cross-referencing the metadata >> sufficiently and usin...

...e interpreted. These profiles are attached to windows so that the compositing manager can get them and do the necessary color conversion. To allow for fine-grained color management (if an application has only a region that it wants to have color managed), the applications have to be able to specify subregions of their window and attach profiles to that. Since toolkits (at least GTK+) already make heavy use of subwindows, using those makes sense to me. So I came up with a document (in the attachment) that describes which window properties and messages are used. Dennis Kasprzyk (compiz developer) wasn...

hi, i'm trying to perform a clustering on a big dataframe the code is this: print("load required R packages") require(spgrass6) require(cluster) gmeta6 <- gmeta6() print("read in our 7 raster files from GRASS") x <- readFLOAT6sp(c ("er","crosc","longc","slope","profc","minic","maxic"))

On Thu, 13 Sep 2012 09:01:18 +0530 Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Hi Hal, > > > My rationale for proposing the self-consistent metadata solution was > > that it seemed to be the safest option. If we simply insist that all > > relevant passes use the ParallizationMetadata pass, without any > > verification, then we could end up with

On Tue, 11 Sep 2012 01:21:59 +0530 Sanjoy Das <sanjoy at playingwithpointers.com> wrote: Sanjoy, Thanks for working on this! Comments below... > Hi all, > > I made some progress on implementing Hal's proposal [1] for > implementing OpenMP support in LLVM. The patch I've attached just > barely compiles, but I'd like to get some input on the design early on >