You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now in the JSON format, the first carrier is placed at f_min + spacing. That's not intuitive because users would typically expect them to start at f_min as the first central frequency (or, possibly, as the lowest passband edge frequency as the docs mention the edge at some places). However, doing that in the existing legacy-JSON would lead to backward-incompatible change.
Right now in the JSON format, the first carrier is placed at
f_min
+spacing
. That's not intuitive because users would typically expect them to start atf_min
as the first central frequency (or, possibly, as the lowest passband edge frequency as the docs mention the edge at some places). However, doing that in the existing legacy-JSON would lead to backward-incompatible change.References:
The text was updated successfully, but these errors were encountered: