Repository navigation
v1.0.0-alpha.2
Pre-release
Pre-release
Breaking changes
- Regarding
nmts.ek.v1alpha.physical.Modulator- the code has been moved from
ek/physical/modulation.prototoek/physical/modem.proto - field
adaptive_coding_and_modulation_to_channelshas been removed - field
adaptive_coding_and_modulation_for_channel_bandwidthshas been added with a different structure:- Previously, the
AdaptiveCodingAndModulationmessage stored a list ofModcodToDataRates, where eachModcodToDataRatestored aoneofof thresholds of received signal quality. This structure allowed the definition of thresholds through multiple metrics within the sameAdaptiveCodingAndModulationmessage (i.e. as both power at receiver output and C/(N+I)), and this should not be allowed. - Now, the
AdaptiveCodingAndModulationForChannelBandwidthmessage stores aoneofof lists of thresholds of received signal quality, so all elements must use the same metric. - Previously,
AdaptiveCodingAndModulationToChannelsdefined anadaptive_coding_and_modulationand all of the channels to which this ACM configuration applied. All channels had to be of the same bandwidth because the data rates in theAdaptiveCodingAndModulationmessage depend on the channel bandwidth, but this was not clear from the structure of the proto. - Now, this message has been renamed to
AdaptiveCodingAndModulationForChannelBandwidth, and it stores a single field for the channel bandwidth and a separate list of center frequencies.
- Previously, the
- Removed
min_received_signal_power_dbwas an option for defining MODCOD thresholds. Carrier to noise-plus-interference should be used instead.
- the code has been moved from
- Regarding
nmts.ek.v1alpha.physical.Demodulator- the code has been moved from
ek/physical/modulation.prototoek/physical/modem.proto - field
adaptive_coding_and_modulation_to_channelshas been removed - field
adaptive_coding_and_modulation_for_channel_bandwidthshas been added with a different structure (seeModulator)
- the code has been moved from
- Regarding
nmts.v1alpha.ek.service.Uni- has been renamed
nmts.v1alpha.ek.logical.Uni(logicalinstead ofservice)
- has been renamed
- In
nmts.v1alpha.ek.logical.LogicalPacketLink- field
propertieshas been removed - field
max_data_rate_bpshas been added (before was nested insideproperties)
- field
- In
nmts.v1alpha.types.geophys.CcsdsOrbitEphemerisMessage- field
filehas been renamed tofile_contents
- field
Additions
- New
nmts.v1alpha.ek.logical.BpAgentFnNMTS Entity to hold Bundle Protocol Agent (RFC 9171) state - In
nmts.v1alpha.ek.logical.LogicalPacketLink- field
max_sid_depthhad been added, inside thesr(SegmentRouting) field
- field
- In
nmts.v1alpha.ek.logical.RouteFn- field
max_sid_depthhad been added, inside thesr(SegmentRouting) field
- field
- In
nmts.v1alpha.ek.logical.Interface- field
max_data_rate_bpshad been added
- field
- In
nmts.v1alpha.ek.physical.PhysicalMediumLink- field
max_data_rate_bpshad been added
- field
- In
nmts.v1alpha.ek.physical.Port- field
max_data_rate_bpshad been added
- field
- In
nmts.v1alpha.ek.physical.LinearFilter- field
frequency_hzhas been added - field
lower_bandwidth_limit_hzhas been added - field
upper_bandwidth_limit_hzhas been added - field
noise_temperature_khas been added
- field
- In
nmts.v1alpha.types.geophys.KeplerianElements- field
central_bodyhas been added (defaults to Earth if not provided)
- field
Other Changes
- Add
go_packageoption to all protos - New Go library
//lib/graphlibrary to support DFS traversal
Full Changelog: v1.0.0-alpha.1...v1.0.0-alpha.2