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
To me, it does not make sense to have the divisions in scos-sensor or the associated calibration file. The only way to know where the divisions occur is to specifically look for them, in which case, they'd already have distinct points in the calibration file (i.e. the SDR would not be able to tune between divisions). If this was not done, then the user would not be able to include the divisions in the calibration file in the first place.
Basically, the frequency divisions are already handled by judicious choice of calibration frequencies, so there's no need to include them in the calibration file separately.
The text was updated successfully, but these errors were encountered:
Copied from the issue NTIA/scos-sensor#156 @ToddSchumannNTIA, as SCOS Actions now contains default calibration files:
To me, it does not make sense to have the divisions in scos-sensor or the associated calibration file. The only way to know where the divisions occur is to specifically look for them, in which case, they'd already have distinct points in the calibration file (i.e. the SDR would not be able to tune between divisions). If this was not done, then the user would not be able to include the divisions in the calibration file in the first place.
Basically, the frequency divisions are already handled by judicious choice of calibration frequencies, so there's no need to include them in the calibration file separately.
The text was updated successfully, but these errors were encountered: