Displaying 9 results from an estimated 9 matches for "pleanty".
2003 Sep 09
0
Re: Hierarchical clustering
I think are looking for the function 'cutree' from package mva
checkout its documentation:
> require(mva)
> ?cutree
pleanty of examples to do what you want.
#############################################################################
Hi R lovers!
I am using the agnes function of the package cluster to compute a
hierarchical clustering.
I'd like to know if somebody has ever developped a function which could
give...
2004 May 24
2
last call for beta 1
Everyone,
It's looking like we're not going to get a draft of the spec done by the
end of the month as I'd hoped. However, I'm unwilling to let the
schedule slip yet again. We're going to freeze the bitstream as whatever
the reference implementation does and just live with any choices that
turn out unfortunate in the future. One has to draw the line somewhere.
This way
2008 Sep 29
1
Ambisonics Proposal summary.
Hi all,
My apologies for the confusion ... but I am re-naming this thread
again because the proposal doesn't come from Ambisonia. As the founder
of Ambisonia I have only been 'mediating' between some members of the
ambisonic community ... so it would be wrong to associate the spec
with Ambisonia.
To clarify. This is what the spec proposes:
- that Mapping = 1 means the contents are
2006 Sep 21
2
4.4 kickstart issues
Greetings all,
I'm trying to create a CentOS 4.4 kickstart CD (not a network install),
duplicating what
I've done for Fedora Core 3.
I am having a cirular dependency for initscripts, which causes
initscripts not to be installed
(no /etc/inittab when the boot gets to INIT)
The cascade is:
initscripts-7.39.25.EL-1.centos4 requires /sbin/nash
/sbin/nash is in mkinitrd-4.2.1.8-1
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...list]
by Monday May 30th 23:59 GMT along with an full explaination. Said
person should also specify a time Wednesday to discuss it on IRC either
before or after Xiph's monthly meeting.
This is not to say that such changes cannot be reverted. libogg2 is not
released yet and there will be pleanty of time for more debate for those
who are interested in debating the nuts and bolts. However, this *WILL*
represent the direction and basis for development to continue toward the
goal of getting a public release, so if you have an objection, it would
be appreciated to state it now.
Again, dis...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...list]
by Monday May 30th 23:59 GMT along with an full explaination. Said
person should also specify a time Wednesday to discuss it on IRC either
before or after Xiph's monthly meeting.
This is not to say that such changes cannot be reverted. libogg2 is not
released yet and there will be pleanty of time for more debate for those
who are interested in debating the nuts and bolts. However, this *WILL*
represent the direction and basis for development to continue toward the
goal of getting a public release, so if you have an objection, it would
be appreciated to state it now.
Again, dis...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...list]
by Monday May 30th 23:59 GMT along with an full explaination. Said
person should also specify a time Wednesday to discuss it on IRC either
before or after Xiph's monthly meeting.
This is not to say that such changes cannot be reverted. libogg2 is not
released yet and there will be pleanty of time for more debate for those
who are interested in debating the nuts and bolts. However, this *WILL*
represent the direction and basis for development to continue toward the
goal of getting a public release, so if you have an objection, it would
be appreciated to state it now.
Again, dis...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...list]
by Monday May 30th 23:59 GMT along with an full explaination. Said
person should also specify a time Wednesday to discuss it on IRC either
before or after Xiph's monthly meeting.
This is not to say that such changes cannot be reverted. libogg2 is not
released yet and there will be pleanty of time for more debate for those
who are interested in debating the nuts and bolts. However, this *WILL*
represent the direction and basis for development to continue toward the
goal of getting a public release, so if you have an objection, it would
be appreciated to state it now.
Again, dis...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...list]
by Monday May 30th 23:59 GMT along with an full explaination. Said
person should also specify a time Wednesday to discuss it on IRC either
before or after Xiph's monthly meeting.
This is not to say that such changes cannot be reverted. libogg2 is not
released yet and there will be pleanty of time for more debate for those
who are interested in debating the nuts and bolts. However, this *WILL*
represent the direction and basis for development to continue toward the
goal of getting a public release, so if you have an objection, it would
be appreciated to state it now.
Again, dis...