<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#c7edcc>
<DIV><FONT size=2>The wiki is on again. :-)</FONT></DIV>
<DIV><FONT size=2>The "Detrended Fluctuation Analysis" is a strong feature about
danceability. It was refered in the mail before the
last one in this thread.</FONT></DIV>
<DIV><FONT size=2>It originates from fractal ananlysis and reveals correlations
within data series across different time scales. In the implementation,
there are some parameters (e.g., the size of MIN time scales, the
size of MAX time scales, the order of the regression fit) which should be
configurable. I'd like to know whether the subclasses of
ProcessingDataConfig or ProcessingConfig are those I should look
into.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>> Normally we do unit tests (white box) for funtional
components we can now the </FONT></DIV>
<DIV><FONT size=2>> result, and back2back for complex computations to assert
that the results are </FONT></DIV>
<DIV><FONT size=2>> not modified without noticing. In your case, and for
chord extraction, we </FONT></DIV>
<DIV><FONT size=2>> should also add some 'fitting' tests (comparing with a
ground truth) to </FONT></DIV>
<DIV><FONT size=2>> support b2b when the results differ and it is suposed to
be an enhancement.</FONT></DIV>
<DIV><FONT size=2>> </FONT></DIV>
<DIV><FONT size=2>> Is that something i could help you in any
way?</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>It helps, thanks, and more demonstrations of documents,
code,etc., could be further helpful, thanks again.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>>></FONT><FONT size=2><I> Given these problems solved,
the next plan is to extract more semantic</I></FONT><FONT
size=2><BR>>></FONT><FONT size=2><I> music descriptors (strong related to
danceability) based on some exsiting</I></FONT></DIV>
<DIV><FONT size=2>>></FONT><FONT size=2><I> CLAM descriptors including
Onsets and BPM.</I></FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>> It sounds funny ;-) Just keep us informed and we'll try
to help you as much as <BR>> we can. Are you planning to do that development
on clam svn?</FONT></DIV>
<DIV><FONT size=2><FONT size=2>Yes, I am, but please tell me if such development
is not appropriate for clam. (due to the complexity? or the
extractor should be separate?) In my opinion, yes it's natural that
users annotate a file by hand with a high semantic
descriptor, but a content-based extraction of the descriptor is also
reasonable, even if just for referrence.</FONT></FONT></DIV></BODY></HTML>