search for: tess

...uveau/nvc0/nvc0_context.h index 09d08e4..f910541 100644 --- a/src/gallium/drivers/nouveau/nvc0/nvc0_context.h +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_context.h @@ -195,8 +195,8 @@ nvc0_shader_stage(unsigned pipe) { switch (pipe) { case PIPE_SHADER_VERTEX: return 0; -/* case PIPE_SHADER_TESSELLATION_CONTROL: return 1; */ -/* case PIPE_SHADER_TESSELLATION_EVALUATION: return 2; */ + case PIPE_SHADER_TESS_CTRL: return 1; + case PIPE_SHADER_TESS_EVAL: return 2; case PIPE_SHADER_GEOMETRY: return 3; case PIPE_SHADER_FRAGMENT: return 4; case PIPE_SHADER_COMPUTE: return 5; --...

...in spatstat. Now I have point data of class "ppp" which window is the same extent as the elevation image. I can conveniently plot the image and the points on the image as follows: >plot(elevation, axes=T, col=terrain.colors(20)) >plot(points, add=T, cex=0.5) I have also created a tessellation of the elevation image into 4 categories as follows: >elev.cut<-cut(elevation.im, breaks=elev.quantiles, labels=c("Very low","Low","High","Very High")) >elev.tess<-tess(image=elev.cut) I would like to do a quadrat count to know how many...

...in spatstat. Now I have point data of class "ppp" which window is the same extent as the elevation image. I can conveniently plot the image and the points on the image as follows: >plot(elevation, axes=T, col=terrain.colors(20)) >plot(points, add=T, cex=0.5) I have also created a tessellation of the elevation image into 4 categories as follows: >elev.cut<-cut(elevation.im, breaks=elev.quantiles, labels=c("Very low","Low","High","Very High")) >elev.tess<-tess(image=elev.cut) I would like to do a quadrat count to know how many...

...stat) data01 <- read.csv("250810.csv", skip=1) x <- data01[[2]] y <- data01[[3]] data02 <- ppp(x, y, xrange=c(0,512), yrange=c(0,512)) unitname(data02) <- c("pixel", "pixels") plot(data02) #etc etc #I can also import my text images and convert them to a tessellation using the following: a <- read.table("FOLLICLES.txt") win <- owin(c(0,512), c(0,512)) unitname(win) <- c("pixel", "pixels") b <- as.matrix(a, xrange=c(0,512), yrange=c(0,512)) unitname(b) <- c("pixel", "pixels") c <- im(b...

...;TrlgR2","TrlgR2adj","TrSSE","TrMSE","TrR2","TrR2adj","rdf2", "TelgSSE","TelgMSE","TelgR2","TelgR2adj","TelgWSSE","TelgWMSE" ,"TelgWR2","TelgWR2adj","TeSSE","TeMSE","TeR2","TeR2adj","edf2","Runtime") Asse <- matrix(0,nrow=5,ncol=length(namVar)) Asse[,1:3]<-2 Asse[2,4] <-2000 Asse[,5:10]<-3 Asse[,11:20]<-5 Asse[,21:30]<-12 if(all(Asse[,"SSdiff"]==0)==TRUE){ Asse <- A...

...9;'t see much about it. I have been searching the web for about 5 hours and I can''t seem to find a good, advanced tutorial on the latest trends in testing. Everything is either outdated or very simplistic. Does anyone know where I might find good testing What are you using? Test::Unit Tess::Rails Selenium Something new that I don''t know about Thanks in adavnce --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-...

Hello, I want to instal a normal windows-programm from http://www.tess-kom.de:8080/ with wine, but its not working. Error message: > > the program calcs could not execute > regards manu

I do the these passages: library(Geneland) set.seed(1) data <- simdata(nindiv=200, coord.lim=c(0,1,0,1) , number.nuclei=5 , allele.numbers=rep(10,20), IBD=FALSE, npop=2, give.tess.grid=FALSE) geno <- data$genotypes coord <- t(data$coord.indiv) path.mcmc <- paste(tempdir(),"/",sep="") set.seed(1) mcmcFmodel(coordinates=coord, genotypes=geno, path.mcmc=path.mcmc, rate.max=10, delta.coord=0,...

This is enough to enable tessellation support on nvc0. It seems to work a lot better on my GF108 than GK208. I suspect that there's some sort of scheduling shenanigans that need to be adjusted for kepler+. Or perhaps some shader header things. Even with the GF108, I still get occasional blue triangles in Heaven, but I get...

...n respect of your last point: Rather than "M <- union.owin(windows)" you should use: M <- do.call(union.owin, windows) But that's rather off the track. What I think you should do (it's hard to be certain without a reproducible example) is something like: tw <- tess(tiles=windows) iw <- as.im(funxy(as.function(tw,values=vvv),W=Window(tw)),dimyx=128) where "vvv" is a vector of the values that you wish to associate with the individual polygons. There may be less cryptic ways of accomplishing the same thing, but this is the sexiest way, I think....

Dear all, I am currently working with the spatstat package, using windows and pixel images. First: My aim is to transform a shapefile (see attached) into a pixel image. My idea is to start transforming the shapefile into a Spatial Polygon file: x <- readShapeSpatial("200001441.shp") y <- as(x, "SpatialPolygons") z <- as.owin(y) Given z, I want to identify each

For "importance" it's probably best to stick with absolute values of coefficients, instead of value of the penalty parameter for which the coefficients changed to non-zero. Friedman skipped a lot of details on his rule ensemble in that talk, due to time constraint. In his implementation he was using his own algorithm, PathSeeker, for which paper and software are available on his

...like to be able to colour the quadrats by the number of points/events each contains, rather than by their identity. Anyone run into this? It seems like an obvious request, maybe I just haven't spotted the necessary option, although I think maybe not - it's something to do with how plot.tess() works. Thanks David -- David O'Sullivan Associate Professor of Geography University of Auckland | Te Whare Wananga o Tamaki Makaurau http://www.sges.auckland.ac.nz/the_school/our_people/osullivan_david/index.shtm

...;t need the NDA. > > - Matt > > -- > Sure, it''s possible to write C in an object-oriented way. But, in practice, > getting an entire team to do that is like telling them to walk along a > straight line painted on the floor, with the lights off. > -- Tess Snider, slug-chat at slug.org.au > _______________________________________________ > Puppet-users mailing list > Puppet-users at madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >

...y <- c(0,radius*sin(theta),0) W <- owin(poly=list(x=x,y=y)) return(affine(W,vec=centre)) } Then do something like: wedgies <- vector("list",length=8) cntr <- c(673593.21,673593.21) for(i in 1:8) wedgies[[i]] <- wedge((i-1)*pi/4,i*pi/4,15,centre=cntr) ttt <- tess(tiles=wedgies) plot(ttt) # Looks OK to me. And maybe also do: W <- do.call(union.owin,wedgies) plot(W) for(i in 1:8) { plot(wedgies[[i]],add=TRUE,border="red") readline("Go? ") } Also looks OK to me. Is *this* what you want? cheers, Rolf Turner -- Technical...

