Vera Erbes

Hi, I now added the fixed function in a new branch named fix_itd2angle_lookuptable. It is ready to merge. Kind regards, Vera

bug fixes for function itd2angle_lookuptable.m

Hi Piotr, I guess I need to be a project developer to do this (my Sourceforge name is verade)? Should I just open a new branch for review? Best regards, Vera Am 22.05.2019 um 17:32 schrieb Piotr Majdak: Dear Vera, thanks for debugging this problem. Can I ask you to submit the bug fix you proposed? Thanks, Piotr [bugs:#87] https://sourceforge.net/p/amtoolbox/bugs/87/ Small bugs in itd2angle_lookuptable.m Status: open Milestone: 0.9.9 Created: Tue Apr 16, 2019 10:17 AM UTC by Vera Erbes Last Updated:...

And I also want to suggest a correction to the suggested code in my first post: idFrontHor = Obj.SourcePosition(:,2) == ele & ... % horizontal plane (((Obj.SourcePosition(:,1) >= -90 & Obj.SourcePosition(:,1) < 0) ... | Obj.SourcePosition(:,1) >= 270) | ... (Obj.SourcePosition(:,1) >= 0 & Obj.SourcePosition(:,1) <= 90));

Meanwhile, I also noticed an additional problem: I think the azimuth range has to be given from +-90° instead of using only positive angles as that leads to a jump in the azimuth over ITD graph that is approximated by polyfit(). A simple solution would be to add azi(azi>180) = azi(azi>180)-360; after line 75, so the funktion is working for data given with azimuth range both 0°-360° and +-180°.

Meanwhile, I also noticed an additional problem: I think the azimuth range has to be given from +-90° instead of using only positive angles as that leads to jump in the azimuth over ITD graph that is approximated by polyfit(). A simple solution would be to add azi(azi>180) = azi(azi>180)-360; after line 75, so the funktion is working for data given with azimuth range both 0°-360° and +-180°.

Small bugs in itd2angle_lookuptable.m

partial loading in multiple dimensions without ...