Displaying 4 results from an estimated 4 matches for "pcoord".
Did you mean:
coord
2009 Oct 31
3
Plots with k-means
Hi,
I'm doing a k-means cluster with 6 clusters and 15 variables. Any
suggestions on how to plot the results?
I've tried the standard xy plot, but couldn't get much of it.
Thansk in advance,
Iuri.
2005 Mar 14
1
Significance of Principal Coordinates
...ht <- round(Total/max(Total)*1000)
>
>
> # Calculate Chord Distance
>
> library(vegan)
> Chord <- vegdist(decostand(Data, "norm"), "euclidean")
>
> # Calculate Principal Coordinates, including distance matrix row weights
>
> library(ade4)
> PCoord.Eigen <- dudi.pco(Chord,row.w=Weight,scann=F,full=T)$eig[1:nEigen]
>
> # Randomization of Principal Coordinates Analysis
>
> library(labdsv)
> for (i in 1:99) {
> Data.random <- rndtaxa(Data,species=T,plots=T)
> Total.random <- apply(Data.random,1,sum)
>...
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
...+ if (fp->texcoord[result] == *idx + 8) {
>>
>> maybe i'm too tired, but why exactly *idx + 8 ?
> See nvfx_fragprog.c:
>
> fpc->fp->texcoord[hw] = fdec->Semantic.Index + 8;
>
> when the semantic is GENERIC. (and 0xfffe when it's PCOORD). This is
> because there can be up to 8 TEXCOORD's.
yet you run for 8 or 10 texcoords. Wont this cause problems on nv40+?
>
>>> + sem = TGSI_SEMANTIC_TEXCOORD;
>>> emit = vroute[sem].emit;
>>> break;
>>>...
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
On 25.05.2015 21:29, Ilia Mirkin wrote:
> Commit 8acaf862dfe switched things over to use TEXCOORD instead of
> GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
> draw logic about TEXCOORD.
>
> Among other things, this fixes a crash in demos/arbocclude when using
> swtnl. Curiously enough, the point-sprite piglit works without this.
>
> Signed-off-by: