[clam-devel] CrossCorrelation visibility

[therealnathanstewart at gmail.com]

Thanks. After looking it over I decided to try correlation in the time domain (really frequency, but performed as if in time domain) since I'm correlating two log specra, that's a 1-D N-bin sized correlation with positive offsets only. 

Still, it seems like correlation belongs in processings, not within one particular components src  folder.
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Pau Arumí <pau.arumi at barcelonamedia.org>
Sender: clam-devel-bounces at lists.clam-project.orgDate: Fri, 27 May 2011 15:09:22 
To: CLAM development list<clam-devel at lists.clam-project.org>
Reply-To: CLAM development list <clam-devel at lists.clam-project.org>
Subject: Re: [clam-devel] CrossCorrelation visibility

El dg 22 de 05 de 2011 a les 05:52 +0200, en/na Nathan Stewart va
escriure:
> I finally uncovered
> CLAM/plugins/spacialization/src/CrossCorrelation.{hxx,cxx} - and I'm a
> bit puzzled that not only is this buried, but the use of the namespace
> 'Hidden' suggests it was done so on purpose.  More importantly, it's
> not installed with the other headers. I'm actually looking to run
> cross correlation on spectra, and I believe a 512 point spectrum will
> adequately handle my needs - so I don't know if doing it in the
> frequency domain is still more efficient.


Hi Nathan,
the code you see like this one

namespace Hidden
{
        static const char* metadata[] = {
                "key", "CrossCorrelation",
                "category", "[plugin] New Spectral Processing",
                "description", "CrossCorrelation",
                0
        };
        static FactoryRegistrator<ProcessingFactory, CrossCorrelation>
        reg = metadata;
}

is a C++ idiom. The intention of this code is not to provide a public
interface but to automatically set up things (register processing
creator method and metadata) at load time. Hence the namespace Hidden.

> Is there any chance this could be moved into the installed headers for
> CLAM, or are there reasons for not doing so?

Well it is just that the authors use this as a clam processings plugin,
not as a library to link external code against it.

Best,
Pau


_______________________________________________
clam-devel mailing list
clam-devel at lists.clam-project.org
http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org