Ryan May wrote:
> John Hunter wrote:
>
>> On Tue, Nov 11, 2008 at 1:38 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>
>>> 1) Have psd(x) call csd(x,x)
>>> 2) Have csd() check if y is x, and if so, avoid doing the extra work.
>>>
>>> Would this be an acceptable solution to reduce code duplica
John Hunter wrote:
> On Tue, Nov 11, 2008 at 1:38 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> 1) Have psd(x) call csd(x,x)
>> 2) Have csd() check if y is x, and if so, avoid doing the extra work.
>>
>> Would this be an acceptable solution to reduce code duplication?
>
> Sure, that should work fi
On Tue, Nov 11, 2008 at 1:38 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> 1) Have psd(x) call csd(x,x)
> 2) Have csd() check if y is x, and if so, avoid doing the extra work.
>
> Would this be an acceptable solution to reduce code duplication?
Sure, that should work fine.
> On a separate note, once
John Hunter wrote:
>> In tweaking mlab.psd(), I'm noticing there is a lot of overlap between
>> the keyword args for psd() and csd(). In fact, csd() doesn't document
>> them itself, but just references psd(). Additionally, the csd() and
>> psd() Axes methods duplicate these docs, with a few additi
On Tue, Nov 11, 2008 at 10:35 AM, Ryan May <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In tweaking mlab.psd(), I'm noticing there is a lot of overlap between
> the keyword args for psd() and csd(). In fact, csd() doesn't document
> them itself, but just references psd(). Additionally, the csd() and
> psd
