Hi Jana,
Alex will commit a change to solve this issue. We decided to add some code
which allows us to set default values for the frequency spacing depending on
the chosen accuracy. For the fastest accuracy, the spacing will be set larger
than the largest channel bandwidth.
cheers,
/oliver
> On 4 Mar 2016, at 09:00, Oliver Lemke wrote:
>
>
>
>> On 4 Mar 2016, at 08:43, Jana Mendrok wrote:
>>
>>
>> For ISMAR the number of frequencies for the fastest accuracy is not set to 1
>> for all channels ike for other sensors. Instead channels 10-13,19,20 are set
>> to -1 which means the default frequency spacing is used instead.
>>
>> no, now we do definitely missunderstand each other. the ones you point out
>> are channels not yet implemented. look at the other settings for them.
>> plenty of question marks there. ;-)
>> what i mean is e.g. happening for channel 18, which is a very broad channel.
>> there the 1GHz spacing overrules the freq_number = 1 set for
>> metmm_accuracy=0 and results in 5 freq points per passband.
>
> Ah, ok, sorry for the confusion. Got it now. Yes, that can happen. I don't
> think that was intentional. We'll have to find a way to set the frequency
> spacing wide enough for those cases to avoid that from happening. I'll
> discuss it with Alex.
>
> cheers,
> /oliver
>
___
arts_dev.mi mailing list
arts_dev.mi@lists.uni-hamburg.de
https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi
