[GRASS-dev] seg fault of i.atcorr on quickbird
Nikos Alexandris
nik at nikosalexandris.net
Mon Nov 28 05:40:31 PST 2016
* Yann <dr.yann.chemin at gmail.com> [2016-11-27 20:12:38 +0100]:
>
>
>On 27/11/2016 20:06, Markus Neteler wrote:
>> On Sun, Nov 27, 2016 at 7:47 PM, Yann <dr.yann.chemin at gmail.com> wrote:
>>> trying to run i.atcorr on an image of Colombo.
>>>
>>> i.atcorr --overwrite input=radxs.1 parameters=6s_b1.txt output=refxs.1
>> ...
>>> Segmentation fault (core dumped)
>>>
>>> I looked into the iwave.cpp, it seems OK. What is the wavelength being less than 0.25 micron, never seen that before...
>> I wonder about this:
>>
>> grep 'ffu.s\[-' imagery/i.atcorr/iwave.cpp
>> case 1: for(i = 0; i < 65; i++) ffu.s[-99+i] = sr1[i];
>> case 2: for(i = 0; i < 65; i++) ffu.s[-99+i] = sr2[i];
>> case 3: for(i = 0; i < 65; i++) ffu.s[-99+i] = sr3[i];
>> case 4: for(i = 0; i < 65; i++) ffu.s[-99+i] = sr4[i];
>> case 5: for(i = 0; i < 65; i++) ffu.s[-99+i] = sr5[i];
>>
>> Negative value (-99)? If I remember correctly the Quickbird support
>> was added still without using the script.
>>
>> In r69930 (just now) I have added the Quickbird2 filter functions as
>> CSV which I got from Nikos in August to that you may re-run the
>> create_iwave.py script and compare the resulting iwave.cpp etc code to
>> that present in the source code at time.
>>
>> Markus
>Thanks Markus, will look into that.
>
>Also I believe the "less than 0.25" thing comes from either (or both) of
>these:
> static const float wli[5] = {0.001, 0.001, 0.001, 0.001, 0.001};
> static const float wls[5] = {0.161, 0.161, 0.161, 0.161, 0.161};
>
>line 2942 in iwave.cpp
Back in August, I thoroughly checked running the (modified) python script
against each and every sensor's spectral response data (in form of CSVs)
we have in our repo.
I'll give it a quick check -- I can only work on it after December the
1st though.
Nikos
Back in August, I thoroughly checked running the (modified) script
against each and every sensor's spectral response data (in form of CSVs)
we have in our repo.
I'll give it a quick check -- I can only work on it after December the
1st though.
Nikos
More information about the grass-dev
mailing list