Hi Stefan, I do understand that the WSM f_gridMetMM provides the tighter of the two.
but aren't the sensor descriptions with freq_number set depending on metmm_accuracy levels tailor-made with respect to speed and a threshold accuracy? why would we prepare them first to then overwrite them (e.g. slowing down the "very very fast" setup significantly at least for ICI/ISMAR, and occasionally forcing the f_grid to contain more points than necessary for the intended and documented accuracy threshold)? does not really make sense to me. i assumed metmm_accuracy=0 should ALWAYS setup a f_grid with exactly one grid point per passband. the user can still overwrite this of course by (re-)setting either of freq_number and freq_spacing. but here, we provide a setting that overwrites itself. as written, seems odd to me. couldn't find this behaviour in documentation neither. the amsu-metmm report says "The first configuration selects 1 frequency in the middle of every channel. The second, third and fourth configuration select different numbers of frequencies for every channel." and doesn't ever mention spacing. but if you're sure that's what you want, i stop complaining ;-) wishes, Jana On Thu, Mar 3, 2016 at 6:15 PM, Stefan Buehler < [email protected]> wrote: > Hi Jana, > > this behaviour is intentional, you are guaranteed to get a least the > frequency number and spacing you specified. The tighter constraint wins. > > Best wishes, > > Stefan > > > On 02 Mar 2016, at 14:06, Oliver Lemke <[email protected]> > wrote: > > > > Hi Jana, > > > > In general, the higher accuracy always wins. So, if the bandwidth > divided by freq_numbers is larger than freq_spacing, the latter will be > used. > > > > Whether the behaviour you see with metmm_accuracy is intentional, I > leave to Alex to comment on. > > > > cheers, > > /oliver > > > > > >> On 2 Mar 2016, at 10:46, Jana Mendrok <[email protected]> wrote: > >> > >> Hi, > >> > >> when running the metmm system with the provided sensor setups, i had > expected that the set freq_numbers (depending on metmm_accuracy choice) are > ruling, ie. it's always them that are applied. > >> however, i found that freq_spacing is set such that it overrules > freq_number occasionally (eg. several of the ISMAR channels with > metmm_accuracy=0, leading to 58 f_grid points for the 15 existing ISMAR > channels, instead of 2x15=30 I had expected). > >> > >> is this intended behaviour? or a bug? > >> > >> wishes, > >> Jana > > > > _______________________________________________ > > arts_dev.mi mailing list > > [email protected] > > https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi > > _______________________________________________ > arts_dev.mi mailing list > [email protected] > https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi > -- ===================================================================== Jana Mendrok, Ph.D. (Project Assistent) Chalmers University of Technology Earth and Space Sciences SE-412 96 Gothenburg, Sweden Phone : +46 (0)31 772 1883 =====================================================================
_______________________________________________ arts_dev.mi mailing list [email protected] https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi
