•The default Spacecraft epoch has been changed from Jan 01 2010 to Jan 01 2020. This will only affect the output of Mission Plans that do not manually assign a Spacecraft's epoch.
•The FreeFlyer Mission Plan format has been updated to optimize the performance and readability of the saved XML. All Mission Plans created in earlier versions of FreeFlyer are still completely supported in FreeFlyer 7.4. If you inspect the XML contents of any Mission Plans that you load and resave in FreeFlyer 7.4, you will notice the following changes:
oThe LastModifiedDate entry in the XML has been removed to prevent it from always being flagged as a change in version control systems. This information can still be retrieved from your operating system's file properties for the Mission Plan file.
oFreeForm Script blocks in the XML now use single character data (CDATA) blocks to improve readability of the raw Mission Plan file, and to prevent the need to escape characters like < and >, which improves testability of these sections.
oUnused attributes such as notes about whether objects are enabled or disabled have been removed from the XML.
•The default timing precision mode for the runtime API's RuntimeApiEngine class is now nanosecond instead of millisecond timing precision mode. To change back to millisecond timing precision, either load a Mission Plan that is in millisecond timing precision or utilize the method that loads script with the added timing mode argument.
•A ViewWindow will now automatically display the updated label for an object if the object's DisplayName property is changed. This contrasts to previous behavior where the DisplayName could be modified and the ViewWindow would not reflect the change.
•As a result of new features supporting proper ingesting of Trk-2-34 tracking data formats in FreeFlyer's orbit determination system, the legacy means by which DSN 60-byte data could be written out via the DSN60ByteObservationFile object are no longer supported.
•All FreeFlyer-provided data files have been updated with this new release. As a result, there will be expected low order of magnitude differences in propagation and timing precision.
•Various Objects, Properties, Methods, and Functions have been deprecated
oDeprecated Objects, Properties, Methods, and Functions are elements of FreeFlyer which are no longer recommended for use. The description of each deprecated element indicates the new recommended way to achieve the functionality of that element. The complete list of affected elements is given on the Deprecated Objects, Properties, Methods, and Functions page. |