|Top Previous Next|
The Save command saves the state of an object (and any attached objects) in internal memory. The Restore command can be used to return the object to the saved state.
•An unlimited number of objects can be saved using a single command.
•The Object.Save() method can be used as an alternative to the Save command.
oThe Object.PutToFile(), Object.PutToString(), Object.GetFromFile(), and Object.GetFromString() methods can also be used in place of the Put and Get commands.
•All the properties of the Saved object(s) are saved, including the properties of all subsystems such as Propagators, ForceModels, and hardware such as Sensors, Tanks, GroundAntennas, etc.
•The Save and Restore commands can only be used to restore an object back to a previous state.
oThese commands can’t be used to save the state of one object and then populate another object with that state.
•The string used with the optional "as" and "from" clause is used to identify the saved states, allowing you to hold multiple saved states in memory.
oIf the "as" and "from" clauses are not used, the Restore command will use the data from the most recent Save command.
oYou can save the state of the same object at different points in the Mission Sequence and restore it to those times separately, so long as you use different strings (for example, "SCstate1" and "SCstate2").
•Saved states persist in memory only during the current execution of the Mission Plan. Therefore, states from a previous run cannot be accessed during a new run.
•Saved states can be cleared using the Object.ClearSavedStates() method.
Object to Save