In a future release, support for partial-trust applications will be removed. Microsoft no longer supports partially trusted code and recommends against its use. If you have a use case that requires partial-trust use of STK Components, contact AGI support.
TiremPropagationModel3_18, TiremPropagationData, and TiremPropagationMode have been moved from AGI.Foundation.Communications.dll to the new AGI.Foundation.Tirem.dll. This new library replaces the previous additional library which was required at runtime to use TIREM.
PolarizationSourceGetPolarizationEvaluator now returns SignalPolarizationEvaluator, which is a new evaluator type that computes Polarization for a given time and Signal. This allows polarization to vary based on the properties of the signal being propagated.
Removed the following items, which were marked obsolete in a previous release:
CommunicationLinkScalar.IntendedSignalIdentifier and CommunicationObjectScalar.IntendedSignalIdentifier
AtmosphericAttenuationModelItuRP676Version3, AtmosphericAttenuationModelItuRP676Version5, CloudFogAttenuationModelItuRP840Version3, RainAttenuationModelItuRP618Version9
Zero-argument and one-argument constructors in PropertyInvalidException
TiremPropagationModel implements the most recent available version of TIREM using a native library on 64-bit Windows and Linux platforms. TiremPropagationModel3_18 is still available without any native runtime dependencies. See the TIREM topic for more information.
Added AnsysHfssFarFieldDataGainPattern and AnsysHfssFarFieldDataPolarizationSource. These classes import data from an Ansys HFSS far field data formatted file (*.ffd) to be used as a RadioFrequencyGainPattern or PolarizationSource, respectively. The far field data exported by Ansys HFSS is based on vertical and horizontal electric field vector components arranged in a spherical coordinate system.
Added support to the Cesium library for the following CZML features:
Corrected the value returned by QuantizedMeshTerrainProviderMinimumSampleSpacing (as well as the derived class StkTerrainServer) to use the ZoomLevel in the calculation. Note that because quantized-mesh tiles are not a regular grid-based format, this value is still an estimate.
Corrected an issue where an invalid entry in a satellite database could throw an exception when read by StkSatelliteDatabase, which would prevent use of other valid entries. Invalid data columns are now left with their default value.
Clarified the documentation for SimpleReceiverGain to indicate that the value pertains to the gain of the amplifier.
Fixed an issue in AccessQueryAnd which would cause an erroneous delay evaluation to be created and lead to an exception.
Removed the following items, which were marked obsolete in a previous release:
Static creation methods in EllipsoidSurfaceRegion.
Methods in TerrainAlongLine which only take a maximum terrain height parameter.
StkCityDatabase.GetCentralBody, StkCityDatabase.GetCityType, and StkCityDatabase.GetCountry.
StkFacilityDatabase.GetCentralBody and StkFacilityDatabase.GetNetwork.
SegmentPropagatorConstraint.Scaling and SegmentPropagatorConstraint.Tolerance.
SegmentPropagatorVariable.MaximumStep, SegmentPropagatorVariable.VariableTolerance, and SegmentPropagatorVariable.Scaling.
Constructors in AccessEntityFilter<TEntity>, EntityDynamicSensorFieldOfView<TEntity>, EntityPoint<TEntity>, and EntityAxes<TEntity> which do not take EntityParameter<TEntity> and TransactionParameter parameters.
TransactionParameter.Instance and EntityParameter.Instance.
EvaluatorHelper.TimeIntervalCollectionIsTimeVarying, EvaluatorHelper.EvaluatorCollectionIsThreadSafe, and EvaluatorHelper.AvailabilityIntervals.
Added CentralBodyIntersection, a utility that can check for orbit intersection with a planet given two-body dynamics.
Insight3D has been updated with internal code changes, including changes to glTF loading.
CartographicExtent can now be constructed with the value of π in native units of the extent. In addition, it now supports longitude wrapping and extents which cross the antimeridian.
TiremPropagationData is now immutable, and its methods have been renamed and their documentation has been corrected.
CommunicationLinkScalar.IntendedSignalIdentifier and CommunicationObjectScalar.IntendedSignalIdentifier have been marked obsolete. Use CommunicationLinkScalarIntendedSignalStrategy and CommunicationObjectScalarIntendedSignalStrategy instead.
Added PointInRegionNearestToReferencePoint. This new point is defined as the closest point within the interior of a specified EllipsoidSurfaceRegion relative to another reference point. The reference point may be on, in, or around the region.
Added regularized boolean operations to EllipsoidSurfaceRegions. These operations include: add (union), subtract (difference), intersect, and complement. A method for combining overlapping regions, Reduce was also added. In order to support these options, EllipsoidSurfaceRegions may now be compared for equality.
Added several new methods to EllipsoidSurfaceCurve, including: ComputeIntersection, for finding the location of curve-curve intersection, and FindClosestPointOnCurve, for finding the location of the point on a curve nearest a given point. EllipsoidSurfaceCurves may now be compared for equality.
Added Iau2015Orientation, which provides central body orientation parameters based on the 2015 IAU report.
The performance and memory use of GridTimeSampledValues have been greatly improved when using parameterized grid types.
Calculations in the following gain patterns have been updated to match changes made in STK Desktop 12: BesselCircularApertureGainPattern, CosineCircularApertureGainPattern, CosinePedestalCircularApertureGainPattern, CosinePedestalRectangularApertureGainPattern, CosineRectangularApertureGainPattern, CosineSquaredCircularApertureGainPattern, CosineSquaredPedestalCircularApertureGainPattern, CosineSquaredPedestalRectangularApertureGainPattern, CosineSquaredRectangularApertureGainPattern, SincExponentRectangularApertureGainPattern, and UniformCircularApertureGainPattern.
Coverage calculations based on time sampling at discrete time steps (ParameterizedTemporallyPartitionedCoverageDefinition and MaterializedTemporallyPartitionedCoverageDefinition) produce more consistent results when computed with different threading settings.
Intervals of consideration in temporally partitioned coverage calculations (ParameterizedTemporallyPartitionedCoverageDefinition and MaterializedTemporallyPartitionedCoverageDefinition) now correctly honor IsStartIncluded and IsStopIncluded.
Fixed an issue where TranslationalMotionInterpolator would return the second data node instead of the last when evaluated without specifying an order and the date to be evaluated is a segment boundary time.
Fixed a very rare issue where EllipsoidSurfaceRegionCheckPointInsideRegion could throw an exception.
ParameterizedEvaluator<TResult> and other similar types are now abstract base classes that can be used to more easily implement a specific parameterized evaluator.
As a result of changes made to RainAttenuationModelItuRP838Version3 and CloudFogAttenuationModelItuRP840Version6, the boolean to evaluate on the transmit clock is no longer supported for these models.
The following SignalPropagationModels have been marked obsolete, and will be removed in a future release, because they have been removed from STK Desktop 12. All of these models have been superseded by newer versions more than 10 years ago.
AtmosphericAttenuationModelItuRP676Version3, AtmosphericAttenuationModelItuRP676Version5 - Use AtmosphericAttenuationModelItuRP676Version9 instead.
RainAttenuationModelItuRP618Version9 - Use RainAttenuationModelItuRP618Version12 instead.
CloudFogAttenuationModelItuRP840Version3 - Use CloudFogAttenuationModelItuRP840Version6 instead.
StkTerrainServer now extends from a new abstract base class, QuantizedMeshTerrainProvider, and most functionality has been moved up to the new base class, which can be used to implement a TerrainProvider based on quantized-mesh tiles without using the STK Terrain Server REST API. As a result, StkTerrainServerTerrainCache has been removed and replaced by QuantizedMeshTerrainCache.
Two constructors in PropertyInvalidException have been marked obsolete. Use the constructor taking both propertyName and message parameters, or the static Validate methods.
RainAttenuationModelItuRP838Version3 and CloudFogAttenuationModelItuRP840Version6 can now optionally be configured with new objects that provide more control over the atmospheric data used by these signal propagation models to compute signal attenuation. Configuring a custom LinkSubdivision specifies how to subdivide the link into sub-segments, where atmospheric conditions will be considered constant over each sub-segment. Configuring a custom ItuRP838AtmosphericModel or ItuRP840AtmosphericModel, respectively, allow atmospheric data to be provided to the calculation at the midpoint of each sub-segment as the signal travels along the link path. These objects allow detailed weather information to be provided to the model, and enables geometries where the link is primarily horizontal and the signal might pass through multiple distinct weather cells.
Calculations in the following gain patterns have been updated to match changes made in STK Desktop 11.7.1: CosineRectangularApertureGainPattern, CosineSquaredPedestalRectangularApertureGainPattern, CosineSquaredRectangularApertureGainPattern, SincExponentRectangularApertureGainPattern, and UniformRectangularApertureGainPattern. Calculations are now based on the Cartesian coordinate frame instead of the rectangular antenna coordinate frame, which eliminates anomalies observed at higher elevation angles.
Improved the performance of calculations in OrbitalElements.
Added a section to the Frequently Asked Questions topic demonstrating whiskbroom and pushbroom sensor design in STK Components.
TwoBodyPropagator produces more reliable results for certain edge-case inputs.
Added several calculation methods to the Complex class.
Clarified the documentation for the time-of-flight methods in OrbitalElements to indicate that a negative true anomaly indicates a time before periapsis (negative time) and a positive sign indicates a time after periapsis (positive time).
Removed the following items, which were marked obsolete in a previous release: GpsCommunicationsConstellation.Create (overload without rolloverCount), LinkGraphics.FollowSurface, TargetedSegmentListOperatorResults.SegmentsForNextOperator, and items related to multiple maneuvers for an ImpulsiveManeuverSegment.
The following methods have been marked obsolete and replaced by better named methods:
The ComputeElevationAngleAboveTerrain and ComputeTerrainIntersection methods in TerrainAlongLine specifying only a maximum terrain height parameter have been marked obsolete. Use the overloaded methods specifying both minimum and maximum terrain heights instead.
In AtmosphericAttenuationModelItuRP676Version3, AtmosphericAttenuationModelItuRP676Version5, and AtmosphericAttenuationModelItuRP676Version9, the API for providing custom atmospheric data from external sources has changed. The ITU-R P.676 model requires the atmospheric conditions for locations along the link path as it crosses multiple horizontal layers. The previous interface did not provide the needed values, and so the following properties have been removed: CustomPressure, CustomTemperature, and CustomWaterVaporPressure, and replaced with a new property CustomAtmosphericModel. This new property allows installation of a new definitional object, ItuRP676AtmosphericModel, which must provide an evaluator which can compute ItuRP676AtmosphericValues for a given JulianDate and Cartographic location. The evaluator will be evaluated at multiple locations along the link during signal propagation, depending on the link geometry and the model-defined atmospheric layers. Note that by default, the model uses values from the standard atmospheres from ITU-R P.835, which is the same as the previous default behavior.
Changed the default for TargetedSegmentListDifferentialCorrectorOnlyStoreFinalResults to true.
Added InitialOrbitSolver, which can determine an orbit based on three positions and (optionally) three times, under two-body conditions.
Added TerrainAlongLineComputePositionWithMaximumElevationAngle, which returns the point on terrain with the highest elevation angle between two positions.
Insight3D has been updated to a new underlying code baseline, with behind-the-scenes improvements, including better glTF support.
Improved the TerrainAlongLineComputeElevationAngleAboveTerrain algorithm, which now attempts to locate extremal values of terrain when sampling of the terrain indicates a sign change in the slope among three adjacent samples. This corresponds to changes made in STK Desktop 11.7.
TerrainLineOfSightConstraint now has a MinimumTerrainHeight property, which can be used to specify the minimum height relative to the Shape. This property defaults to TerrainAlongLineDefaultMinimumTerrainHeight.
Improved the performance of calculations in OrbitalElements.
Improved the exception thrown by ScalarAtEndOfSegmentConstraint and ScalarAtEndOfNumericalSegmentConstraint when the segment it is associated with cannot be found. The exception message will now contain the name of the segment that it was looking for.
Improved documentation clarity in the Multivariable Function Solvers topic.
Corrected errors in the calculation of the following signal propagation models, where they did not match the equations in the ITU specifications: AtmosphereModelItuRP835, CloudFogAttenuationModelItuRP840Version6, AtmosphericAttenuationModelItuRP676Version3, AtmosphericAttenuationModelItuRP676Version5, RainAttenuationModelItuRP618Version10, RainAttenuationModelItuRP618Version12, and RainAttenuationModelItuRP838Version3.
Fixed a bug where the final position for a CZML polyline would be omitted if it was equal to the first position. This should only be done for CZML polygons and holes, which are closed curves by definition.
Fixed incorrect exception documentation on ModifiedKeplerianElementsComputePeriod.
Removed the following items, which were marked obsolete in a previous release: AtmosphericAttenuationModelItuRP676, CloudFogAttenuationModelItuRP840, RainAttenuationModelItuRP618, RainAttenuationModelItuRP838, TropoScintAttenuationModelItuRP618, ItuRP618RainAttenVersion, ItuRP618TropoScintVersion, ItuRP676Version, ItuRP838Version, ItuRP840Version. Also, IPropagateCollectionFromOnePoint was unused and has been removed.
InterpolationAlgorithm now derives from DefinitionalObject, and interpolation has been moved to a new Interpolator type, which can be obtained from an InterpolationAlgorithm by calling GetInterpolator. The purpose of this reorganization is to make these types more closely match the rest of STK Components, where a definitional object (InterpolationAlgorithm) represents the configuration for a calculation and produces an evaluator (Interpolator) which performs the calculations using a snapshot of the configuration, and also allows a consistent approach to thread safety. Note that some Interpolators are not safe for use from multiple threads simultaneously, and so must be handled using the techniques described in the Multithreading topic.
The following static properties have been marked obsolete: TransactionParameter.Instance and EntityParameter.Instance. Rather than using these global singleton parameters, construct instances of the appropriate parameter type where needed, and use those parameters in your problem definitions.
AccessEntityFilter<TEntity>, EntityDynamicSensorFieldOfView<TEntity>, EntityPoint<TEntity>, and EntityAxes<TEntity> now must be constructed with instances of EntityParameter<TEntity> and TransactionParameter. The other constructors have been marked obsolete.
The following helper methods in EvaluatorHelper have been marked obsolete: TimeIntervalCollectionIsTimeVarying, EvaluatorCollectionIsThreadSafe, AvailabilityIntervals. Use the other helper methods with more consistent names.
The following properties in SegmentPropagatorConstraint have been marked obsolete, as the properties may be directly set on the underlying SolverConstraintSettings: SegmentPropagatorConstraint.Scaling and SegmentPropagatorConstraint.Tolerance.
The following properties in SegmentPropagatorVariable have been marked obsolete, as the properties may be directly set on the underlying SolverVariableSettings: SegmentPropagatorVariable.MaximumStep, SegmentPropagatorVariable.VariableTolerance, and SegmentPropagatorVariable.Scaling.
Added CzmlClientEntitySet, which can be used to create a CzmlUpdateDocument containing only the differences between a CzmlDocument and the previous state of a particular CZML client application. This provides a mechanism to efficiently send updates without retransmitting the entire CZML state repeatedly.
Added support to the Cesium library for the following CZML features:
AGIProcessedDataTerrain now supports reading PDTT version 2 files.
Added ScalarGrazingAltitudeBetweenTwoPoints, a new scalar that can compute the dynamic grazing altitude on the line-of-sight between two points in space.
Added ScalarSquintAngle, which can compute the angle between the projected velocity vector of a moving object and a projected displacement vector between the object and an arbitrary target. This is commonly used to measure or constrain the cross-track ground angle between two objects.
Added ScalarAngleInRange, a scalar that takes an input angle and outputs the angle in a new range. An example of this operation would be to take an angle produced in the range -π, π and output the same angle in the range 0, 2π.
Added ScalarAngleSmallSpan, a scalar that returns the small span between two scalars that produce an angle.
Added ScalarDopplerConeAngle, a simple geometric scalar that returns the symmetric angle between the link displacement about the velocity vector at the specified end of the link.
Added SphericalDescriptiveStatistics for computing descriptive statistics of data that is spherical in nature.
Added several new method overloads to compute grazing altitude in Ellipsoid.
Improved the behavior of the grazing point and grazing altitude methods on Ellipsoid for nearly coincident points.
Calculations are now validated against the latest version of the Standards of Fundamental Astronomy (SOFA) Libraries, Issue 2019-07-22.
Fixed an issue where EllipsoidGeodesic would not report final longitude and final heading consistent with the rest of the points on the geodesic curve in the case where the final point happened to lie at a pole of the ellipsoid.
No changes in this release. This release only contains changes that affect STK Components for Java.
All of the static creation methods in EllipsoidSurfaceRegion are now obsolete. These creation methods have been replaced with new EllipsoidSurfaceRegionBuilder types, which can create EllipsoidSurfaceRegions in all previous ways, plus several new ones. For more information, see each builder type: ConvexBoundaryEllipsoidSurfaceRegionBuilder, SpecifiedCurveEllipsoidSurfaceRegionBuilder, SpecifiedNodesEllipsoidSurfaceRegionBuilder, and SpecifiedExtentEllipsoidSurfaceRegionBuilder.
PhasedArrayGainPattern.BacklobeSuppression has been marked obsolete and renamed to BackLobeSuppression.
Added support to the Cesium library for the following CZML features:
Added DeleteCesiumProperty<T> to generate CZML which indicates that existing data (samples or interval values) should be deleted from the client for a particular property.
Added the following new antenna gain patterns:
Added DynamicDelaunayElements, DynamicEquinoctialElements, and DynamicKozaiIzsakMeanElements, which compute time-varying orbital elements from a Point. Added ScalarDelaunayElement, ScalarEquinoctialElement, and ScalarKozaiIzsakMeanElement, which provide individual orbital elements as a time-varying Scalar.
Added a documentation page for numerical integrators, including examples on how to use them and guidelines on how to proceed for various types of problems.
Fixed an exception when using TranslationalMotionInterpolator with zeroth degree Lagrange interpolation.
Removed the following items, which were marked obsolete in a previous release: ScopedEvaluatorGroup, KeplerianElements.PerifocalToCartesianMatrix, KeplerianElements.TrueAnomalyToMeanAnomaly, KeplerianElements.TrueAnomalyToEccentricAnomaly, KeplerianElements.MeanAnomalyToTrueAnomaly, KeplerianElements.MeanAnomalyToEccentricAnomaly, KeplerianElements.EccentricAnomalyToTrueAnomaly, KeplerianElements.EccentricAnomalyToMeanAnomaly, KeplerianElements.ComputeEccentricity, KeplerianElements.ComputeRadiusOfPeriapsis, KeplerianElements.ComputeRadiusOfApoapsis, KeplerianElements.ComputeTimeOfFlight, KeplerianElements.ComputeTimePastPeriapsis, KeplerianElements.ComputeTimePastPeriapsis, KeplerianElements.TimePastPeriapsisToTrueAnomaly, KeplerianElements.TimePastPeriapsisToMeanAnomaly, KeplerianElements.TimePastPeriapsisToEccentricAnomaly, KeplerianElements.SemimajorAxisToPeriod, ChildrenExtension.FindDescendents, EvaluatorHelper.IsAvailable, EvaluatorHelper.EvaluatorCollectionIsThreadSafe, EvaluatorHelper.EvaluatorCollectionIsTimeVarying, EvaluatorHelper.AvailabilityIntervals, TimeConstants.PicoSecond, Stereoscopic.AutomaticallyComputeProjectionDistance, CoverageDefinitionOnCentralBody, CoverageGridPoint, CoverageGridResult, CreateCoverageGridPointForAccess, DiscreteCoverageDefinitionOnCentralBody, GridStatistics, EllipsoidGrid, EllipsoidGridGlobal, EllipsoidGridIntersection, EllipsoidGridLatitudeBounds, EllipsoidGridLatitudeLine, EllipsoidGridLongitudeLine, EllipsoidGridPoint, EllipsoidGridRegions, EllipsoidGridSpecified.
ImpulsiveManeuverSegment now only works with a single maneuver. For multiple impulsive maneuvers, use multiple segments.
TargetedSegmentListOperatorResults.SegmentsForNextOperator is now obsolete. Obtain the segment propagators from the ParentConfiguration instead.
LinkGraphics.FollowSurface is now obsolete, replaced by the new ArcType property. Note that in most situations, this will not need to be configured, since the new default (CesiumArcType.None) is appropriate for drawing links.
Added new methods to IPropagatedSignalService to return the propagated signal before or after a specific propagation model.
The overload of GpsCommunicationsConstellation.Create taking a SEM almanac filename had a hard-coded value of 1 for rolloverCount, which is no longer correct for almanacs after April 7, 2019. A new overload has been added taking rolloverCount as a parameter.
Removed PolylinePrimitive.RenderInScreenSpace which was unintentionally made public in a previous release.
Added the capability to model atmospheric refraction. VectorRefractedDisplacement represents a refracted displacement vector, using a configurable AtmosphericRefractionModel, and LinkRefracted wraps another link and provides the refracted path. Also, CommunicationLinkCollection now has additional methods to add links using a refraction model. Several refraction models are available:
Added the ability to distinguish the propagation loss for a specific propagation model, or subset of models, in the propagation chain. Use ScalarPropagationLossSelectedModels to specify the propagation models for which to compute loss, or use the new "Detailed" methods on CommunicationSystem to create LinkBudgetScalars with detailed propagation loss scalars for each propagation model, or to evaluate a LinkBudget containing the loss for each model.
Added CentralBodySurfaceCurveGraphicsArcType and CentralBodySurfaceRegionGraphicsArcType to specify how Cesium should connect the positions of a surface curve, or the boundary curve of a surface region. By default, this will be automatically detected from the type of EllipsoidSurfaceCurve. Also added LinkGraphicsArcType, however, the default of CesiumArcType.None is appropriate for drawing links in most cases.
Added FiniteManeuverSegment and associated functionality to propagate spacecraft requiring modeling of non-instantaneous burns. This new functionality includes the ability to target a finite maneuver's properties based upon seed dynamics generated by a simple impulsive maneuver. Continuous thrust force modeling is included via ContinuousThrustForceModel. Generic propagation segment switching functionality is also included in the form of SwitchableSegment.
Various helper geometry types were also added to enable fixing thruster orientation, fixing spacecraft properties at a parameterized state, and more. These helper types include: PointFixedAtJulianDate, ScalarFixedAtJulianDate, VectorFixedAtJulianDate, DelegateOnStateValueDefinition<T>, TimeFromStateValueDefinition, etc.
Added extension methods to StkCityDatabaseEntry, StkCityDatabase, StkFacilityDatabaseEntry, StkFacilityDatabase, StkSatelliteDatabaseEntry, and StkSatelliteDatabase. Each method creates Platforms from a STK database entry, or the result of a database query.
Added the following additional features to Insight3D:
STK Components is now tested against .NET Core. See the System Requirements topic for more information on supported platforms.
HufnagelValleyRefractiveIndexStructureParameterModel now uses the grazing altitude instead of the transmitter's altitude for its calculation.
Modified approach to computing numerical partial derivatives of density to match STK Desktop 11.6 implementation.
Improved Earth fixed transformations when EarthOrientationParameters are not configured.
Added FollowSegmentStartsWithStoppingConditionsUseWrappedStoppingConditions, which allows the user to toggle the use of the stopping conditions set on the underlying propagator of the FollowSegmentStartsWithStoppingConditions when finding the initial state for the follow segment.
The CesiumDemo example application has been expanded to demonstrate more capabilities, and is now a web application rather than a command-line program. See the Cesium Demo topic for more information on how to build and run the example.
Fixed a crash in Insight3D when used in an WPF application when animating.
Fixed issues preventing cloning from working correctly for AxesInAxes, AxesLinearRate, EntityAxes<TEntity>, and GpsCommunicationsFrontEnd. Fixed errors in definitional equality for AxesAlignedConstrained and EntityDescriptor<TEntity>.
The following signal propagation models have been marked obsolete, and replaced with new classes which specify the version in the name. Having separate implementations per version of the model allows more flexibility in cases where different versions of the model have different configurable parameters. The following list specifies the replacement classes which match the same version of the model as the obsolete implementations. Note that some models now have additional versions available, including newer versions, which are listed in the New Features section below.
AtmosphericAttenuationModelItuRP676 is replaced by AtmosphericAttenuationModelItuRP676Version5.
CloudFogAttenuationModelItuRP840 is replaced by CloudFogAttenuationModelItuRP840Version3.
RainAttenuationModelItuRP618 is replaced by RainAttenuationModelItuRP618Version9.
RainAttenuationModelItuRP838 is replaced by RainAttenuationModelItuRP838Version3.
TropoScintAttenuationModelItuRP618 is replaced by TropoScintAttenuationModelItuRP618Version9.
Added the following new versions of existing signal propagation models:
Added AccessQueryStartAndMaintain. This new constraint encompasses two underlying queries, a start query and a maintain query. This query will be considered satisfied after the start query is satisfied, and for as long as the maintain query is satisfied.
Added SP3dEphemeris to read data from SP3-d precise ephemeris files.
Added BurdenFairesAdaptiveQuadrature numerical integration utility to integrate to an arbitrary tolerance.
Fixed an issue where EllipsoidRhumbLine would compute incorrect values related to the distance along the curve for the case of a sphere.
Fixed several issues in TranslationalMotionInterpolator related to multiple data elements at segment boundaries. The interpolator will now choose either the first or last datum depending upon whether or not interpolation is to the boundary or from (inclusive) the boundary.
Fixed an issue where the interpolator for the ICRF/ITRF transformation could throw an exception near the boundary of the valid dates for IAU 2006 data.
The example applications have been updated to fix errors when opening controls in the Visual Studio designer. Note that the errors in the designer did not affect building or running the applications. Because Visual Studio is still 32-bit, the designer cannot directly load the Insight3D control, which is 64-bit. Instead, we include a placeholder blank panel in the location where Insight3D should go, then create and add the Insight3D control to that panel in non-designer code.
Fixed an issue where certain access constraints could throw an exception while evaluating in rare cases, when a very small, non-zero rate of change in the constrained value could cause a step size to be calculated which exceeds the valid range of a JulianDate.
Fixed a bug in RainAttenuationModelItuRP838 and CloudFogAttenuationModelItuRP840 that could cause an exception during propagation when the model's SignalPropagator was cloned, or used from multiple threads simultaneously.
STK Components for .NET now requires .NET 4.5 or above.
Insight3D is now 64-bit only. Note that all other analysis libraries continue to be independent of system architecture.
Insight3D now depends on the Microsoft Visual C++ Redistributable for Visual Studio 2017, which should installed on any system running an application using Insight3D. The installer for the current version of the redistributable is included in the install for ease of deployment. The previous ability to load the required dependencies from the application directory ("app-local") is still technically possible, but due to the complexity is not described here. Contact AGI support if you have a need to deploy Insight3D applications without an installer on systems that cannot install the redistributable.
The Auto-Routing Library has been discontinued and is no longer included with STK Components. For questions or concerns, please contact email@example.com.
The coverage system has markedly changed. See the following list for a migration path to the new system:
Use ParameterizedSpatiallyPartitionedCoverageDefinition in place of CoverageDefinitionOnCentralBody.
Use ParameterizedTemporallyPartitionedCoverageDefinition in place of DiscreteCoverageDefinitionOnCentralBody.
Use CoverageGridPointWithResults in place of CoverageGridPoint.
Use CoverageResults in place of CoverageGridResult.
Use CoverageGridPointCreationCallback in place of CreateCoverageGridPointForAccess.
Use GridDescriptiveStatistics in place of GridStatistics.
New overloads of the available methods in GridTimeSampledValues have been created to support the new types.
Use CentralBodyCoverageGrid in place of EllipsoidGrid.
Use GlobalCoverageGrid in place of EllipsoidGridGlobal.
Use IntersectionWithSurfaceRegionsCoverageGrid in place of EllipsoidGridIntersection.
Use LatitudeBoundsCoverageGrid in place of EllipsoidGridLatitudeBounds.
Use LatitudeLineCoverageGrid in place of EllipsoidGridLatitudeLine.
Use LongitudeLineCoverageGrid in place of EllipsoidGridLongitudeLine.
Use CoverageGridPoint in place of EllipsoidGridPoint.
Use SurfaceRegionsCoverageGrid in place of EllipsoidGridRegions.
Use SpecifiedCentralBodyCoverageGrid in place of EllipsoidGridSpecified.
GraphicsParameterTransform<TInput,TOutput>.TransformationCallback now uses the Converter delegate type instead of a custom TransformCallback delegate type.
IEvaluator now has a Group property, which gets the EvaluatorGroup that contains an evaluator. In general, this means that all evaluators throughout the system now require a group to be passed to their constructor. In practice, this only affects custom evaluator subclasses, because normally evaluators are obtained by calling a GetEvaluator (or similar) method, which is unaffected.
ScopedEvaluatorGroup is now marked obsolete. This type used the dispose pattern in a misleading manner, especially now that EvaluatorGroup is disposable. The purpose of the ScopedEvaluatorGroup was as a shortcut to obtain an evaluator and then optimize, which can now be accomplished by calling the static method EvaluatorGroup.GetOptimized and passing a delegate which obtains the desired evaluator.
Several helper methods in EvaluatorHelper have been marked obsolete and replaced by new methods which provide better syntax. These helper methods are mainly useful for implementing custom evaluator subclasses.
AccessEntityFilter<TEntity> now requires an EvaluatorGroup to be given either to the constructor or to the ApplyChanges method. The provided group will be used to obtain an AccessEvaluator from the configured query when needed.
EllipsoidGraphicsSubdivisions has changed from CesiumProperty<double> to CesiumProperty<int>. This property always required integer values in order to render correctly, and the new type makes this more clear.
Removed the following items, which were marked obsolete in a previous release: BingMapsStyle.Hybrid, SegmentPropagatorVariable.CreateSettings, Sgp4EstimationInput.OutputEpoch, GpsSatelliteInformation.PRN, GpsSatelliteInformation.SVN, GpsSatelliteInformation.SatNum, GpsSatelliteInformation.SVBeginsAsPrn, GpsSatelliteInformation.SVEndsAsPRN, SemAlmanacRecord.SpaceVehicleNumber.
Several uncommonly used constructor overloads of FileStreamFactory have been removed. For unusual situations, use the new constructor overload which takes a delegate, or extend FileStreamFactory and override OpenFileStream.
StoppablePropagatorDefinition.AnyConditionSatisfiedEvent has been renamed to StoppablePropagatorDefinitionAnyConditionSatisfied and is now a proper event.
Added StkTerrainServerTerrainOverlay which loads visual terrain data in Insight3D from STK Terrain Server, either over the internet or from your own local server.
Added BasicLaunchSegment and SimpleAscentPropagator. The new propagator can propagate a launch vehicle from a specified position in a central body's fixed frame, to a specified burnout position and velocity. The underlying technique used for this new propagator is fitting an ellipse to the input, thus it is intended to act as a reasonable initial segment for the purposes of visualization and basic ephemeris output. The BasicLaunchSegment encapsulates this new propagator so that it may be used in the Segment Propagation Library.
Added 3D coverage and Volumetric analysis capabilities to the Spatial Analysis Library. The new features include the ability to extrude 2D coverage grids to 3D, new geometric primitive grid types (cuboid, spheroid, etc.), new gridding algorithms, grids with motion, and the ability to easily modify and combine grids. The ability to specify grids attached to any reference frame is also included. The following list specifies some of the new grid types:
ConeCoverageGrid - This grid can be easily manipulated to be a disc, a part of a cone, a shell, etc.
CuboidCoverageGrid - This grid can be easily manipulated to be a plane or a box.
CylinderCoverageGrid - This grid can be easily manipulated to be a disc, a shell, etc.
RectangularPyramidCoverageGrid - This grid can be easily manipulated to be a frustum.
SpheroidCoverageGrid - This grid can be easily manipulated to be a shell, a hemisphere, etc.
TorusCoverageGrid - This grid can be easily manipulated to be a shell, a half torus, etc.
The new coverage system now allows use of parameterized calculations in both continuous and discrete partitioning modes. Previously, parameterized calculations could only be used with discrete mode. See the Coverage topic for more information.
Added the following additional features to Insight3D:
Added support to the Cesium library for the following CZML features:
EvaluatorGroup now implements IDisposable. Disposing a group will dispose all evaluators created in that group. Disposing the group when you are done working with a set of evaluators is now the recommended style, rather than disposing individual evaluators.
ScalarOccultation, ScalarOccultationCylindrical, and ScalarOccultationDualCone have been moved to the Models library, to allow them to be used in general access problems. The Frequently Asked Questions topic demonstrates an example of using these scalars to perform a more advanced sun lighting access constraint.
Added several helper methods to download the contents of data files as a string, without parsing the data into objects.
Documentation has been added to the Cesium library to indicate what the default behavior is if each property is left unspecified.
Fixed an issue where Dilution of Precision and GPS satellite tracking evaluators required a IGpsPrnService service on the satellite objects. This prevented these evaluators from using other sources of orbit data than GPS almanacs.
Fixed an issue when specifying CzmlDocumentMaximumDataPointsPerPacket that could cause an exception to be thrown when writing CZML.
Fixed an issue where changing CzmlDocumentEnableAutomaticReferencing to false had no effect.
Fixed a bug that caused generating CZML to fail if the last sample date was a segment boundary time.
Fixed an issue where Insight3D could crash on certain systems when loading images on 64-bit.
Fixed an issue where HistoryGenerator<TEntity> could fail to cull history in rare cases.
Fixed an issue in JulianDate that could cause exceptions in methods such as SecondsDifference or EqualsEpsilon when operating on MinValue or MaxValue, or intervals containing those value as endpoints.
Fixed a bug relating to occultation percentages when the illuminating body is closer than the occluding body.
ScalarAtmosphericDensity and derived classes now have a configurable UpperHeightLimit property, above which the density model will return a value of zero. The default value for each model has been set to match the behavior of STK Desktop 11.3.
Calculations are now validated against the latest version of the Standards of Fundamental Astronomy (SOFA) Libraries, Issue 2018-01-30.
An issue was introduced in the 2017 r4 release that could cause the CentralBodySurfaceRegionSensorVolumeConstraint to produce incorrect access results. The issue has been fixed in this release.
Several points and axes, such as SolarSystemBarycenterCenterOfMassPoint, SolarSystemBarycenterInertialFrame, and EarthCentralBodyInertialFrame, can now be directly evaluated. Previously, they would throw an exception. Observing points and axes using GeometryTransformer remains the preferred technique in nearly all cases.
Changed SphericalHarmonicGravityModel file parsing to be case-insensitive with respect to labels.
Corrected documentation for AxesVehicleVelocityLocalHorizontal which incorrectly stated that the axes directions were defined relative to the inertial frame.
Fixed an issue that could cause an infinite loop when freezing ForceModel objects.
The documentation for PointCentralBodyProjection now uses the term "direction" instead of "heading".
Documentation for ScalarAtmosphericDensitySetApparentSunPosition and ScalarAtmosphericDensitySetTrueSunPosition now state that the vector position of the Sun originates at the CentralBody and not at the Earth.
Removed the following items, which were marked obsolete in a previous release: SignalPolarization, AccessConstraintCollection.ConstraintAdded, AccessConstraintCollection.ConstraintRemoved, PlatformCollection.PlatformAdded, PlatformCollection.PlatformRemoved, StkEphemerisFile.CreateCovarianceIntepolator.
The following methods on KeplerianElements have been marked obsolete:
Use the methods on OrbitalElements instead.
TimeConstants.PicoSecond has been marked obsolete and will be removed in a future release.
ChildrenExtension.FindDescendents was misspelled and has been marked obsolete. Use ChildrenExtensionFindDescendants instead.
Added CentralBodyLayeredProjectedVolumeAccessConstraint, which creates a layered volume from unorganized input points about a central body when supplied with altitude layers. In each layer, a 2D convex hull is created from the points that fall within that layer, and extruded from the bottom to the top of the altitude layer. This layered volume can then be used as an access constraint.
Added support to the Cesium library for the following CZML features:
JulianDate, GregorianDate, and Duration now ensure that their values do not overflow when being constructed, or when performing arithmetic, and throw an exception as soon as a value is detected that is outside the valid range of values that can be stored.
The performance of CentralBodySurfaceRegionSensorVolumeConstraint has been improved for most use cases.
The fidelity of the range calculations in CloudFogAttenuationModelItuRP840 have been improved to match current versions of STK Desktop.
Corrected several issues with TiremPropagationModel3_18:
The height above terrain of the transmitter and receiver were not correctly calculated, which could lead to negative height values and cause incorrect results or exceptions.
The default parameters for the model have been adjusted to be in line with current versions of STK Desktop. Specifically, SurfaceConductivity, SurfaceHumidity, SurfaceRefractivity, and SurfaceRelativePermittivity now default to more realistic real-world values.
TerrainSamplingStep now defaults to null, and the sampling value will be calculated dynamically based on the resolution of the configured TerrainProvider. The property can be set to override this behavior.
Additional validation is done at propagation time to ensure that the inputs to the TIREM algorithm are produced correctly. The transmitter and receiver height above terrain must be above 0.6 meters and below 30,000 meters. The terrain sampling must produce at least one additional terrain height sample between the transmitter and receiver. If the transmitter and receiver are extremely close, this may require reducing the TerrainSamplingStep.
Fixed an issue where GregorianDateToIso8601String incorrectly rounded the date to the specified number of decimal digits before writing the string.
Fixed an issue where incorrect units were used when calculating the derivatives for the following IAU orientation axes. The orientations were correct, but the rotation rates were not.
The following types contained code which created and then disposed a temporary evaluator while creating another evaluator:
In rare situations, this could result in that disposed evaluator being reused in unrelated calculations within the same EvaluatorGroup. These temporary evaluators are no longer disposed.
Fixed an issue where a configuration exception could be masked by a spurious NullReferenceException in CoverageDefinitionOnCentralBody.
In the previous release, several changes included in the release were inadvertently omitted from the What's New. These items have been added to the section for the previous release.
CesiumGenerator and related classes now operate on IServiceProvider items. Previously, this system accepted items of type Object, but in practice, CZML generation always required IServiceProvider items.
BingMapsStyle.Hybrid has been marked obsolete. Microsoft now calls this map style BingMapsStyle.AerialWithLabels.
Removed the following types, methods, and properties, which were marked obsolete in a previous release: ScalarDependentOnLink, SignalParameter.Instance, CartesianParameter.Instance, DoubleParameter.Instance, Curve.ArcLength, Curve.InterpolateUsingArcLength, EvaluatorHelper.CollectionsAreSameEvaluatorHelper.Dispose overload taking a boolean, SegmentResults.AddEphemerid, RinexObservationHeader.TimeOfLastObservaton, and PropagateSegmentResults.AddStoppingConditionBackwardsAdapters overload taking a StoppingCondition.
Added StkTerrainServer which can read terrain data from STK Terrain Server, either over the internet or from your own local server.
Added PhasedArrayGainPattern for modeling planar phased array antennas. This gain pattern is configured using a list of PhasedArrayElement objects. Forming antenna beams and nulls is handled by a PhasedArrayBeamformer, such as MinimumVarianceDistortionlessResponseBeamformer (MVDR), which is responsible for computing each element's complex weights.
Added a new access constraint, CentralBodySurfaceRegionConstraint, which can be used to determine if an object is within a given surface region.
The demo applications included with STK Components have been refactored and improved to load data online by default, and fall back on offline data files when run in an offline environment.
AzimuthElevationMask no longer requires the first and last ElevationMask values to have azimuths of 0 and 2π, respectively. The values must still be sorted by azimuth in increasing order, and azimuths must not wind.
Fixed an issue with RectangularFilter where an exception was thrown if the input signal's lower bandwidth limit was equal to the filter's upper bandwidth limit, or if the input signal's upper bandwidth limit was equal to the filter's lower bandwidth limit.
BingMapsForEnterpriseImageGlobeOverlay previously used a web service which has been discontinued by Microsoft, preventing the globe overlay from working. It has been updated to use the currently supported web service to retrieve imagery metadata.
Several properties have changed from CesiumProperty<double> to CesiumProperty<int>. These properties always required integer values in order to render without error, and the new type makes this more clear.
Several of the properties on GpsSatelliteInformation have been replaced by better-named properties.
SemAlmanacRecord.SpaceVehicleNumber has been marked obsolete. Use SatelliteVehicleNumber instead.
Sgp4EstimationInput.OutputEpoch has been marked obsolete. Use RequestedEstimationEpoch which makes it more clear that the resulting epoch may be be different if it occurs during a leap second.
SegmentPropagatorVariable.CreateSettings is now obsolete. Use SegmentPropagatorVariableEvaluatorCreateSettings instead.
The LeapSecond constructor taking a JulianDate previously reinterpreted the numeric day count in the UTC TimeStandard, regardless of the TimeStandard of the JulianDate, which could lead to unexpected results. Now, it requires that the given date is in UTC, and throws if it is not.
Added RainAttenuationModelItuRP838, which implements the ITU-R P.838 rain attenuation model.
Added independent and dependent variable scaling to NewtonRaphsonMultivariableFunctionSolver, configured using the new SolverVariableSettingsScaling and SolverConstraintSettingsScaling properties, as well as to the differential corrector in the Segment Propagation Library, using the new SegmentPropagatorVariable.Scaling and SegmentPropagatorConstraint.Scaling properties.
Added new functions to automatically download data over the internet from AGI servers. See:
Added support to the Cesium library for the following CZML features:
API methods use JetBrains ReSharper Annotations to indicate information useful for static code analysis, such as whether a parameter or return value can be null or not, whether a method is pure (has no side effects), and other information. These attributes were originally added in 2016r2. Not all API methods have been marked with this information yet. Coverage will increase over time in future releases. To be clear, ReSharper is not required to use STK Components. If you do not, then these attributes have no effect.
StkEphemerisFile can now load ephemeris files containing time information expressed in the time formats GPSG, UTCG, TAIG, and TDTG.
The algorithm used to compute geodesic curves on an ellipsoid has been improved. See the documentation for EllipsoidGeodesic for details.
Sgp4PropagatorEstimateElements now adds 1 second to a requested epoch that falls during a leap second. This avoids issues with creating a TwoLineElementSet because the TLE format cannot represent an epoch that is during a leap second. This behavior can be configured using the Sgp4PropagatorSgp4EstimationInputAllowEstimationEpochDuringLeapSecond property.
Added new static helper methods to CesiumResource to create an instance from an image or from a stream.
The look and feel of the documentation has been improved, and the content has been revised throughout.
Fixed an issue with EllipsoidGeodesic that prevented computing the distance between two points that did not have a unique geodesic solution connecting them.
Fixed an issue with RainAttenuationModelItuRP618 with a configured CustomRainRate. The custom rain rate is now correctly expected to be in meters per second, and is documented as such. Previously, the value was treated as millimeters per hour.
Fixed an issue when writing TwoLineElementSets with values for BStar or MeanMotionDotDot that require leading zeros in the mantissa in place of digits greater than the maximum allowable in the exponent.
The set of LeapSeconds parsed from an EarthOrientationParametersFile and available from the EarthOrientationParametersLeapSeconds property were incorrect, and have been corrected. These leap seconds are for informational use, and are not used for analysis by STK Components.
Writing a LeapSecondFile previously produced unexpected output for the epoch of the rate at which the UTC time scale is slowing with respect to TAI. This data is not used, but by definition this value should always be 41317.
Added Iau2009Orientation, which provides central body orientation parameters using data from the 2009 IAU report.
Added support to the Cesium library for the following CZML features:
Added implicit conversions for the following types: string to SignalIdentifier, and double to ScatteringCoefficient. The existing implicit conversion operators were: from string to StringSignalIdentifier, and from double to ConstantCrossSectionScatteringCoefficient. The conversions to the base type are generally more useful, because the situations where you typically use them involve the base types (such as assigning a value to a property).
Fixed a bug when writing CZML with a CompositePoint or CompositeAxes where the axes or points contained by the composite could be evaluated outside of the interval over which the composite contains them, which could cause an exception while sampling.
Fixed an issue where DenseMatrix computed its hash code incorrectly.
NumericalPropagator now wraps exceptions caught during propagation in a NumericalPropagationException, and throws if there are no registered handlers for the ExceptionDuringPropagation event. If you want to ignore exceptions during propagation, register a handler for this event that does nothing.
The following events have been marked obsolete and will be removed in a future release: AccessConstraintCollection.ConstraintAdded, AccessConstraintCollection.ConstraintRemoved, PlatformCollection.PlatformAdded, and PlatformCollection.PlatformRemoved.
StkEphemerisFile.CreateCovarianceIntepolator was misspelled and has been replaced by CreateCovarianceInterpolator.
The Polarization and AntennaPolarizationLoss properties have been removed from FrpaGainPattern, and the AntennaPolarization and AntennaPolarizationLoss properties have been removed from GpsCommunicationsFrontEnd and IGpsCommunicationsReceiverConfiguration. Polarization efficiency loss is now modeled using the new Polarization classes.
Added CentralBodyEllipticCylindricalAccessConstraint, which determines access based on whether the constrained object is within a cylinder (elliptic or circular). This new constraint can be combined with the existing AltitudeConstraint to model an airspace constraint.
Added the ability to dynamically model polarization efficiency loss based on the communications link geometry. Polarization efficiency loss is now enabled by configuring a RadioFrequencyTransmittingAntennaExtension and RadioFrequencyReceivingAntennaExtension with the appropriate PolarizationSource.
Added JplDE430, which loads JPL DE430 ephemeris data.
ImpulsiveManeuverSegment will now honor the Orientation of the ImpulsiveManeuverInformation, and the StateElementAdapter for the propagated point, when run as a single segment, or when it is the first segment in a sequence producing ephemeris. This requires a StateElementAdapter to be set for the propagated point in those cases. If an adapter for the point is specified on an ImpulsiveManeuverSegment and it is not the first segment producing ephemeris, that adapter will be used at propagation time when producing the ephemeris.
Improved the exception message thrown by Sgp4Propagator when estimation of orbital elements fails.
LifetimeOrbitPropagator has been changed to match recent changes in STK. Specifically, a correction has been made to the J2^2 effects to eliminate unexpected eccentricity growth which could result in prediction of orbital lifetimes that were too short.
Fixed a bug when writing CZML that caused auxiliary properties, such as reference frame, interpolation settings, etc., to be incorrectly omitted from subsequent intervals after the first when using an interpolator with segment boundary times. These auxiliary properties are scoped in CZML at the interval level, so they must be included in all intervals in order to be loaded correctly.
Fixed an issue where an AxesAlignedConstrained would produce the incorrect orientation when configured with the principal axes as the AxisIndicator.Second and the reference axes as the AxisIndicator.First.
Fixed a bug in MultivariableFunctionDifferentialSolver where the maximum step of variables was misapplied. This fix will improve the numerical stability of the differential corrector.
Fixed an issue where EllipsoidSurfaceRegionIsPointInsideRegion could return incorrect results in cases where the region under consideration is very large relative to the size of the central body.
Fixed incorrect coefficients in finite differencing in the Route Design Library that affected derivatives in certain edge cases.
Subclasses of InterpolationAlgorithm must now implement IEquatableDefinition by implementing CheckForSameDefinition and ComputeCurrentDefinitionHashCode. Typically, most algorithms have no state, so definitional equality is solely determined by the type.
BoundingRectangle has been moved from Insight3D to the AGI.Foundation.Coordinates namespace in the Core library. Additionally, the Width and Height properties previously returned incorrect results and have been corrected.
In the Cesium library, BillboardGraphicsAlignedAxis has been changed to a CesiumProperty<UnitCartesian>. The value was always required to be unit magnitude in order to work correctly in Cesium, but the new type enforces this constraint.
SegmentResultsStateForNextSegment is no longer settable.
In the Curve class and all subclasses, ArcLength was inappropriately named and has been marked obsolete. Use the more accurately named AngleSubtended property instead. Similarly, InterpolateUsingArcLength is obsolete and replaced by InterpolateUsingAngleSubtended.
The approach for cloning functions used with SolvableMultivariableFunction has changed. As such, the CreateClonesOfFunctionForParallelEvaluation methods are now obsolete, and SolvableMultivariableFunctionOperationsComputeJacobianNumerically no longer takes an array of cloned functions.
The overload of PropagateSegmentResultsAddStoppingConditionBackwardsAdapters taking a StoppingCondition has been marked obsolete. Use the overload taking a SegmentDefinition.
In EvaluatorHelper, CollectionsAreSame has been marked obsolete and will be removed in a future release. Also, the overload of Dispose taking a boolean flag has been marked obsolete. Instead, use the overload that does not take a boolean flag.
Removed the following types and properties, which were marked obsolete in a previous release: GainPattern, ReceivingAntennaExtension, TransmittingAntennaExtension, CraneRainAttenuationModel.UseRainRateOverride, CraneRainAttenuationModel.RainRateOverride, CraneRainAttenuationModel.UseRainHeightOverride, CraneRainAttenuationModel.RainHeightOverride, RainAttenuationModelItuRP618.UseRainRateOverride, RainAttenuationModelItuRP618.RainRateOverride, RainAttenuationModelItuRP618.UseRainHeightOverride, RainAttenuationModelItuRP618.RainHeightOverride, InvalidFuelStateException.PropagationElementThanRanOut.
Introducing the Radar Library, which allows for modeling radar signal propagation, processing, and data products.
Added the ability to model communications signal point scattering using the new PointScattererExtension and associated ScatteringCoefficient types. TargetRadarCrossSectionExtension derives from PointScattererExtension and is used to model radar signal reflection from target objects.
Added CesiumPositionExtension and CesiumOrientationExtension. These new extensions can be used to configure details about how position and orientation information is written to CZML, such as interpolation and extrapolation settings.
Added support to the Cesium library for the following CZML features:
Added VelocityVectorDirectionCesiumProperty, which is a CesiumProperty<UnitCartesian> which specifies that the value will be computed on the client to be the direction of the velocity vector of a given object.
Added LeapSecondFileDownloadLeapSeconds to automatically download the latest leap second data file over the internet from AGI servers.
Added the December 2016 leap second to the default LeapSecondsFacet.
Added a topic to the documentation explaining external data files used in Components. See the External Data.
DurationStoppingCondition now uses the absolute value of the threshold by default.
Added StateElementAdapterHelpers with static methods to help in creating adapters to and from segments.
SegmentPropagator, SolvableMultivariableFunction, and related classes now have an ApplyResults method to assist in setting state on the object that normally gets set during evaluation or propagation. This method allows those objects to continue from where another run left off, which can reduce run times.
The Cesium library now properly uses SegmentBoundaryTimes from interpolators when writing CZML, to automatically separate samples into multiple intervals. SampledCesiumProperty<T> now has a list of SegmentBoundaryTimes.
EarthOrientationParameters loaded from a file now indicate the intervals of time over which data is observed or predicted. It also now provides a list of leap seconds specified in the file.
Reference frame transformations are now validated against the latest version of the Standards of Fundamental Astronomy (SOFA) Libraries, Issue 2016-05-03.
Previously, ephemeris would not be constructed properly for SegmentLists whose child segments were going in different directions in time, or if there were time discontinuities in the segments. This has been corrected.
Auto-sequences in a PropagateSegment are now reported in the original propagate segment's defined-in axes and frame.
SegmentListResults that are completely eclipsed by later overlapping segments now have no ephemeris in its ephemeris lists.
Fixed an issue where Covariance3By3SizeAndOrientationInterpolator modified CovarianceData while getting an evaluator, causing evaluator caching to fail. Getting an evaluator now correctly leaves the definitional object unmodified.
Corrected a race condition that could cause the number of worker threads used to parallelize calculations to be incorrectly determined to be zero, leading to a crash.
Fixed an issue in Ellipsoid that could cause tangent points to be returned that were slightly off the ellipsoid.
Fixed an issue where PointAtAltitude would throw an exception if requested to evaluate at an order higher than it was capable of.
Corrected documentation for Sgp4PropagatorReferenceFrame which incorrectly stated that the frame was TEME of Epoch.
Significant refactoring was done to the Segment Propagation Library that in many cases were not able to be made in a backwards compatible way. Please contact AGI support if you need assistance in upgrading to this new version.
IGeneralState and IMotionState have been removed; all of their responsibilities are now on ITimeBasedState. The Segment Propagation Library now only propagates ITimeBasedStates as opposed to IMotionStates. All operations with stopping conditions that use a state, and methods in StoppingConditionEvaluators, now operate on ITimeBasedStates.
As the SolvableMultivariableFunction has a default implementation of computing the Jacobian numerically, the events for a normal function evaluation and a function evaluation done as part of computing a perturbation have been moved to the base type and off of the TargetedSegmentListFunction.
StateElementAdapterFactory has been renamed to StateElementAdapterDefinition and all adapters have been redesigned to now follow the normal create-set-call pattern of Components.
The base StoppingCondition no longer has a Threshold property, but instead has a method that creates the threshold when needed. The derived stopping condition types all have their own Threshold property.
The thresholds on StoppingConditions and the DesiredValue of SegmentPropagatorConstraints are now both ValueDefinition<T> objects instead of doubles. This allows them to be varied by a higher level computation (such as a TargetedSegmentList and TargetedSegmentListDifferentialCorrector) using a ParameterizedValueDefinition<T>. This also led to the removal of IKnownDateStoppingCondition, IKnownDateStoppingConditionWithMutableThreshold, StoppingConditionWithMutableThreshold, StoppingConditionWithMutableThresholdEvaluator, and all TargetedSegmentListOperatorConfiguration types.
The segment configuration parameter passed to SegmentPropagatorPropagate is now a SegmentConfiguration type as opposed to a ICloneWithContext. This new configuration type has a property letting you know if the segments are being run nominally or not.
The signature for many of the Propagate methods on SegmentPropagator and SegmentListPropagator have been changed to not take an initial state. The initial state is now a property on the SegmentConfiguration.
The following StateElementAdapterDefinitions were removed:
StoppableNumericalPropagatorResponse was removed.
The OriginalConfiguration property on SegmentPropagator was removed.
The existing TargetedSegmentListOperatorConvergenceBehavior values have been replaced with better named values.
NumericalPropagatorSegmentResults was removed and replaced with PropagateSegmentResults.
NumericalPropagatorSegmentConfiguration was removed and replaced with PropagateSegmentConfiguration.
ImpulsiveManeuverInformation now has a ParameterizedPoint that represents the position and velocity of the space object being propagated. This point must be used in defining geometry types that rely on the spacecraft's motion, including the ImpulsiveManeuverInformationOrientation.
The InnerParameterEvaluator of the ImpulsiveManeuverInformation has been removed.
The following static properties have been marked obsolete: SignalParameter.Instance, CartesianParameter.Instance, and DoubleParameter.Instance. Rather than using these global singleton parameters, construct instances of the appropriate parameter type where needed, and use those parameters in your problem definitions.
ScalarDependentOnLink has been marked obsolete. Use the new ScalarDependentOnServiceProvider class instead. The properties on various Communications Library types have been changed to the new type.
The TargetedSegmentListOperatorGetOperatorEvaluator method no longer takes the parent propagator as an argument.
Removed the following types, methods, and properties, which were marked obsolete in a previous release: HashCode.FinalizeHash, Signal.LowerNoiseBandwdithFrequency, TransmitterIdentifier. Removed a MultivariableFunctionSolverIterationResults constructor taking an array of function evaluations.
Introducing the Aircraft Propagation Library, which provides several maneuver definitions and performance models that can be used to propagate an aircraft.
IAdjustableState allow for new elements to be added or removed from states that implements this interface.
Points, Scalars, and Vectors can be parameterized on states now with the ParameterizedOnStatePoint, ParameterizedOnStateScalar, ParameterizedOnStateVector types. The new parameter type for these geometry types is TimeBasedStateParameter.
The Semi-major axis can now be specified as a KeplerianElement.
The ability to propagate a NumericalPropagator until a StoppingCondition was satisfied has been broken out into an abstract StoppablePropagator class. These propagators create a StoppablePropagatorResults. The following derived types were added:
As part of this refactoring, many bugs were addressed.
ChangeStoppingConditionThresholdOperator<T> allows a callback to be defined to change the Threshold of a StoppingCondition when run in a TargetedSegmentList. This can be used, for example, to round a value derived by a differential corrector that ran before this operator.
Segments can now be designed to not define the elements getting propagated, but instead, just pass all of the elements and their StateElementAdapters from the previous segment to the next.
SegmentDefinition now has virtual methods that let you set, get, check, and remove the elements getting propagated and their adapters and defined-in objects. These methods can be overridden as needed and many segments will call them automatically.
ImpulsiveManeuverSegment can now be run as a single segment independent of any other segments.
ReturnSegment will end propagation for a specified SegmentDefinition that the ReturnSegment is a part of, with options to be enabled or disabled if the wrapping segment is being run in a TargetedSegmentListOperator. All SegmentResults now have a StopPropagationForCurrentSegmentList property.
StopSegment will stop all propagation if enabled and encountered.
UpdateSegment allows you to define discrete changes to specific elements in the previous segment.
PropagateSegment is now the base class of the existing NumericalPropagatorSegment. PropagateSegment can work with any StoppablePropagator. New propagate segments have been added deriving from this type.
ChangePropagateSegmentsPropagatorOperator will change the StoppablePropagator of a PropagateSegment when the operator runs in a TargetedSegmentList. Note that this will change the StoppablePropagator for any type of PropagateSegment even if the segment used could not have been initially configured with the type of StoppablePropagator that it is getting changed to.
The following SegmentPropagatorConstraints have been added or expanded:
ScalarDifferenceOfSegmentConstraint which will return the difference of a value between the start and end points of a segment.
Added the following geometry types:
Added USStandardAtmosphere1976 which provides Scalar objects for computing atmospheric density, temperature, pressure, speed of sound and density ratio using the U.S. Standard Atmosphere model, 1976 version.
Added overloads of StkEphemerisFileWriteTo(TextWriter, Boolean) and StkAttitudeFileWriteTo(TextWriter, Boolean) that pretty-format the files with aligned columns. Properties are now written to the file in a consistent order, and added support for writing files version-tagged as STK 11.
All StateElementAdapters have been moved to the Models library.
SolvableMultivariableFunction now has a helper method to create clones of itself suitable for the default numerical computation of the Jacobian matrix.
StoppingConditions will now obey their FunctionTolerance. Before, the stopping condition could be satisfied even if the root finding did not converge within the specified tolerance. The RequireFunctionTolerance property was added to allow the condition to be satisfied even if it does not converge to within the tolerance.
InitialStateSegment<T> is no longer abstract.
Added support for model node transformations (also known as articulations) in the Cesium library. See ModelGraphicsNodeTransformations.
Added support to the Cesium library for drawing polylines on the surface of a central body. See CentralBodySurfaceCurveGraphics.
Added the following properties to the Cesium library:
Added support for sending CZML delete packets. See CesiumDeleteExtension.
Added new functions to automatically download data over the internet from AGI servers. See:
Fixed an issue where a non-thread-safe AccessConstraintEvaluator was not always copied before being used from another thread, specifically when evaluating access with an interval collection with more than one interval, and when one of those intervals is zero-duration.
Fixed an issue where ScalarOccultation could throw an exception in rare cases where a platform is very far away from a central body.
Corrected an issue where CZML name and parent properties would only be written if the item also had other CZML graphical properties defined. These properties are now written by new NameCesiumSource and ParentCesiumSource objects.
The following properties have changed from double to ScalarDependentOnLink, allowing the values used by the models to vary based on time, or the positions of transmitter or receiver. A constant double value can be implicitly converted to a ScalarDependentOnLink.
Several types that were specific to RF communications have been renamed, and the previous version are now obsolete. Specifically, GainPattern is replaced by RadioFrequencyGainPattern, ReceivingAntennaExtension is replaced by RadioFrequencyReceivingAntennaExtension, and TransmittingAntennaExtension is replaced by RadioFrequencyTransmittingAntennaExtension.
The following properties are now obsolete:
Instead, customize the models using these new properties:
InvalidFuelStateException.PropagationElementThanRanOut was misspelled and has been marked obsolete. Use InvalidFuelStateExceptionPropagationElementThatRanOut instead.
You can now specify custom weather-related values that vary with time or position when using signal propagation models in the Communications Library, by providing a ScalarDependentOnLink instance. Previously, these values had to be constant values.
Added an optical antenna gain pattern, GaussianOpticalGainPattern, for modeling the beam profile of the transmit or receive optics. The model takes the aperture diameter and divergence angle as input and also includes the ability to provide a fixed pointing offset from the link line-of-sight vector.
Added TropoScintAttenuationModelItuRP1814, which implements the ITU-R P.1814 (Section 5 Scintillation effects) tropospheric scintillation propagation loss model for modeling scintillation loss in the optical frequency band. The model can use a custom RefractiveIndexStructureParameterModel, or by default uses the new HufnagelValleyRefractiveIndexStructureParameterModel, which implements the Hufnagel-Valley (H-V) model.
Added BeerLambertLawAtmosphericAttenuationModel, which implements the Beer-Lambert Law atmospheric absorption model for modeling atmospheric absorption/scattering in the optical frequency band.
Added ModulationOok, which implements the On-off Keying (OOK) modulation scheme, typically used in digital optical communications, for modeling Bit-Error-Rate vs Eb/No.
Added PointAtAltitude which projects a reference point's motion onto a surface of constant altitude.
Added overloads of TimeIntervalCollection<T>.Remove and TimeIntervalCollection<T>.RemoveLeavingEndpoints that take a TimeInterval. Previously, a TimeInterval<T> was required, even though the data was ignored.
An optimization has been added to improve function trending when exploring extrema to find potential threshold crossings but not requiring that the extrema be found precisely.
AccessQuery now honors the ExtremaCrossingUncertaintyFactor of the AccessConstraintSampling. The default value for the uncertainty factor has been changed to a conservative value, in order to prevent false negative results from access (missed satisfaction intervals).
Fixed an issue that caused an exception to be thrown, incorrectly indicating that data is not available, when computing access with a CommunicationObjectConstraint over an interval that exactly matches the availability of the transmitter.
All EqualsEpsilon methods (for example, CartesianEqualsEpsilon) now return true when the difference in value is exactly equal to the epsilon value. Previously, it only returned true if the difference was less than epsilon.
Fixed an issue with the default constructor for ComplexDigitalTransmitter which switched the default power and frequency values, causing it to incorrectly use a transmit power of 14.5e9 Watts and a frequency of 1000.0 Hz, rather than the documented power of 1000 Watts and frequency of 14.5e9 Hz.
The pattern for implementing definitional objects has changed. In general, classes that derive from DefinitionalObject must override protected methods from their base class and call the base implementation, augmenting the process of checking if two objects have the same definition. See the documentation for DefinitionalObject for more information on implementing the pattern correctly.
TransmitterIdentifier is now obsolete. See below for related changes to how IntendedSignalByTransmitter identifies signals.
Removed the following types, methods, and properties, which were marked obsolete in a previous release: CentralBodyObstructionConstraint.GetDegreeOfObstruction, ScalarDensityJacchiaRoberts.UseApparentSunPosition, MarkerBatchPrimitive.AlignToPixel, ProjectedRasterOverlay.
HashCode.FinalizeHash is now obsolete. Hash codes are finalized automatically when calling the Combine methods.
Signal.LowerNoiseBandwdithFrequency was misspelled and has been marked obsolete. Use LowerNoiseBandwidthFrequency instead.
Access Queries can now optionally log debugging information about constraint satisfaction. See AccessQueryDebuggingLogger.
All assemblies are now digitally signed by Analytical Graphics, Inc.
IntendedSignalByTransmitter now identifies transmitters of a signal by checking for a specified SignalIdentifier, rather than using a direct reference to the transmitter itself. A new service, IIdentifiableTransmitterService, has been added to existing transmitter types to configure the identifier for that transmitter's signal.
SolvableMultivariableFunction now computes its derivatives. By default, the first derivative will be computed numerically. Derived types can override the method if the derivative can be computed analytically. A related helper method, SolvableMultivariableFunctionOperationsComputeJacobianNumerically has been added.
The numerical derivative computed by SolvableMultivariableFunction and TargetedSegmentListDifferentialCorrector can now be computed with a forward, backwards, central or signed difference method. See FiniteDifferenceMethod.
Improved LifetimeOrbitPropagator implementation to better predict decay of eccentric orbits.
The hash algorithm used by HashCodeCombine has been replaced with the MurmurHash3 algorithm.
Fixed an issue in EllipsoidEllipsoidSeparationDistance which would cause incorrect results for greatly distorted ellipsoidal shapes.
Fixed an issue in ComplexReceiver that prevented successful cloning.
Fixed an issue in ScalarDensityJacchia1970 which was reporting incorrect densities below the minimum altitude height of 90 km. It now returns the density at 90 km when evaluated below 90 km.
Fixed an issue in ScalarDensityMsis90 where daily and average F10.7 solar flux index values were incorrectly passed to the computational algorithm causing the values to be swapped.
Restored documentation of a number of Insight3D types, which was omitted in previous releases.
In rare cases with overlapping ellipsoids EllipsoidEllipsoidSeparationDistance would throw an exception rather than successfully calculating the answer.
This release includes an updated Software License Agreement.
In some cases terrain height could be calculated incorrectly when performing signal propagation with TiremPropagationModel3_18.
In rare cases EllipsoidGeodesicHeading could calculate the wrong heading when very close to an equatorial crossing.
64-bit binaries of the Insight3D library are now available.
Fixed a crash which could occur when trying to generate CZML for an object whose ephemeris had segment boundary times.
All example solutions previously targeted to VS 2005 are now targeted to VS 2008.
CssiSolarGeophysicalData was not thread safe.
Improved performance when using a NewtonRaphsonMultivariableFunctionSolver in multiple threads.
Fixed a possible race condition in NewtonRaphsonMultivariableFunctionSolver.
Fixed a possible race condition when using TargetedSegmentListDifferentialCorrector in certain configurations.
Fixed a possible race condition when calling DefinitionalObjectGetDefinitionHashCode in certain cases.
TargetedSegmentList.ResetNestedTargetedSegments was replaced with TargetedSegmentListResetBetweenRuns. It is now the responsibility of a TargetedSegmentList to reset itself between runs if necessary, rather than determine whether its children must be reset.
Removed the unused ParentSegment property from TargetedSegmentListOperator.
Moved ImpulsiveManeuverSegment and related types from AGI.Foundation.OrbitPropagation.dll to AGI.Foundation.SegmentPropagation.dll. In addition, many abstract types were moved from AGI.Foundation.SegmentPropagation.dll to AGI.Foundation.Models.dll.
Added PrescribedAccelerationTransitionProfile, which allows users to specify a route profile which will apply a given thrust acceleration or deceleration over the inclined or level traversal between two waypoints.
Fixed a bug where constructing an EllipsoidSurfaceRegion larger than half of the ellipsoid's surface would result in the Centroid property representing the centroid of the area outside of the region rather than the inside of the region.
Fixed improper formatting with some of the exception messages thrown by KozaiIzsakMeanElements.
The abstract UseDailyFlux property has been removed from the abstract base class SolarGeophysicalData, as not all derived types need to handle this behavior.
Deprecated the UseApparentSunPosition property on ScalarDensityJacchiaRoberts. Instead, use the new VectorToSun property on the ScalarAtmosphericDensity base class to set the Vector directly. The new helper methods SetApparentSunPosition and SetTrueSunPosition can be used to easily set the most common cases.
A single CentralBodiesFacet and a single LeapSecondsFacet instance are now consistently shared among all threads by default. To explicitly give a thread its own separate instance, construct a new instance and call CentralBodiesFacetUseInCurrentContext or LeapSecondsFacetUseInCurrentContext in that thread.
Several DLLs related to decoding videos are no longer statically linked in AGI.Foundation.Graphics.dll. They must now be copied into the bin directory when a graphics project is built. For more information see the Getting Started topic or the HowTo.
Introducing the Segment Propagation Library, which allows for the modeling and targeting of trajectories or other states where the propagation changes over time.
Added CssiSolarGeophysicalData, allowing CSSI space weather files to be read in and used with supporting density models.
Added many types to easily represent components of multi-dimensional entities as Scalars. These include: ScalarPointElement, ScalarVectorElement, ScalarSphericalElement, ScalarCartographicElement, and ScalarModifiedKeplerianElement.
Added AxesVelocityOrbitNormal to represent the Vector Normal Co-normal axes.
Added AxesBPlane to represent the axes aligned to the B-Plane.
Added ScalarDeltaSphericalElement to represent the delta-declination and delta-right ascension between two points and their common 'center'.
Added LifetimeOrbitPropagator to calculate long-term mean orbital elements and expected reentry time.
Added ScalarDensityJacchia1970 which calculates atmospheric density according to the Jacchia 1970 model.
Added overloads to the EllipsoidSurfaceRegion static construction methods to allow the user to manually specify a reference point as being inside or outside of the region. This allows for the definition of regions larger than half of an Ellipsoid.
ProjectedRasterOverlay has been deprecated and replaced with the new primitive ProjectedRaster, which projects images and video onto terrain or the central body surface and contains the same functionality as the old ProjectedRasterOverlay class, but with some performance and visualization enhancements.
MathPlayer is no longer used in our documentation and has been removed from the install.
Added BallisticPropagator which allows for the easy calculation of two-body trajectories from and to fixed locations on a CentralBody. Solutions for minimum energy, minimum eccentricity, or matching specified values of delta-V, flight duration, or apogee altitude can be found.
Texture2DFactory can now create mipmap compatible textures.
Further significant improvements to the performance of CentralBodySurfaceRegionSensorVolumeConstraint.
TimeIntervalCollectionContains no longer throws an exception if called on an empty collection.
In rare cases ScalarOccultationDualCone could return NaN instead of a valid result.
CentralBodySurfaceRegionSensorVolumeConstraint could return false positives when wide sensors were used.
MarkerBatchPrimitive could use the wrong cached shader when using per batch distance display conditions, causing the markers to be visible even when they did not meet the display conditions.
We now use the same user agent for requesting both Bing map tiles and Bing metadata.
Function explorers (DoubleFunctionExplorer, DurationFunctionExplorer, and JulianDateFunctionExplorer) used to precisely find all extrema that may potentially result in threshold crossings if the ExploreExtremaToFindCrossings property was set to true. Now they exit out of those calculations early if it is very unlikely that the current extrema will result in a threshold crossing, based on the value of their ExtremaCrossingUncertaintyFactor property. Setting this property to DoublePositiveInfinity will retain the old functionality. AccessConstraints do not expose their function explorers, but JulianDateFunctionSampling has an ExtremaCrossingUncertaintyFactor property.
Optimized CentralBodySurfaceRegionSensorVolumeConstraint. Users should see a dramatic performance improvement, from 8 to 20 times faster computation times.
JulianDateFunctionExplorer was modified to stop calculating the precise location of extrema when it is evident that they will not lead to a threshold crossing, which provides a performance boost to many functions, especially Access and Coverage calculations.
GeospatialImageGlobeOverlay can now load a much larger variety of image file types.
Some CachingMotionEvaluators would not properly dispose the evaluator they were caching when they themselves were being disposed.
The SatelliteOutage class was reading times in UTC but marking them as being written in the GPS time standard.
Several bug fixes should make viewing KMLs much more stable.
Fixed a memory leak from displaying a Balloon.
A large number of types and members have been removed in this release. These items were all marked obsolete in previous releases. Please contact AGI support if you have difficulty adjusting your code to work with this release.
CentralBodyObstructionConstraint.GetDegreeOfObstruction is now obsolete. Please use EllipsoidGetDegreeOfObstruction instead.
NumericalPropagationStateHistory.Insert has been removed.
The result of NumericalPropagationStateHistoryGetDateMotionCollectionT is now ordered chronologically, regardless of the sorting of the history itself. This allows the returned collection to be used correctly with other objects, such as interpolators, without manipulation. However, this means that if you were previously reversing a collection manually for this purpose, you will need to change that. If a chronologically reversed collection is desired after propagating backwards in time and creating a reversed history, one can still be created by manually calling PropagationStateConverterGetDateMotionCollectionT and passing the reversed time and state lists as parameters.
Added NewtonFindRoot. This new class uses the Newton-Raphson method to solve for the roots of a function.
Insight3D now displays the end-cap (or dome) of a sensor when the FieldOfViewCentralBodyProjectionGraphicsExtensionDisplayEndCap property evaluates to true.
Added a CentralBodyClipped property to MarkerBatchPrimitive, PointBatchPrimitive, PolylinePrimitive, and TriangleMeshPrimitive to control whether or not the primitive is clipped by the Earth or other central body.
Using an AdaptiveNumericalIntegrator to integrate backwards, while that integrator is choosing adaptive steps, and while that integrator is truncating those adaptive steps, will no longer cause an erroneous exception to be thrown.
Fixed several memory leaks in Insight3D.
Added the Navigation Advanced Library, which builds on the Navigation Accuracy Library and the Communications Library by considering how communication links contribute to GPS errors. GPS transmitters, signals, and a GPS receiver communications front end are modeled, allowing for GPS link budgets to be used in analysis, and to determine tracking using Carrier to Noise thresholds.
Added CentralBodySurfaceRegionSensorVolumeConstraint to constrain access based on whether a sensor can see part of a surface region (or area target) on the ground.
Added ModulationFsk to support Frequency Shift Keying (FSK) modulation.
Fixed a bug that could lead to generating coverage grids with missing grid points.
Fixed a bug where TerrainAzimuthElevationMask would throw an exception for some requested numbers of azimuth steps.
Fixed a bug in EllipsoidSurfaceCurveGetDiscretePoints which would, in rare cases, cause instances of the inherited classes to provide points which were not dense enough to fulfill the requested granularity.
Fixed a bug that could lead to an exception when computing sensor projections.
Fixed a bug where EllipsoidSurfaceDistance could return NaN if one of the points was very, very close to (but not on) the equator.
Fixed a bug in EllipsoidSurfaceRegionCheckPointInsideRegion that could lead to false results in rare edge cases. This usually manifested as tiny gaps in access intervals calculated by CentralBodySurfaceRegionElevationAngleConstraint.
Fixed a bug in TimeIntervalCollectionToDuration that caused it to throw an exception when the collection contained intervals expressed using different time standards. Now, the returned duration will be expressed using the time standard of the first interval in the collection.
Added WaypointPropagatorConstructConstantVelocityWaypointPropagator which provides a method to easily construct a WaypointPropagator that hits the desired waypoints at the desired times.
Added StkAttitudeFileAttitudeTimeQuaternionsConvertToStkAttitudeConvention and StkAttitudeFileAttitudeTimeQuaternionsConvertFromStkAttitudeConvention methods to transform between the attitude convention used in STK Components and the one used in STK attitude files.
Fixed a bug that could cause GregorianDate to incorrectly interpret invalid dates (such as the 30th day of February) as a year plus a day of the year.
Fixed a bug in StkAttitudeFileConfigureFromAxes that caused incorrect results when using an Axes not supported by the STK Attitude file format. StkAttitudeFileConfigureFromAxes now correctly transforms the input data to a supported Axes.
Fixed a bug where StkAttitudeFileAttitudeTimeQuaternionsAttitudeData was not consistently represented using STK Desktop's attitude convention.
Fixed a bug in Insight3D that could cause imagery overlay tiles to be shown before they were done loading.
The raw IAU 2006 XYS data used to compute International Celestial Reference Frame (ICRF) is now exposed via the Iau2006XysData class.
GregorianDateParseExact now optionally takes an array of acceptable formats.
CollectionAlgorithmsBinarySearch now supports searching a subset of the collection.
JulianDateToString now also returns a standard Gregorian representation of the date and time represented by the instance.
The difference between TAI and UTC specified in Earth Orientation Parameters (EOP) files is now honored when converting sample times to TAI. Previously, the difference according to the LeapSecondsFacet was used, which could be different in rare circumstances. If the previous behavior is desired, it can be restored by setting EarthOrientationParametersReadOptionsInterpretTimesUsingLeapSecondsFacet to true on the options passed to ReadData.
ScalarExponent now produces correct partial derivatives when the exponent varies with respect to the independent variables.
Fixed a bug in GregorianDateToString that could cause it to report incorrect fractional seconds with seconds close to but not equal to zero.
DefinitionObject is now obsolete. Use DefinitionalObject instead.
All definitional objects in the libraries now derive from DefinitionalObject. This gives them all a core set of capabilities, including the ability to be copied and frozen. However, it also means that existing definitional objects in user code must implement some new abstract methods. See the DefinitionalObject reference documentation for more information.
TimeIntervalCollection<T>.Intersect no longer considers a nullData property to be equal to every other value. As a result, consider intersecting with a time interval collection without data or calling IntersectMergingData to control how data is merged in the resulting intervals.
Added GaussianStatistics, containing functions for use with multi-dimensional Gaussian probability distributions like position covariance.
Added CovarianceSeparationConstraint to constrain access based on the range between two objects while taking into account the uncertainty of position of one or both of them.
Added new coordinate type, Covariance3By3Derivative, representing the derivatives of the positional variance and covariance information for an object.
Added new geometry type, DynamicCovariance3By3, to evaluate covariance and its derivatives over time.
Added a STK_COMPONENTS_NO_DEFAULT_LEAP_SECONDS environment variable that, when set, prevents the libraries from using a default table of leap seconds. As a result, if a table of leap seconds is not explicitly given, the libraries will throw an exception when leap seconds are required.
Added a STK_COMPONENTS_NO_DEFAULT_EARTH_ORIENTATION_PARAMETERS environment variable that, when set, prevents the libraries from using a default table of EarthOrientationParameters (EOP) data. As a result, if EOP data is not explicitly given, the libraries will throw an exception when EOP data is required.
New classes have been added, e.g. StkComponentsCore, containing easily-accessible version information about the version of STK Components being used.
EntityParameter<TEntity> and TransactionParameter now have a DefaultValue property which allows the user to specify a default value for the parameter if one is not specified during evaluator parameterization.
Improved the performance of many evaluators in the libraries when derivatives are not required.
Added an overload of GregorianDateToIso8601String to specify the number of decimal digits to include after the decimal point in the 'seconds' field.
Unicode characters in the Space Separator category are now treated as valid white space characters within a TLE string when constructing a TwoLineElementSet.
Added Version property to StkEphemerisFile and StkAttitudeFile. Upon construction, the version defaults to v9.0. Upon reading an unrecognized version specification in a file, the version is set to Unknown.
The values of the AuxiliaryStateElements in the NumericalPropagatorCurrentState property are now updated on the creation and reset of the propagator. Previously, these values were out-of-date until Propagate was called.
Fixed a bug where an StkEphemerisFile containing CovarianceTimePosVel data and without the CovarianceFormat property explicitly specified would be incorrectly interpreted as UpperTriangular rather than LowerTriangular.
Fixed a bug where converting from UTC time to UT1 time very early, without first accessing other parts of the libraries, could throw an exception.
Fixed a bug in GregorianDateToString that could lead to rounding errors in the last decimal place in the formatted number of seconds.
Removed IInterpolator and PolynomialApproximation. These types were marked obsolete in a previous release in favor of InterpolationAlgorithm.
Removed the SigmaInterpolator and RotationInterpolator properties from Covariance3By3SizeAndOrientationInterpolator. These properties were marked obsolete in a previous release in favor of SigmaInterpolationAlgorithm and RotationInterpolationAlgorithm.
Removed the Interpolator property from DoubleMotionInterpolator, TranslationalMotionInterpolator, and RotationalMotionInterpolator. This property was marked obsolete in a previous release in favor of the InterpolationAlgorithm property.
Improved the performance of HermitePolynomialApproximation.
SensorVolumeConstraint now uses an improved algorithm for selecting the sampling step for conic sensor shapes, resulting in improved performance when evaluating the constraint over time.
GregorianDateToIso8601String now has an overload that takes an enumeration indicating how the string should be formatted.
Fixed a bug in ScalarAngleBetweenVectors where it did not use the same EvaluatorGroup for all pieces of its computation. This did not affect the results, but it caused poor performance in certain situations.
Fixed a bug when evaluating a MotionEvaluator<T> or MotionEvaluator<T, TDerivative> over an interval. In most cases, any exceptions occurring during evaluation would be wrapped in a ThreadException, but sometimes an exception would pass through without being wrapped. Now, all exceptions are wrapped.
PropagatedRoute.HasNoConfigurationErrors is obsolete. Please use HasConfigurationErrors instead.
Added Terrain Integrated Rough Earth Model (TIREM) v3.18 for accurate communication signal propagation along terrain. For more information, see the reference documentation for TiremPropagationModel3_18.
Added EllipsoidEllipsoidSeparationDistance to compute the separation distance between two ellipsoids.
Modified TerrainAvoidanceProfile so that having a large effective pitch rate will no longer cause the profile to exaggerate the height above the terrain. This includes alternative heuristics to avoid cases where noisy terrain can cause problems when trying to navigate over local peaks. TerrainAvoidanceProfile should now be more reliable and create reasonable routes in most cases, though configuration errors may still result from certain difficult geometries.
Improved the reliability of the StandardTransitionProfileSegment to prevent numerical noise from causing conflict between the boundary conditions between profiles. The height of the profile at the end of a long surface segment will now be more precise with respect to the requested boundary condition.
Added a constructor to Matrix3By3Symmetric that rounds the non-diagonal elements of a Matrix3By3. This provides a better way of constructing a symmetric matrix from a matrix which has become slightly non-symmetric due to numerical noise from the FromLowerTriangular and FromUpperTriangular methods.
Fixed a bug in GregorianDateToIso8601String that caused single-digit numbers of seconds to be formatted without a leading zero. In addition, ISO8601 dates are now formatted consistently regardless of the current culture.
RinexNavigationEphemerisAvailabilityIntervals is now computed from the time of transmission rather than from the time of ephemeris.
StkEphemerisFile no longer automatically converts distances to meters and angles to radians on load. However, the interpolator accessible via the Interpolator property still offers data in meters and radians for easier interfacing with other parts of STK Components.
When an exception occurs during function evaluation, TimeIntervalFinder now wraps the exception in a ThreadException even when it is operating in a single-threaded mode. This is consistent with the behavior in the rest of STK Components and allows user code to catch the same exception regardless of whether the operation ended up being multithreaded.
Orbit Propagation Library now supports propagation of a StateTransitionMatrix that can be used to compute state covariance, or the uncertainty in the state elements, over time. See the Covariance and Uncertainty topic for more information.
Added basic support for sensors that change shape with time. See the bottom of the Sensor Field of View Volumes topic for more information.
Added LagrangeOrbitVariationOfParameters to interpolate orbital positions using a two-body propagator and variation of parameters (VOP).
StkEphemerisFile now supports the "LagrangeVOP" interpolation method.
Added an EvaluationBehavior property to GpsRinexPropagator, allowing control of the behavior when evaluating outside the AvailabilityIntervals of the propagator. Also added a similar option to RinexNavigationCreateSatelliteCollection and RinexNavigationRecordCreateSatellite.
Added a new constructor overload to AzimuthElevationMaskConstraint to make it easier to construct an instance from a link and a link end.
CartesianStateElementConverter is no longer abstract so it can be constructed directly.
Fixed a bug in CustomSensorPattern that resulted in poor performance when using the sensor volume to compute access.
Fixed a bug in DescriptiveStatisticsPercentileT that would rarely cause it to index incorrectly into the supplied list and raise an exception.
Added new geocentric (or planetocentric) coordinate type, LongitudeLatitudeRadius.
Fixed a bug that could cause Access Queries, DoubleFunctionExplorer, DurationFunctionExplorer, and JulianDateFunctionExplorer to throw an ArithmeticException when given evaluation intervals smaller than the independent variable convergence tolerance or when an extremum was indicated over a similarly small interval.
Fixed a bug in UsgsDigitalElevationModel that caused it to interpret negative heights and voids incorrectly.
Fixed a bug where DiscreteCoverageDefinitionOnCentralBody could not be canceled by ITrackCalculationProgress.
Fixed a bug that could cause DiscreteCoverageDefinitionOnCentralBody to throw an IndexOutOfRangeException when the computation was aborted as a result of a different exception.
Fixed a bug that could lead to an access violation when loading Collada models with textures.
Removed the Principle and PrincipleAxis properties of AxesAlignedConstrained. They were marked obsolete in a previous release in favor of the correctly-spelled versions.
Classes derived from AccessEvaluator are now required to implement the EvaluateIgnoringAvailability method. This new method offers improved performance in cases where the underlying evaluators are already known to be available.
The EvaluatorGroup.CreateEvaluatorCallback delegate types have been renamed, for example, AGI.FoundationEvaluatorGroupCallback0TEvaluator.
The following types were moved from the AGI.Foundation.Geometry namespace to the AGI.Foundation.Communications namespace: LinkBudget, LinkBudgetScalars, AntennaTargetingResult, AntennaTargetingResultReason, and AntennaTargetingResultCollection.
PointInterpolatorType is now obsolete. Please use InterpolationAlgorithmType instead.
The Explore method on DoubleFunctionExplorer, DurationFunctionExplorer, and JulianDateFunctionExplorer now automatically calls Reset. As a result, events will no longer be raised for crossings and extrema occurring between the intervals in two successive calls to Explore.
Added DiscreteCoverageDefinitionOnCentralBody, an alternative to CoverageDefinitionOnCentralBody that may be faster and more flexible in some situations. See the Coverage topic for more information.
Added IPlaceHolderService, which serves as a marker for extensible objects that act as placeholders rather than fully-functional objects. In some circumstances, placeholders may be subject to less verification than regular objects so that they are not required to provide all of their eventual services until evaluator creation time.
AGI Components has been renamed to STK Components!
Improved terrain performance by about 10% in many important use-cases.
Improved performance for common cases involving Communications Library propagation models and antenna patterns.
Improved performance of repeated calls to GeometryTransformerObservePoint with different points but where each point is defined in the same reference frame.
Fixed a bug in StkEphemerisFile that caused distances to be read incorrectly when the file specified the DistanceUnit property.
Fixed a bug preventing CommunicationSystem from being used with CoverageDefinitionOnCentralBody.
Fixed a bug in TranslationalMotionInterpolator that caused it to arbitrarily return either of the two values when evaluated exactly on a segment boundary time. Now, it always returns the second value.
Fixed a bug in various caching evaluators that could cause them to return incorrect results when the underlying evaluator threw an exception and then the cache was evaluated again at the same time.
Fixed a bug where CoverageDefinitionOnCentralBody would report incorrect access results for assets defined to include an AccessQueryOr.
Added the recently-announced June 30, 2012 leap second to the default list of leap seconds.
Signal now throws an exception if constructed with zero bandwidth or a negative frequency.
SensorFieldOfView.GetProjections is now obsolete. Please use SensorFieldOfViewGetProjection instead.
IInterpolator and PolynomialApproximation are now obsolete. Use the new abstract base class InterpolationAlgorithm instead.
Properties named Interpolator on TranslationalMotionInterpolator, RotationalMotionInterpolator, DoubleMotionInterpolator, and Covariance3By3SizeAndOrientationInterpolator are all now obsolete, and are replaced by properties named InterpolationAlgorithm. This makes a clear distinction between the interpolation algorithm classes and the interpolator classes that use them.
Interpolation methods on LinearApproximation, HermitePolynomialApproximation, and LagrangePolynomialApproximation taking IList<double> parameters are now obsolete. They are replaced by better-performing versions that take double parameters.
All of the sensor types, including RectangularPyramid, ComplexConic, SyntheticApertureRadarVolume, and CustomSensorPattern, can now compute their complete projection into space as well as onto the ellipsoid.
Sensors visualized with FieldOfViewCentralBodyProjectionGraphicsExtension now display the projection of the sensor into space in addition to displaying the projection onto the ellipsoid.
Added the EllipsoidSurfaceRegion.CreateRegionUsingExtent method to make it easy to create a coverage grid from a latitude / longitude extent.
Interpolation using TranslationalMotionInterpolator, RotationalMotionInterpolator, DoubleMotionInterpolator, and Covariance3By3SizeAndOrientationInterpolator is now faster, due to the interpolation algorithm changes mentioned in the "Breaking Changes" section above.
Improved the numerical stability of computing sensor projections.
Fixed a bug in EllipsoidTangents that caused it to always report that there were no tangents when the specified half angle was greater than 90 degrees.
TextBatchPrimitive now works correctly when one or more of the strings is an empty string.
Classes deriving from GainPattern are now required to override the Clone method.
Overloads of NumericalPropagatorPropagate taking an outputInterval have been removed. Instead, an outputSparsity parameter is provided to reduce the output produced by the propagator.
CommunicationLinkCollection now has a DefaultAccessConstraints property. The constraints are applied to all links in the collection so that they are unavailable when, for example, the transmitter and receiver are on opposite sides of the Earth.
Added a new type of IntendedSignalStrategy, IntendedSignalByTransmitter, that makes it easy to specify that the intended signal in a CommunicationSystem is the one transmitted by a particular transmitter.
CentralBodyObstructionConstraint no longer requires either end of the link to have an orientation. In addition, it is a bit faster in many cases.
GainPattern now implements ICloneWithContext.
AGI Components for .NET is now tested against Mono v2.10.5.
StkEphemerisFile now reads the InterpolationSamplesM1 property written by recent versions of STK. Previously, it ignored the property, which could result in incorrect interpolation.
References to a single instance of a NumericalPropagator held by multiple objects will now get updated properly when those objects are cloned.
Fixed a bug where specifying values near zero for the minimum threshold of a CommunicationObjectConstraint would cause the constraint to incorrectly report that access is not available.
Fixed a bug in BrentFindExtremum that could cause it to produce NaNs and attempt to evaluate the function at invalid independent variable values when a function evaluated to positive or negative infinity.
Attempting to stop the cache thread for a TerrainCacheGroup that was already stopped now throws an exception instead of hanging.
Fixed a bug that could rarely cause an exception to be thrown when setting valid ModelPrimitive articulation values.
ThreadingPolicyFacet, NumberOfProcessorsThreadingPolicyFacet, and ConstantThreadingPolicyFacet are now obsolete. Please use ThreadingPolicy instead.
Removed constructor overloads for BingMapsForEnterpriseImageGlobeOverlay taking an account ID and password, because the account ID and password are no longer required. These constructors were previously marked obsolete.
Added higher-level types to make it much easier to do analysis with the Communications Library. See the Basic Communications topic more information.
IersTechnicalNote21 now exposes Updated1980NutationModel and UpdatedEquationOfEquinoxes, and EarthCentralBody is configured to use these models by default. The old models are still available from ClassicalEquationOfEquinoxes and Iau1980Nutation, and can be selected by setting the EquationOfEquinoxes and NutationModel properties on EarthCentralBody.
Added IntendedSignalByIdentifier<T> to select an intended communications signal by specifying its identifier.
Added new GraphicsParameter<T> types for use with ServiceProviderDisplay, including AxesGraphicsParameter, PointGraphicsParameter, ScalarGraphicsParameter, and VectorGraphicsParameter. Also added GraphicsParameterFormatter and GraphicsParameterTransform<TInput, TOutput> to make it easy to generate dynamic labels by combining several parameters together.
Improved the numerical stability of the QuarticRealPolynomialRealRoots method.
JplDE now uses the equation of the equinoxes to model the longitude of the mean ascending node of the moon for nutation. Previously, it was always 0.0.
Sgp4Propagator now returns an approximate acceleration which is the same as the acceleration produced by the J4Propagator. Since the SGP4 theory itself is an approximation, and even its position and velocity do not correspond exactly, the fact that the acceleration is not exact is deemed an appropriate approximation. Having acceleration available from the propagator is extremely useful throughout other parts of the system.
AGI Components now consistently honors the ThreadingPolicyThreadSource property when executing parallelizable operations in multiple threads.
Fixed a bug in EllipsoidSurfaceCurve that could cause EllipsoidGridRegions to produce grid points far outside the desired region.
Fixed a bug that prevented markers in KML documents in Insight3D from working with the newest NVidia GPU drivers and when running on certain other GPUs.
The InitialVelocityResiduals and FinalVelocityResiduals properties of Sgp4PropagatorSgp4EstimationOutput have been marked obsolete. The values were never computed or used as part of the estimation process.
CentralBody is no longer settable via the service interface, making it consistent with other service interfaces.
Matrix3By3.EigenDecompositionOfSymmetricMatrix is now obsolete. Use Matrix3By3SymmetricEigenDecomposition instead.
StkEphemerisFile now stores covariance information using the more efficient Matrix3By3Symmetric instead of Matrix3By3 in order to reduce memory requirements when dealing with large amounts of covariance information.
Added DoubleMotionInterpolator to interpolate over collections of double-precision, floating-point numbers using various interpolation algorithms.
In Matrix3By3, the associated reordering of the eigenvectors to produce the proper sorting of the eigenvalues in the eigen decomposition of a symmetric matrix is now performed in such a manner as to preserve the "right-handedness" and rotational characteristic of the underlying Schur decomposition.
Improved performance and reduced memory requirements when writing an StkEphemerisFile that contains covariance information.
Due to a new license agreement between AGI and Microsoft, BingMapsForEnterpriseImageGlobeOverlay no longer shows an evaluation banner when not using a licensed account. All Insight3D applications can now use imagery from the Microsoft Bing Maps public servers free of charge.
TwoLineElementSetToTleString now throws an exception when the values of the properties cannot be represented as a TLE string. Previously, it would generate an invalid TLE.
Starting in AGI Components 2011 r4, EndianBitConverter would throw different exceptions depending on whether the desired endianness matched the system. This regression has been fixed, and the exceptions thrown by EndianBitConverter once again match those thrown by the standard bit converter.
Fixed an issue with Sgp4PropagatorEstimateElements which would cause a matrix to become singular for some orbits.
Fixed a bug in UsgsDigitalElevationModel where numbers expressed in Fortran scientific notation were not parsed correctly, leading to a FormatException.
A large number of types and members have been removed in this release. These items were all marked obsolete in previous releases. Please contact AGI support if you have difficulty adjusting your code to work with this release.
SunCentralBody.MeanSolarRadius is now obsolete. Use MeanSolarRadius1992Seidelmann, MeanSolarRadius1993Prussing, or MeanSolarRadius2007Carroll instead. The 2007 value is now used for the Shape of the SunCentralBody by default.
Introducing the Orbit Propagation Library, which provides a specialized state variable and several force and environment models that can be used to propagate a satellite. For more information, see the Orbit Propagation topic.
Added new static method CollectionAlgorithmsCreateJaggedDoubleArray.
Added new method JulianDateDaysDifference.
Added a MinimumSampleSpacing property to TerrainProvider. This property provides a good estimate of the resolution of the terrain data and is used in TerrainAlongLine to select how the terrain is sampled.
MarkerBatchPrimitive now supports aligning markers with the north vector, using the AlignToNorth method, or with an arbitrary axis, using the AlignToAxis method, in addition to the previous capability of aligning with the screen, using the AlignToScreen method.
TriangleMeshPrimitive can now display a texture. It has new properties for specifying the Texture and TextureFilter, and can specify the per-vertex texture coordinates using the new SetTextureCoordinates method.
Fixed a bug where the ScalarDotProductCheckForSameDefinition method mistakenly returned true when comparing scalars representing "vectorA 'dot' vectorB" and "vectorB 'dot' vectorA". While the values are likely to be the same, the definitions should be considered different.
Fixed a bug in SqlServerArchive<TEntity> that could cause problems when archiving data spanning multiple days.
Fixed a bug in Insight3D that caused it to crash at startup when run on a Linux system under WINE. Insight3D is still not officially supported on non-Windows platforms.
Fixed a bug in Insight3D that could cause textures on MDL models to disappear under some circumstances.
VectorDotProduct is now obsolete. Use ScalarDotProduct instead.
Parameter evaluators now throw an exception if they are evaluated without first being parameterized. Previously, they returned a default value.
TrackingTypeArchiverCollection.AddPrimitive has been removed. A new AddEnumerationT method is provided to register an enumeration type for default archiving. Any other type should use the Add method and pass a custom archiver class.
Constructors for BingMapsForEnterpriseImageGlobeOverlay that take an account ID and password are now obsolete because Microsoft is discontinuing support for Token Service authentication on March 30, 2012. Instead, use the new constructors that take an application ID and utilize the Key Service.
Added new scalar and vector types: VectorSum, ScalarSum, ScalarDotProduct, ScalarProduct, and ScalarExponent. New operator overloads were added to Scalar and Vector to facilitate the use of these new types.
Added two new access constraints, AngleInPlaneConstraint and AngleOutOfPlaneConstraint. These constraints are similar to AzimuthAngleConstraint and ElevationAngleConstraint, respectively, but allow more flexibility in how the angles are defined.
PointInterpolator now supports a PointInterpolatorType of Linear in addition to Hermite and Lagrange.
Fixed a bug where parameters in a parameterized evaluator sometimes returned false from their IsTimeVarying property, leading to improper caching of their value.
Fixed a bug where TerrainAlongLine would report an obscured view if the one of the points was very slightly below the terrain surface. It is common to end up placing objects very slightly below terrain when attempting to put them on terrain, due to floating point rounding.
Fixed a bug in PointVectorToPoint that caused an exception when comparing it to another point of a different type.
Fixed several memory leaks in Insight3D.
Fixed an exception that could occur in WebMapServiceCachedImageGlobeOverlay.
When RasterTerrainProviderCartographicExtentToIndexExtent is passed a Cartographic extent outside of the valid range of the terrain provider, it now clamps the returned index extent rather than throwing an exception.
Added support for Stereoscopic rendering.
Added a TerrainAzimuthElevationMaskCreateDelayedMask method which creates a delayed azimuth-elevation mask in which individual azimuths of the mask are not computed until they are needed. In most cases, using this method instead of the Compute method will improve performance by eliminating unnecessary computations.
Added overloads of StkEphemerisFileReadFrom that allow additional read options to be specified, such as whether or not to read covariance data.
Beginning with this release, AGI Components for .NET is distributed as a simple ZIP file instead of as an installer. We hope that you will find this more convenient, but we appreciate your feedback.
Improved the performance of AGIProcessedDataTerrain.
Improved the performance of AGIWorldTerrain.
ThreadedCalculation now installs a ConstantThreadingPolicyFacet specifying one thread in each thread that is used to do the computation. This ensures that parallelizable computations invoked within the thread are not themselves parallelized. As a result, the number of threads is closer to the number of cores in common use-cases, which improves performance by reducing context switch overhead. For example, when splitting a large coverage grid among multiple threads, the individual access computations that are performed for each grid point will not themselves be multithreaded.
Fixed a bug that could lead to an exception when PerItemPickingEnabled was set to true on a primitive with an empty collection of batch items.
Fixed a bug that could cause some tiles of irregular, high-resolution PDTT files to not be rendered.
Fixed a bug that caused textures on MDL models to disappear when rendered in the same view as a TextBatchPrimitive.
Fixed a bug that prevented evaluation of AGIWorldTerrain heights very close to -180 degrees longitude or 90 degrees latitude.
Fixed a bug that caused AGIProcessedDataTerrain to incorrectly return heights of 0.0 for some regions of irregular, high-resolution terrain.
Fixed a bug that could lead to an access violation when using imagery overlays in Insight3D. This bug was introduced in AGI Components 2011 r2.
DoubleFunctionThreshold, DurationFunctionThreshold, JulianDateFunctionThreshold, DoubleFunctionExtrema, DurationFunctionExtrema, and JulianDateFunctionExtrema are now obsolete. Use DoubleFunctionExplorer, DurationFunctionExplorer, or JulianDateFunctionExplorer instead.
The misnamed DelaunayElements.MeanMotion property is now obsolete. The MeanAnomaly property should be used instead.
Added support for the ColladaFX framework for Collada models rendered with ModelPrimitive. ColladaFX allows for fine-grained control over the rendering of the model in order to create sophisticated visual effects. See the Advanced Shading section of the Model Primitive topic for more information.
Added DoubleFunctionExplorer, DurationFunctionExplorer, and JulianDateFunctionExplorer to numerically explore functions looking for threshold crossings, minima, and maxima. See the Exploring Functions topic for more information.
Insight3D terrain and imagery now use per-pixel lighting on supported hardware, which improves visual quality.
Fixed a bug in the Insight3D Balloons that could cause sizing issues when given certain content.
Fixed issues with orbital element support for non-closed orbits which would cause some conversions and operations to throw exceptions or produce incorrect results.
Fixed a bug in DoubleFunctionExtrema, DurationFunctionExtrema, and JulianDateFunctionExtrema that could lead to an exception when evaluating over an extremely short interval.
Fixed a bug in DoubleFunctionExtrema that could cause it to report incorrect extrema.
Fixed a bug in DoubleFunctionThreshold that could cause it to report incorrect threshold crossings.
Fixed a bug in CoverageGridResult where the boundary vertices, if set beforehand, would become null after calling ApplyFilter.
Fixed a bug that incorrectly caused multiple items to be picked on older video cards or over Remote Desktop when TextBatchPrimitivePerItemPickingEnabled was set.
Fixed rendering problems with PathPrimitive on older (OpenGL 1.1) graphics cards.
Fixed a bug where KML network links would fail to refresh in certain configurations.
Fixed a bug in KmlNetworkLink that could lead to an exception when using query strings to request data.
Fixed a bug that could lead to an exception when visualizing a link using ServiceProviderDisplay.
KmlDocumentLoadedEventArgsException is no longer settable.
Added PrimitiveFactory to simplify creating primitives for common use cases such as polygons, circles, and latitude-longitude grids.
Added NetworkContext to configure additional network settings for acquiring resources from URIs in Insight3D. For instance, you can now set a proxy, set credentials, or configure certificate policies that can enable SSL connections.
Improved accuracy when calculating Earth Rotation Angle, particularly at times far removed from J2000.
Improvements to ProjectedRasterOverlay. See the Raster and Projection Streams topic for more information. Improvements include:
Projection onto models.
Visualization of the far plane.
Colors and translucency of various aspects of the visualization can now be customized.
Support for Rasters with alpha channels.
Access to the direction vectors that define the projection's frustum.
Visual properties can now be set dynamically while visualization is occurring.
Other fixes and performance enhancements.
Fixed a crash in Platform Graphics when mixing null and non-null GraphicsParameter<T> objects of the same type.
Fixed a bug causing the GlobeImageOverlayAddCompleteEventArgs object provided to any registered handlers for the ImageCollectionAddComplete event to always report failure when adding a GeospatialImageGlobeOverlay, even if the add succeeded.
Added StationaryHoldProcedure to Route Design Library. It allows users to define a waypoint at which the vehicle will slow to a stop, hold for a specified amount of time, and then speed up to continue toward the next procedure.
Fixed an issue with AxesFromBankAngle that could cause a discontinuity when several tight turns were performed close together.
Fixed a bug in EvaluatorGroup that could cause top-level evaluators to not be cached even when retrieved multiple times.
Fixed an issue with StandardTransitionProfile where the profile was not using the user's SpeedReference in all cases. Also, in the event that the profile attempts a near-vertical path, the profile will now try to reconfigure the path to create a more flat profile to avoid an error where there is a discontinuity in speed in the middle of the profile.
Fixed a bug that could cause ModelPrimitives using some MDL models to be lit incorrectly.
Fixed a bug that caused ModelVisualizer to try to evaluate an object at the wrong time, leading to an exception.
Fixed a problem that could cause ground overlays loaded from a KML document to be rotated incorrectly.
AccessQueryOptions is now obsolete. Please specify the time observer directly rather than wrapping it in AccessQueryOptions.
Ellipsoid.SurfacePoint is now obsolete. Please use SurfacePosition instead.
TerrainProvider.Cache has been removed. It was previously marked obsolete.
The SetPositionRadius, SetPositionAzimuthElevation, TryCartographicToWindowCoordinate, CartographicToWindowCoordinate, TryWindowCoordinateToCartographic, WindowCoordinateToCartographic, ViewExtent (obsolete overloads only), and ViewSphere methods of Camera were removed. They were previously marked obsolete.
The ViewEntityFromOffset<TEntity>Shape property and constructor taking an ellipsoid were removed. They were previously marked obsolete.
Added StartInThreadPoolThread and StartInNewThread methods to start a MessageQueue with explicit control over what type of thread to use. StartInNewThread optionally allows you to specify the name of the thread. The existing StartInAnotherThread method uses either a thread pool thread or a newly created thread depending on the state of a new property: ThreadingPolicyFacet.UseThreadPool, which is true by default to maintain the previous behavior.
Improved the algorithm used by BrentFindRoot to converge more quickly in most cases and to more closely match Brent's published algorithm.
TimeGenerator now generates time in the nearest arithmetic-safe time standard (such as TAI) when given times in a non-safe standard (such as UTC).
Fixed a bug in BrentFindRoot that could cause it to think it converged on the independent variable tolerance before it really had.
Removed usages of methods in the .NET Framework that were not available in older (pre-service pack) versions of .NET 2.0 and .NET 3.5.
Fixed a bug that led to an access violation when setting the SceneManagerAnimation property to the same value it already held.
Fixed a memory leak when accessing the CameraPosition property. This bug fix also substantially improves the performance of this property.
Accessing a KmlNetworkLink when that network link is unavailable now throws an appropriate exception instead of causing an access violation.
Fixed an access violation that could occur when loading a KML document containing assets accessed via SSL (HTTPS).
ModelVisualizer<TEntity> now supports multiple models for a single entity.
Fixed an issue that could cause KML to render improperly with terrain.
The "tessellation" property of a polygon in a KML document is now correctly ignored when the polygon's altitude mode is "clampToGround."
The StkEphemerisFile class now only provides a valid interpolator for ephemeris files with Lagrange and Hermite interpolation methods. For GreatArc and other methods, users must construct an interpolator manually. Previous versions returned a partially-constructed but unusable interpolator for unsupported interpolation methods.
IsTimeVarying is now abstract on evaluator classes. If you are implementing your own evaluators, you will need to override this property.
Added a new class, CentralBodyInertialAxes, which represents an inertial axes for a central body that is consistent with STK Desktop's default central body inertial axes.
TerrainAlongLineComputeTerrainIntersection now only returns the starting point if it lies exactly on the terrain surface and the direction of interest is toward the surface.
Messages can now be posted to a MessageQueue even after it has been terminated. The messages will be processed if and when the queue is restarted.
Improved BrentFindExtremum performance by using Golden section instead of bisection when one end of the bracketing interval remains stationary over two iterations.
Insight3D now renders at a target rate of 60 frames per second by default. Previously it would render as fast as possible, causing unnecessary CPU usage. The previous behavior can be restored by setting the RefreshRate property on the SceneManagerAnimation object.
Fixed a crash that could occur when creating a ModelPrimitive and specifying a model filename that does not include an absolute or relative path.
SurfaceMeshPrimitive now correctly renders polygons with a hole.
Fixed a crash that could occur when working with streaming Rasters.
Fixed a bug that could result in excessive memory usage when animating but not interacting with the Insight3D window.
Fixed outlined PolylinePrimitive rendering artifacts that occurred for overlapping polylines that wrapped around the globe.
Fixed a bug where outlined PolylinePrimitives could not be picked.
Fixed a bug where the wrong item in a MarkerBatchPrimitive could be reported as picked.
Fixed an issue where SurfaceMeshPrimitiveSupported could incorrectly return false even when it was supported by the video card. This was most common with Intel video chipsets.
All evaluators now correctly implement IsTimeVarying when they do not vary with time. Previously, many evaluators simply returned true, which did not cause incorrect results but could negatively impact performance in certain cases.
Fixed an issue in HeightTransitionProcedure that would cause a discontinuity for some cases when exiting a left-handed spiral.
Fixed an issue where the speed reported by the StandardTransitionProfile segment was zero when extrapolating before the "Start" or after the "Stop" times of the route. This fixes an issue where AxesFromBankAngle threw an exception when evaluated slightly before the start or slightly after the stop times.
Fixed an issue in TimeIntervalFinder that would cause LocalMaximum or LocalMinimum events at the function threshold or within the tolerance of the function threshold to incorrectly start or end an interval.
Fixed an issue where AccessQuery evaluation at a single date could return inconsistent results if an interval of consideration had been previously analyzed.
Fixed an issue in TerrainAlongLineComputeElevationAngleAboveTerrain where the incorrect end point could be used for part of the computation.
The AccessSampling type has been renamed to JulianDateFunctionSampling.
Added the DurationFunctionThreshold type to find threshold crossings of functions where the independent variable is of type Duration.
Added the DoubleFunctionExtrema, JulianDateFunctionExtrema, DurationFunctionExtrema types to find function minima and maxima.
Fixed a bug where a control called AgGxBalloonBrowserControl was being added to the Visual Studio toolbox when adding AGI.Foundation.Graphics.dll from the Choose Items... dialog.
Fixed a bug where CentralBodySurfaceRegionVisualizer would cause an exception if the CentralBodySurfaceRegionGraphicsExtensionBoundaryGraphics property was null.
GlobeImageOverlayAddCompleteEventArgs and TerrainOverlayAddCompleteEventArgs now correctly provide exception information to completion event handlers when terrain or imagery are added asynchronously. In AGI Components 2010 r6 (but not prior versions) this information was lost.
ProjectedRasterOverlay.Translucency now throws NotSupportedException instead of silently ignoring the provided value, restoring the behavior that existed prior to AGI Components 2010 r6.
In AGI Components 2010 r6, the SceneManager.Animation.Time property was initialized to TimeConstantsJ2000 instead of SceneManagerTime as it was in previous releases. This caused the time to quickly jump from the scene manager's time to the animation controller's time at the start of animation if SceneManager.Animation.Time was not set explicitly.
Fixed a bug where setting the SceneManager.Animation.StartTime property and then rendering, without explicitly setting SceneManagerTime, would cause the scene to be rendered at a different time than that reported by the SceneManagerTime property.
Two assemblies that were previously unsigned, AGI.Foundation.Platform.Graphics.dll and AGI.Foundation.Tracking.Graphics.dll, now have strong names.
Fixed a bug in Insight3D's terrain and imagery loading that could lead to access violations or hangs in certain situations.
RealTimeSimulationAnimation no longer has a TimeOffset property. Also, the amount of time stepped by StepForward and StepBackward is now controlled by the TimeStep property instead of by the amount of real time that has passed since the last step.
AreaTarget, AreaTargetElevationAngleConstraint, LineTarget, LineTargetElevationAngleConstraint, and related types have been marked obsolete. Instead, use CentralBodySurfaceRegion, CentralBodySurfaceRegionElevationAngleConstraint, CentralBodySurfaceCurve, and CentralBodySurfaceCurveElevationAngleConstraint.
Insight3D can now load and display KML documents and provide basic access to the underlying document object model (DOM). See the KML topic for more information.
Insight3D can now display rich HTML balloons attached to positions in a scene. See the Balloons topic for more information.
A new library, Platform Graphics, has been added that makes it easy and flexible to visualize Platforms, links, and other IServiceProviders, as well as the results of analyzing these objects, in Insight3D. For more information, see the Visualizing Platforms topic.
Added a Matrix6By6 type.
StkEphemerisFile can now read covariance data from an ephemeris file and interpolate over the data.
Fixed a memory leak in SurfaceShapes.
RealTimeSimulationAnimation now behaves more consistently when switching between animating forward and animating backward. It also now works correctly when set to loop at either end.
Removed RaimComputation, CreateFromArray, IIndexableImmutable, CrossPlatform, IOrdinalArithmetic, FunctionThreshold, and IPropagateFromInitialConditions. They were previously marked obsolete.
Removed the Prn and PrnCharacter properties from RinexObservationSatRecord. They were previously marked obsolete.
Removed Jpeg2000ImageGlobeOverlay. It was previously marked obsolete.
The Camera methods Camera.TryWindowCoordinateToCartographic, Camera.WindowCoordinateToCartographic, Camera.TryCartographicToWindowCoordinate, and Camera.CartographicToWindowCoordinate are now obsolete. Please instead use WindowToCartographic, TryWindowToCartographic, CartographicToWindow, and TryCartographicToWindow, respectively.
Introducing the Route Design Library, which provides simple ways to represent and analyze routes for vehicles, such as aircraft, ground vehicles, and ships, operating near the surface of the Earth or other central body. For more information on the Route Design Library, see the Route Design topic.
Added the ability to obtain the gradient, hessian, and surface normals at a point in a TerrainProvider, by calling the GetGradient, GetHessian, and GetNormal methods. The gradient can be used to compute a directional derivative of height along the surface. First and second partial derivatives are also now available, by calling the GetFirstPartials and GetSecondPartials methods.
Added PreloadExtent and UnloadExtent methods to TerrainProvider. PreloadExtent is used to load the terrain data for a specified region into the terrain cache. UnloadExtent unloads preloaded data from the cache. See the Terrain topic for more information.
Added the ability to stream Microsoft Bing Maps for Enterprise (previously Microsoft Virtual Earth) imagery using the BingMapsForEnterpriseImageGlobeOverlay class.
A web proxy can now be specified when constructing an OpenStreetMapImageGlobeOverlay.
Insight3D globe overlay (terrain and imagery) rendering performance has been significantly improved.
VideoStream now uses an asynchronous connection for RTP streaming in addition to UDP and TCP streaming.
TextBatchPrimitiveSet performance has been substantially improved.
Improved mouse handling when MouseOptionsAnimateWhileHandling is enabled, and the frame rate is low.
Fixed a bug that resulted in an access violation when a large number of triangles were used with SurfaceMeshPrimitive.
Fixed a bug that caused the Camera to temporarily have an incorrect axes after a zoom.
Setting the CameraAxes property no longer causes the view to change.
ViewExtent now works correctly when the extent crosses the international date line.
Camera.SetPositionRadius and Camera.ViewSphere are now obsolete. Use CameraViewOffset instead.
Camera.SetPositionAzimuthElevation and Camera.ViewExtent methods taking AzimuthElevationRange are now obsolete.
Removed PointBatchPrimitive.SupportsDistanceDisplayConditionPerPoint. It was previously marked obsolete.
The ViewEntityFromOffset.Shape property, and the related constructor, has been made obsolete. Use the CentralBody property instead.
LinearApproximation now throws an exception when given the same value for x0 and x1. Previously, it would return the average of y0 and y1.
HistoryVisualizer<TEntity>, LabelVisualizer<TEntity>, MarkerVisualizer<TEntity>, PointVisualizer<TEntity>, and WaypointVisualizer<TEntity> can now be constructed with a SetHint value which is given to any Insight3D primitives created by the visualizer.
MarkerBatchPrimitive, PointBatchPrimitive, PolylinePrimitive, and TriangleMeshPrimitive now allow an empty collection of positions to be passed to their Set methods and an empty collection of indices to be passed to their SetPartial methods.
RecurringTaskSchedulerRemoveTask now returns the final set of performance metrics for the removed task.
Tracking Library now provides default archivers for all AGI Components relevant value types and enumerations.
Implemented an improved algorithm in CubicRealPolynomial with better numerical properties.
LagrangePolynomialApproximation now uses additional derivatives in the input data, if available. Previously, only the input coordinate values were used to compute the Lagrange polynomial. Higher-order output, if requested, was computed from that polynomial. Now, the Lagrange polynomial for a given output order is computed from the input data with the highest-order less than or equal to the output order. For example, if both position and velocity information are provided as source data for interpolation but position, velocity, and acceleration are requested as output, the position and velocity information are interpolated independently and the derivatives of the velocity interpolating polynomials are used to compute the acceleration.
LinearApproximation now linearly interpolates across all given orders of input. If higher order outputs are requested, the output order one higher than the highest input order is the constant slope for that segment, and any higher outputs are zero. Previously, input derivatives were ignored, the first derivative on output was constant, and higher derivatives were zero.
InterpolationAlgorithm now has an additional method, GetRequiredDataPoints, which takes a degree and an input order and returns the number of independent variables that must be interpolated over in order to attain the specified degree of polynomial approximation.
EulerSequence and YawPitchRoll now check to ensure the EulerSequenceIndicator or YawPitchRollIndicator that is returned from each type's Sequence property is valid. Previously, it was possible to create invalid instances in .NET, but not Java. The two versions now behave consistently.
Insight3D now properly orients Collada models. If you added code to correct for the incorrect orientation, you will need to remove it when you upgrade to this release.
LagrangePolynomialApproximation can now compute any requested output order. In previous releases, interpolated values only up to the second derivative could be computed.
HermitePolynomialApproximation can now use any number of input derivatives (including zero), and return any number of output derivatives.
Fixed a bug in HermitePolynomialApproximation that caused it to interpolate with a much higher degree than specified when used with large data sets, resulting in extremely slow performance.
Fixed a bug in LinearApproximation that caused it to throw an exception when the requested output order was larger than the input order. Now it returns the slope of the line for the output order one higher than the input order and zero for any additional output orders.
Fixed a bug where MarkerBatchPrimitiveSupported would incorrectly return false.
Fixed a bug in SceneManagerRefreshEvaluators where it would not refresh the evaluator associated with the ReferenceFrame of a Primitive. Changes to the ReferenceFrame would not take effect even after calling SceneManagerRefreshEvaluators.
Removed the CentralBody property on Primitive, which was previously marked obsolete.
Removed the SetCartographic and SetPartial overloads on Primitive that did not take a central body. They were previously marked obsolete.
Removed the PositionCartographic property from ModelPrimitive, which was previously marked obsolete.
Removed the SetSubsetCartographic overloads on PolylinePrimitive that did not take a central body. They were previously marked obsolete.
MarkerBatchPrimitive.Supported is now obsolete because MarkerBatchPrimitive is now supported on all video cards.
TextBatchPrimitive.Supported is now obsolete because TextBatchPrimitive is now supported on all video cards.
NgaDigitalTerrainElevationData must now be constructed with a FileStreamFactory instead of a more general StreamFactory. Previously, using a StreamFactory was allowed but would throw an exception at runtime if the factory did not produce a FileStream.
TerrainProvider.Cache is now obsolete. Not all terrain providers use a cache.
Introducing Tracking Library, which seamlessly integrates the processing, visualization, and analysis of dynamically acquired data in AGI Components. See the Tracking topic for more information.
MarkerBatchPrimitive now works correctly even on older video cards.
TextBatchPrimitive now works correctly even on older video cards.
Added new overloads for ExtrudedPolylineTriangulatorCompute and ExtrudedPolylineTriangulatorComputeCartographic that take two collections of positions, one specifying the top positions and the other specifying the bottom.
Added the EllipsoidApparentAngularSize method.
Fixed a bug that caused the colors to be inverted when an ECW image was used as a globe overlay.
Terrain readers now work reliably with streams that have Read methods that can return fewer bytes than requested.
Fixed a bug that caused GraphicsFont to incorrectly undersize fonts by about 25%.
RaimComputation and related types are now obsolete. Use ReceiverAutonomousIntegrityMonitoring instead.
AccessSampling no longer implements IFunctionSamplingStrategy<JulianDate>. Instead, it has a method, AccessSampling.CreateFunctionSamplingStrategy, that returns an instance of IFunctionSamplingStrategy<JulianDate>.
RinexObservationSatRecord.Prn and RinexObservationSatRecord.PrnCharacter are now obsolete. Use RinexObservationSatRecordPseudoRandomNumber and RinexObservationSatRecordPseudoRandomNumberCharacter instead.
SatelliteIdentifier is now immutable, meaning that it cannot be changed after it is created.
Removed the incorrectly named EvaluatorGroup.CreateEvaluatorCallback3, which was previously marked obsolete. Use Callback4 instead.
Removed Solid.GetEnclosures, which was previously marked obsolete. Use SolidGetEnclosureDescriptions instead.
Removed CrossPlatform.ParseDateTime, which was previously marked obsolete. Use GregorianDateParse instead.
The CrossPlatform class is now obsolete. Its one method, IsMonoRuntime does not need to be included in AGI Components. To detect whether an application is running under Mono, see the "How can I detect if am running in Mono?" question in the Mono Technical FAQ.
Removed the AxesVehicleVelocityLocalHorizontal.CentralBody property and the related constructor, which were previously marked obsolete. Use the AxesVehicleVelocityLocalHorizontalReferenceFrame property instead.
Removed the constructor for GpsReceiver taking a GpsReceiverSolutionType, which was previously marked obsolete. Instead, construct it with one of the other constructors and set the ReceiverSolutionType property.
Insight3D now has the ability to render solids such as boxes and ellipsoids. See the Solid Primitive topic for more information.
YearMonthDay can now be constructed from a year and a day-of-the-year.
Added EndianBitConverter to enable conversion between values in fixed byte order formats.
Numerous improvements to the examples and documentation.
The performance of SensorVolumeConstraint has been improved.
ReceiverAutonomousIntegrityMonitoring replaces RaimComputation. The new class offers better performance and an easier-to-use interface.
Improved numerical results for finding roots of a QuadraticRealPolynomial when the linear term is zero and the constant term is small in relation to the quadratic term.
GridTimeSampledValues.ComputeData now creates grid points and figure of merit scalars in multiple threads simultaneously according to the ThreadingPolicyFacet.
AccessSampling now ensures that access constraint functions are sampled at least three times over each interval. Previously, small intervals might be sampled only twice and access events could be missed.
Fixed a bug in DoubleFunctionThreshold and JulianDateFunctionThreshold that could cause them to throw an exception claiming that the "threshold crossings of the function are not consistent" when two crossings of the threshold are close together.
Fixed a bug that could cause TriangleMeshPrimitive to flicker under certain circumstances.
Fixed a bug that caused AccessSampling to ignore the AccessSampling.TrendingStep property if it was smaller than the AccessSampling.MinimumStep.
Jpeg2000ImageGlobeOverlay is now obsolete. Use GeospatialImageGlobeOverlay instead.
Setting MarkerBatchPrimitiveSize now throws InvalidOperationException if the marker batch was not constructed with MarkerBatchSizeSource.UserDefined. Similarly, MarkerBatchPrimitiveSet and MarkerBatchPrimitiveSetCartographic now throw ArgumentException if per-marker sizes are provided and the marker batch was not constructed with MarkerBatchSizeSource.UserDefined.
EvaluatorGroupCreateEvaluator now throws an ArgumentTypeInvalidException if any of the given parameters implement IEvaluator. Previously, this was allowed but could result in poor evaluator performance. Instead, definitional objects should be passed to EvaluatorGroupCreateEvaluator and the evaluators should be obtained inside the callback method.
ECW files, ECW files streamed from a server through the ECWP protocol, and MrSID files can now be used as Globe Overlays via the GeospatialImageGlobeOverlay class. They can also be added by filename to an ImageCollection.
SurfaceMeshPrimitive can now do trapezoidal texture mapping by setting the SurfaceMeshPrimitiveTextureMatrix property. In other words, a texture can be accurately rendered in cases where the Cartographic coordinates of the four corners are known. See the Surface Mesh Primitive topic for more information.
The algorithm for computing an intersection between an Ellipsoid and a cone has been improved. This makes the computation of the projections of the ComplexConic and SyntheticApertureRadarVolume sensors more accurate and predictable.
Unhandled exceptions raised in the TerrainCacheGroup thread (for example, while a TerrainProvider is loading a region of terrain) are now rethrown when TerrainCacheGroupRequestRegionLoad is called. TerrainCacheGroupStartCacheThread can be called to clear the exception and restart the TerrainCacheGroup thread. Previously, unhandled exceptions would silently end the thread and cause poor terrain performance.
Numerous improvements to documentation and examples.
Fixed a bug where TextureScreenOverlay would sometimes fail to update its texture if it was assigned for the first time after it had been rendered.
Fixed a bug in ScalarSingleFrequencyIonosphericCorrection and ScalarSaastamoinenTroposphericCorrection that could result in incorrect results when the receiver's LocationPoint was not defined in the Earth Fixed frame.
Fixed a bug in TerrainCacheGroup that caused it to load the least recently used region instead of the most recently used one when multiple regions were in the queue. This bug fix should yield a performance improvement in certain cases.
Primitive.CentralBody has been made obsolete. Set the PrimitiveReferenceFrame property instead.
The overloads of SetCartographic and SetPartialCartographic on MarkerBatchPrimitive, PointBatchPrimitive, PolylinePrimitive, and TextBatchPrimitive that do not take a CentralBody have been made obsolete. Instead, use the overloads that specify a CentralBody.
ModelPrimitive.PositionCartographic has been made obsolete. Instead, use ModelPrimitiveSetPositionCartographic.
FunctionThreshold has been made obsolete in this release. Instead, use DoubleFunctionThreshold or JulianDateFunctionThreshold.
IPropagateFromInitialConditions has been made obsolete in this release.
IIndexableImmutable and CreateFromArray have been made obsolete in this release.
In AGI Components 2009 r6, the MATLAB example referenced the default install location of AGI Components 2009 r5. In this release, the example uses a relative path so it should work regardless of where AGI Components is installed.
Fixed a bug that could cause EarthOrientationParameters to return NaN instead of a valid value in rare circumstances when working with multiple EarthOrientationParameters instances in a single application.
The Ellipsoid copy constructor, which was marked obsolete in AGI Components 2009 r3, has been removed in this release.
Added the KozaiIzsakMeanElements coordinate type.
Insight3D now continues animating while the user interacts with it using the mouse. The previous behavior can be restored by setting the MouseOptionsAnimateWhileHandling property on the Insight3D control to false.
RotateFilter can now rotate by an arbitrary angle. Previously it only allowed 90, 180, and 270 degree rotations.
Numerous documentation improvements.
Fixed several problems with sensor projections that could cause exceptions or unexpected results in certain unusual cases.
Fixed a bug that prevented the EllipsoidGrid.ReferenceTerrain property from being used with coverage analysis.
The Insight3D control was incorrectly raising a DragDrop event when the DragEnter event should have been raised.
Fixed some problems rendering filled polygons and video on terrain with ATI HD video cards.
ScalarReceivedIsotropicPower and ScalarReceivedPowerFluxDensity previously did not take into account access constraints applied to the link, so "received" power was unaffected by terrain line of sight, etc. In addition, ScalarPropagationLoss will now report 100% loss when the link's access constraints are not satisfied.
Fixed several problems preventing the AGI Components analysis components from being used in a partial-trust environment such as from within an XBAP application. Insight3D (AGI.Foundation.Graphics) still cannot be used in a partial trust environment because of its use of unmanaged code.
Fixed a problem with EllipsoidGridRegions when some of the regions span the international date line.
Examples of using AGI Components from MATLAB are now included in the Examples subdirectory.
An overload of EllipsoidGrazingAltitudeLocation that was marked obsolete in AGI Components 2009 r2 has been removed in this release.
Removed Primitive.RenderPasses, which was previously marked obsolete.
Added support for the International Celestial Reference Frame (ICRF), which can be obtained from the EarthCentralBodyInternationalCelestialReferenceFrame property. By default, the EarthCentralBodyInertialFrame is now ICRF instead of J2000.
The "Mean Earth" fixed frame for the Moon can now be obtained from JPL ephemerides using the JplDE421GetMoonTopographicFixedFrame method.
Added ExtrudedPolylineTriangulatorComputeSingleConstantAltitude to create extrusions with a constant altitude and a varying altitude.
Added a UnitSpherical coordinate type.
Added a CustomSensorPattern class that can be used to define a custom sensor that can then be used to constrain access.
Grids in Spatial Analysis Library now allow users to specify a TerrainProvider as a reference for the grid point heights.
Added support for RINEX meteorological files with the RinexMeteorological class.
Numerous documentation improvements.
The performance of many computations has been substantially improved.
The performance of the TerrainAlongLineComputeElevationAngleAboveTerrain method and the TerrainLineOfSightConstraint access constraint has been substantially improved. This is on top of the general library-wide performance improvements mentioned above.
Numerous improvements to the HowTo application.
Added a new constructor to GpsReceiver that fully constructs the receiver and prepares it for use. Marked the previous constructor, which created a GPS receiver that could not be used to compute accuracy, as obsolete.
ModelPrimitive now supports Collada models (*.dae) with textures with non-power-of-two dimensions regardless of whether or not the video card supports GL_ARB_texture_non_power_of_two.
Fixed the normals returned by ExtrudedPolylineTriangulator. In some cases, incorrect normals lead to incorrect lighting when the returned ExtrudedPolylineTriangulatorResult was assigned to a TriangleMeshPrimitive.
Fixed some potential problems with various access constraints when AccessSampling.UseConstraintSamplingSuggestion is set to false.
Fixed a potential crash related to the GraphicsFont class.
Fixed a bug that caused AccessComputationOverrideConstraintSampling to be ignored.
Fixed a MarkerBatchPrimitive bug where markers with duplicate per-marker textures did not render.
The Insight3D control will now appear when added to the Visual Studio 2008 toolbox even when the project is set to use .NET 2.0. Previously the control would not appear unless the project used .NET 3.0 or later.
A significant number of types, methods, and properties that have been marked obsolete for 6 or more months have been removed in this release.
JulianDateToTimeStandard now throws an ArgumentOutOfRangeException if asked to convert a JulianDate representing a time during a leap second to Coordinated Universal Time (UTC). A TryConvertTimeStandard method has been added to attempt the conversion without throwing an exception if it fails. Also, arithmetic operations on JulianDate (such as Add and Subtract) return a result in International Atomic Time (TAI) if the result cannot be represented in UTC.
AltitudeDisplayCondition and DistanceToPositionDisplayCondition now have a CentralBody and ReferenceFrame, respectively, which default to Earth and Earth's FixedFrame. Previously, these display conditions used the central body of the primitive to which the display condition was applied.
The following classes, properties, and enumerations related to the Insight3D camera have been deprecated in this release: UntetheredCamera, NormalCamera, Camera.Untethered, Camera.Normal, Camera.ActiveViewMode, and CameraViewMode. Equivalent functionality is available on the Camera class.
The orientation of imagery used with the ProjectionStream class has changed. Previously, X went from the bottom to the top of the image, Y went from the left to the right of the image, and positive Z went into the image. Now, the orientation is a more conventional scheme where X goes from the left to the right of the image, Y goes from the bottom to the top of the image, and negative Z goes into the image. This change means that it is no longer necessary to invert a quaternion representing the transformation from CBF before assigning it to the ProjectionStream.
SimulationAnimation and RealTimeSimulationAnimation no longer validate the StartTime, EndTime, StartCycle, and EndCycle properties when those properties are set. Instead, they are validated when animation is started. This frees the user from needing to worry about the order in which the properties are set.
Primitive.RenderPasses has been deprecated in this release.
CrossPlatform.ParseDateTime has been deprecated in this release.
Many access constraints have logic to suggest the next sampling step in order to avoid missing interesting features of the constraint function. This can now be disabled by setting the AccessSampling.UseConstraintSamplingSuggestion property to false, in which case the function will be sampled using the AccessSampling.DefaultStep instead.
Added support for rendering imagery from a WMS-C server to the Insight3D globe via the WebMapServiceCachedImageGlobeOverlay class.
Added TryCartographicToWindowCoordinate, CartographicToWindowCoordinate, TryWindowCoordinateToCartographic, and WindowCoordinateToCartographic methods to the Camera class to quickly find the longitude, latitude, and altitude corresponding to a specified pixel, or vice-versa.
Added a SurfaceDistanceConstraint to constrain access based on the distance between two objects along the surface of the Earth or another central body.
Numerous documentation improvements.
The terrain extent computed by the GTOPO30Terrain reader has been changed slightly in order to improve conformance with STK Desktop and with the terrain format specification. The previous behavior, if required, can be restored by passing the GTOPO30Options.StrictlyHonorUpperLeft option to the constructor.
A single CompositePrimitive can now hold both opaque and translucent primitives. Previously, it threw an exception when adding primitives with different render passes.
SurfaceMeshPrimitiveTexture now supports textures with non-power-of-two dimensions regardless of whether or not the video card supports GL_ARB_texture_non_power_of_two. Therefore, SurfaceMeshPrimitiveTexture no longer throws InsufficientVideoCardException.
Improved performance when passing arrays of Cartographic positions to many methods in Insight3D.
Improved the performance of GeometryTransformer in certain cases.
TerrainAzimuthElevationMaskCompute no longer computes the ray at both 0 degrees and 360 degrees, which yields a small performance improvement.
Fixed a bug in AGIProcessedDataTerrain that caused it to fail on big-endian processor architectures such as SPARC.
Fixed a bug that affected the light intensity of some TriangleMeshPrimitives.
Fixed an exception in RinexObservation when reading an observation file that contains only one record.
Fixed a rendering problem when extremely small PDTTX or JP2 files were added to the Insight3D globe.
Fixed a bug in StkAttitudeFile that caused it to write files that could not be read by STK.
Fixed a bug that could cause camera's position to be updated incorrectly when setting the CameraPosition property.
An uncommonly used overload of EvaluatorGroupCreateEvaluator was misspelled in the previous release and has been corrected.
TotalAngularRateConstraint now computes the angular rate with respect to the reference frame of the constrained link end, which is the end of the link to which the constraint has been applied. Previously the rate was computed with respect to the displacement vector's axes, which could be different if accounting for light-time delay.
The functionality previously in AGI.Foundation.Terrain.dll has been split into two assemblies: AGI.Foundation.TerrainReaders.dll and AGI.Foundation.TerrainAnalysis.dll. You will need to update the references in your projects.
This release includes Insight3D®, a flexible and high-performance 3D visualization component. It is a technically accurate 3D globe with excellent support for visualizing time-dynamic geometry. For more information, see the Visualization with Insight3D® topic in the documentation.
StkEphemerisFile now provides an interpolator for StkEphemerisFileEphemerisLLATimePos, making it much simpler to read longitude, latitude, and altitude data from an ephemeris file and use it for analysis.
AxesVehicleVelocityLocalHorizontal is now defined with a reference frame instead of a central body. This allows the axes to be oriented based on, for example, the velocity in the fixed frame rather than the velocity in the inertial frame.
EarthCentralBodyOrientationParameters is now, by default, configured with a default-constructed EarthOrientationParameters. This allows the transformation between the Earth Fixed and J2000 frames to be computed, though somewhat less accurately, without first loading EOP data.
Numerous documentation improvements.
A bug has been fixed that prevented the "simple" licensing system from finding a license embedded in an assembly other than the entry assembly. The entry assembly is usually the application executable.
Fixed a numerical stability problem in AGIWorldTerrain that could cause it to throw an exception when attempting to provide the terrain height at certain valid locations.
This release includes changes to the mechanism for licensing AGI Components for use in your applications. While it is designed to be minimally intrusive, you will need a new license and to take some basic steps to avoid licensing exceptions at runtime. Please see the Getting Started or Licensing and Deployment topics for more information.
CoverageDefinitionOnCentralBody now has the option to store the grid cell boundary vertices along with the coverage data in the CoverageGridResult. This is useful when plotting results.
Fixed an issue with BrentFindExtremum for certain functions where it would take an infinitesimal step and cause the algorithm to 'converge' prematurely.
The EllipsoidGrazingAltitude method now guarantees that the resulting minimum altitude is measured at a point between the two end points.
Fixed an issue with the Ellipsoid.SurfacePoint method when specifying a heading of zero with respect to a spherical instance of Ellipsoid.
VectorNormalized now handles zero-vectors better.
Fixed an issue with AGIWorldTerrain where it would calculate some post indices incorrectly.
Fixed Duration so that it is possible to multiply by a fractional value and get the correct result.
Please contact us at firstname.lastname@example.org and we will be glad to help you update your existing code to work with this release.
Evaluators are now expected to implement the IAvailabilityGetAvailabilityIntervals method instead of the AvailabilityIntervals property. The new method allows the caller to specify the intervals over which they are interested in the availability.
The Ellipsoid class is now immutable, meaning it cannot be changed after it is created.
Introducing Communications Library, which analyzes communication signals by modeling antenna gain patterns, wireless propagation effects, and hardware processing. It provides several ways to analyze signal data, including the creation of "Link Budgets" based on various scalar parameters such as ScalarCarrierToNoise or ScalarBitErrorRate<TModulation>. It also models the effects of multiple signals interfering with an intended signal. For more information on Communications Library, see the Communications topic.
AxesAlignedConstrained now allows the user to specify which axes to use as the principal and reference.
BrentFindExtremum now has better behavior for flat functions and other special cases. This may improve access results in certain cases.
StkSatelliteDatabase now treats the wr, fr, and tce files that are normally part of the database as optional. This is useful when using a custom satellite database.
Default-constructed AzimuthElevationMaskConstraint, ThirdBodyElevationAngleConstraint, LineTargetElevationAngleConstraint, and AreaTargetElevationAngleConstraint objects now default to having a MinimumValue of 0.0 radians. Previously neither MinimumValue nor MaximumValue was set, so the constraints effectively did nothing unless the user explicitly set one of these properties.
GeometryTransformer now computes transformation chains between axes and reference frames more quickly in certain cases.
This release of AGI Components is now tested against Mono v2.2.
Numerous documentation improvements.
Fixed a bug that could cause an "eccentricity violation" exception when computing access with an SGP4-propagated satellite and light-time delay enabled, even with a valid TLE and computation interval.
AccessEvaluator now correctly reports its availability as infinite. An access query can be evaluated at any time. If an underlying quantity is not available at that time, the result of the query is that access is "unknown."
Fixed a bug in TimeGenerator that could cause it to very rarely return two identical times at the end of the interval. This could manifest itself as two identical times being returned from evaluating any evaluator over an interval.
Fixed a bug in Heading that could cause the algorithm to compute NaNs in certain very rare circumstances.
VectorMagnitude no longer throws an exception when the magnitude is zero.
Spatial Analysis Library now multithreads the creation of grid points in order to improve performance on multi-core and hyperthreaded hardware.
AGI Components is now built using Visual Studio 2008. This change should be transparent as Visual Studio 2005 and .NET 2.0 are still fully supported in this release.
Numerous documentation improvements.
Fixed a bug in the constructor for Waypoint that takes a previous waypoint. The bug would result in an exception ("The waypoint collection does not model constant accelerations between the waypoints") when attempting to use the waypoints with WaypointPropagator.
Terrain Analysis Library now has the ability to read terrain data in the AGI PDTT format using AGIProcessedDataTerrain.
Navigation Accuracy Library now has the ability to read RINEX Observation files using RinexObservation.
VectorDifferentiator and PointDifferentiator now have a DerivativeToCompute property. Previously, these types always computed the next derivative after the highest available from the underlying vector or point.
Added an EllipsoidGridSpecified type that makes it easy for the grid points used in a coverage computation to be given explicitly by the user.
Addressed a difference between the convention used to represent rotational motion in an StkAttitudeFile and that used in the rest of AGI Components. This could cause rotational motion interpolated from an attitude file to be interpreted incorrectly. See AttitudeData for more information.
EarthGravitationalModel1996 now has unnormalized versions of the J2, J3, and J4 constants. Also, the documentation for J2Propagator and J4Propagator has been updated to refer users to these constants.
Numerous documentation improvements.
Fixed a bug in the Satellite Tracker demo application that could cause it to fail to invoke Google Earth when exporting KML.
Fixed a bug in StkEphemerisFile that caused it to throw an exception when encountering an .e file with comments.
Several Ellipsoid methods now check to see if they are operating on a point that is very close to the center of the ellipsoid and throw an exception if this is the case. Previously, these methods could, in rare situations, get stuck in an endless loop.
Evaluators now have overloaded Evaluate methods that sample the evaluator at a fixed step over an entire interval. The sampling is automatically performed in multiple threads, as appropriate, for best performance on multi-core systems.
Added a new type, TerrainAlongLine, which provides a simple way to determine terrain obscuration between two points.
Added GTOPO30Terrain to read terrain data in the GTOPO30 format.
Added a DegreesMinutesSeconds type to work with angles represented as these three components.
Made it much easier to construct a PointInterpolator to interpolate over a set of position and velocity data. New constructors accept the required information directly rather than requiring the construction of several additional objects.
Simplified the use of LagrangePolynomialApproximation and HermitePolynomialApproximation by adding InterpolateWithDegree methods. These methods interpolate over an appropriate subset of the data, chosen based on the degree of interpolation and the x-value at which to interpolate.
GeometryTransformerObservePoint is now smarter about avoiding unnecessary transformations. In particular, it will now perform only a trivial operation if asked to observe a point in a reference frame that has that point as its origin.
SatelliteGlobalUserRangeError now exposes clock phase error.
Numerous documentation improvements.
StkEphemerisFile no longer fails with an exception when reading a .e file with covariance data.
Fixed a problem where TerrainLineOfSightConstraint could miss obstructing terrain when the two objects are far apart and the "lower" object is in a very flat region of terrain.
Fixed a problem where an EllipsoidRhumbLine could travel the long way around the ellipsoid.
The RINEX file readers now allow blanks, representing data that was unknown when the files were created. Previously, the readers threw an exception when they encountered a blank.
Fixed a problem in NgaDigitalTerrainElevationData that caused the reader to report unknown heights for certain cells even though the cells existed and had valid data.
Please contact us at email@example.com and we will be glad to help you update your existing code to work with this release.
Custom access constraints written for previous releases will not work in this release.
Classes implementing IFunctionSamplingStrategy are now also required to implement the methods of IThreadAware.
Introducing the Spatial Analysis Library, which provides several major new capabilities:
Define a set of assets that can cover a region. An asset can be a spacecraft, aircraft, constellation, chain, or any boolean combination of these.
Define and discretize a region using one of several gridding algorithms.
Determine the coverage of the region by the assets.
Compute statistical information (Figures of Merit) related to the coverage of the region.
Effectively, Spatial Analysis Library brings many of the capabilities of STK/Coverage to AGI Components. For more information, see the Coverage topic.
Access Queries enable the modeling of sophisticated intervisibility problems involving any number of objects. Access constraints on one or many objects can be combined using boolean operators such as And, Or, Not, AtLeastN, AtMostN, and ExactlyN. Access queries can be used to model a chain and will account for light-time delay between each hop. Access queries bring many of the capabilities of the STK Chain and Constellation objects to AGI Components, and in fact enable many use cases that STK cannot support.
Previously, EllipsoidGeodesic could get stuck in an endless loop when given certain ambiguous cases. Now, it will instead throw an exception explaining the problem.
Fixed a number of bugs in TimeIntervalCollection that could yield incorrect results for certain operations in unusual cases.
Several new navigation-related access constraints were added to Navigation Accuracy Library:
Navigation Accuracy Library can now operate in a 'diligent' or 'lazy' mode when computing accuracy using Prediction Support File (PSF) data. Previously this option was only available when computing accuracy using Performance Assessment File (PAF) data.
Added an analytical model for the positions of the planets and Earth's moon based on a paper by Simon et al. This new model, found in Simon1994PlanetaryPositions, is now the default model used by all central bodies. This means that it is no longer necessary to load and configure JPL DE data before performing computations that depend on planetary positions. However, you may still want to use JPL DE data because it is more accurate than this analytical model.
The orbital element types now take optional tolerance parameters, where appropriate. Also, these types now throw more reasonable and consistent exceptions when given invalid input.
Numerous documentation improvements.
Fixed a bug in PointVectorToPoint that resulted in one less than the highest requested derivative being returned. If no derivatives were requested, the returned position would be incorrect as well.
Support for two new terrain formats has been added to Terrain Analysis Library:
The name has been changed from AGI Component Technology to AGI Components.
Numerous documentation improvements.
The CHM documentation will now remember the language selection made with the drop-down list in the upper right-hand corner.
This release of AGI Components is now tested against Mono v1.9.
Some changes to evaluators and evaluator groups have been implemented to improve performance and to simplify the task of writing a new evaluator. If you have written your own evaluator or if you are using evaluator groups to improve performance, please see the Evaluators And Evaluator Groups topic for a description of the changes.
Fixed a bug in EarthCentralBodyFixedFrame where values computed prior to the J2000 epoch were computed incorrectly. This could affect the transformation between the Earth Fixed and Earth Inertial reference frames.
Fixed several bugs in RinexNavigation that could cause certain files to fail to parse.
Fixed a bug in GpsRinexPropagator that could cause it to miss the first time step when evaluating.
Fixed a bug in the RectangularPyramid sensor type that could cause the enclosure function to compute NaNs in very specific circumstances.
Fixed a bug in AzimuthElevationRangeConvertMotion that caused the range-rate to be computed incorrectly.
Fixed a bug in ScalarDihedralAngle where the dihedral angle would not be computed correctly if the vectors used to measure the angle were expressed in different axes.
A new interface has been added, IIsTimeVarying, which allows evaluators to report whether or not they have a different value as a function of time. All evaluators implement this interface and by default they return true. For best performance, the IsTimeVarying method should be overridden to return false when the evaluator is known not to change with time.
PointEvaluator, AxesEvaluator, ScalarEvaluator, and VectorEvaluator now have a SimplifyIfNotTimeVarying method. By calling it in the GetEvaluator-type methods after obtaining the evaluator, the evaluator complexity can be substantially reduced. This is done for many of the evaluators included in the library and results in a substantial performance improvement when, for example, computing access to a stationary facility.
EarthCentralBody now has a SlowChangingAxesUpdateInterval property. By default, this interval is used by Iau1976Precession and Iau1980Nutation for their CacheSeconds value. It is still possible to set the CacheSeconds property explicitly to override this value. It is also used for updating pole wander during the Earth Fixed → Inertial transformation. The default value is 0, indicating that the values should be computed every time, so previous results should be unaffected. However, increasing this value will result in a significant performance improvement for many use cases with little to no difference in results.
CartographicZoneConstraint now offers the ability to obtain the zone parameters from the constraint after they have been set. Previously they were write-only.
SatelliteOutageFile now has several FindOutages methods to find the outages corresponding to a particular PRN or interval.
CentralBodyObstructionConstraint will now yield better performance when not considering light-time delay.
The documentation has been improved in several places.
The performance of Dilution of Precision (DOP) and RAIM calculations has been substantially improved.
Fixed a serious race condition in TranslationalMotionInterpolator and RotationalMotionInterpolator that could cause them to report wrong numbers when used from multiple threads simultaneously even after doing a CopyForAnotherThread.
Fixed a serious race condition in DefaultAccessSamplingStrategy that could cause incorrect sampling of constraint functions during access computations. The incorrect sampling could cause missed intervals of access or, under certain circumstances, unexpected exceptions.
The first release of AGI Component Technology!