The ACTIVATE command, used in conjunction with the DEACTIVATE command, switches Adams/Solver (C++) elements on and off. All Adams/Solver (C++) elements are active by default in the input dataset, but can be deactivated using the DEACTIVATE command. For simulation purposes, when Adams/Solver (C++) activates a statement, the statement appears as though it was always in the dataset. When Adams/Solver (C++) deactivates a statement, the statement effectively disappears from the model. Both the ACTIVATE and DEACTIVATE commands take effect when you issue the next SIMULATE command.
After the activation of any element, Adams/Solver (C++) reprocesses the model at the next SIMULATE command, as if it had just been read in from the dataset. During the reprocessing, Adams/Solver (C++) checks the entire model for consistency, reinitializes user subroutines, and recomputes initial conditions.
While checking the entire model, Adams/Solver (C++) verifies that the model is still valid when the newly activated elements are included. For example, if an activated JOINT overconstrains a model resulting in an immobile system, Adams/Solver (C++) issues an error message. Adams/Solver (C++) also reinitializes all user subroutines to re-establish functional dependencies. For each element that refers to a user-written subroutine, Adams/Solver (C++) calls the user-written subroutine with IFLAG set to true.
Prior to the actual simulation, Adams/Solver (C++) computes initial conditions for the model. If this is the first simulation, Adams/Solver (C++) begins with the positions and velocities specified in the dataset, and maintains any user-supplied joint initial-conditions and part positions specified as EXACT. If you ran a previous simulation, Adams/Solver (C++) begins with the final displacements and velocities. Adams/Solver (C++) then adjusts the initial conditions to ensure that they are consistent with the model constraints.