Hi I have installed Festival on the same box as asterisk and followed the instructions to integrate it with asterisk. Festival seems to work fine on its own performing text to speech from the command line or via a file. Asterisk answers the call but there is no speech. I can see no errors in the Festival log file The asterisk console shows --Executing Answer("SIP/81801-c091",

Imagine that I have a large number of points (given by coordinates x and y) that vary in density per space. For the purpose of demonstration it could be generated like this: s <- data.frame(x=runif(10000,0,900),y=runif(10000,0,900)); plot(s) I want to create polygons around the points where point density is greater than a selected threshold (for example, by using krieging or equivalent

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

Hello there. Just to let you know i have just put in production mode puppet on 41 freeBSD 4.7 virtual servers (yes not real servers but "jailed ones"). I had some little problems with facter at first but i have manualy upgraded the servers that where affected by the little "facter does not read his facts" problem i had. I should have missed something in my deploiement.

I believe that your problem is this: /*01a0*/ LD R8, [R8]; /* 0x8000000000821c85 */ That needs to be LD.E (and your ST's need to be ST.E). You're using a 32-bit gmem address, but you need to be using a 64-bit one. I believe the 32-bit ones work on fermi, but afaik not on Kepler. Cheers, -ilia On Wed, Dec 16, 2015 at 12:06 PM, Hans de Goede