panel set acf_twindow deactivate
Turns off a statement that was previously turned on by the ACTIVATE command or was active by default
Format:
panel set acf_twindow deactivate |
|---|
beam_name = | an existing beam. |
bushing_name = | an existing bushing |
field_name = | an existing field |
joint_name = | an existing joint |
jprim_name = | an existing primative joint |
motion_name = | an existing motion |
sensor_name = | an existing sensor |
single_component_force_name = | an existing single-component force |
spring_damper_name = | an existing spring-damper force |
group_name = | an existing group |
Example:
panel set acf_twindow deactivate & |
|---|
panel set acf_twindow deactivate beam_name = | beam_1 & |
|---|
panel set acf_twindow deactivate bushing_name = | bushing_1 & |
panel set acf_twindow deactivate field_name = | field_1 & |
panel set acf_twindow deactivate joint_name = | joint_1 & |
panel set acf_twindow deactivate sensor_name = | sensor_1 & |
panel set acf_twindow deactivate sensor_name = | sensor_1 & |
panel set acf_twindow deactivate group_name = | group_1 |
Description:
Parameter | Value Type | Description |
|---|
beam_name | An Existing Beam | Specifies an existing beam. |
bushing_name | An Existing Bushing | Specifies an existing bushing. |
field_name | An Existing Field | Specifies an existing field which you want information on |
joint_name | An Existing Joint | Specifies an existing joint |
jprim_name | An Existing Primative Joint | Specifies an existing jprim |
motion_name | An Existing Motion | Specifies an existing motion generator. |
sensor_name | An Existing Sensor | Specifies an existing sensor |
single_component_force_name | An Existing Single-component Force | Specifies an existing single_component_force |
spring_damper_name | An Existing Spring-damper Force | Specifies an existing spring-damper force |
group_name | An Existing Group | Specifies an existing group |
Extended Definition:
1. A DEACTIVATE command, used in conjunction with the ACTIVATE command, switches Adams elements off and on. All Adams elements are active by default in the input dataset, but may be deactivated using the DEACTIVATE command. For simulation purposes, when ADASMS activates a statement, the statement appears as though it were always in the dataset. When Adams deactivates a statement, the statement effectively disappears from the model. Both ACTIVATE and DEACTIVATE commands take effect when the user issues the next SIMULATE command. Once deactivated, a statement remains inactive until it is activated using the ACTIVATE command.
After the deactivation of any element, Adams reprocesses the model at the next SIMULATE command, as if it had just been read in from the dataset. During the reprocessing Adams checks the entire model for consistency, reinitializes user subroutines, and recomputes initial conditions.
When checking, Adams examines all active-element function expressions and arguments for references to inactive elements. If an active force, constraint or sensor refers to an inactive element, Adams issues an error message just as if the inactive element did not exist. If a force REGUEST or a force GRAPHIC refers to an inactive element, Adams reports zero forces for the inactive element.
Adams also reinitializes all user subroutines to re-establish functional dependencies. For each element that refers to a user-written subroutine, Adams calls the user-written subroutine with IFLAG set to true.
Adams reports zero values in all output files for any forces associated with inactive elements, including both applied forces and joint reaction forces. This includes requests, force graphics, and forces in the results file.
AdamsAdams continues to report displacements, velocities, and accelerations for all JOINT and JPRIM MREQUESTs, even for JOINTs and JPRIMs that have been deactivated. MREQUEST create displacements, velocities and accelerations requests for the markers associated with the specified JOINTs and JPRIMs. Adams continues to output the relative marker displacements velocities and accelerations even if the user has deactivated the original JOINT or JPRIM.
If the user deactivates a constraint or force in the middle of a simulation, by default Adams will split the Tabular Output, Request, Graphics and Results output into two separate set of output concatenated together. This ensures that the output correctly reflects the new system topology.
The OUTPUT/NOSEPARATOR argument will prevent Adams from splitting the file. This allows the user to plot or animate the output continuously from the beginning to end, but may result in misleading graphics during postprocessing.
2. You may identify a beam by typing its name or by picking it from the screen.
If the beam is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the beam is displayed.
If you created the beam by reading an Adams data set or graphics file, the beam name is the letters BEA followed by the Adams data set beam ID number. The name of AdamsAdams BEAM/101 is BEA101, for example. If you created the beam during preprocessing, you gave it a name at that time.
If a beam is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a beam under a different model, for instance, you may need to enter the model name as well. For example, you may specify beam 101 from the model named test by entering ".test.bea101". If you type a "?", Adams View will list the beams available by default.
3. You may identify a bushing by typing its name or by picking it from the screen.
If the bushing is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the bushing is displayed.
If you created the bushing by reading an Adams data set or graphics file, the bushing name is the letters BUS followed by the Adams data set bushing ID number. The name of Adams BUSHING/101 is BUS101, for example. If you created the bushing during preprocessing, you gave it a name at that time.
If a bushing is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a bushing under a different model, for instance, you may need to enter the model name as well. For example, you may specify bushing 'lower_front' from model 'sla' by entering ".sla.lower_front". If you type a "?", Adams View will list the bushings available by default.
4. You may identify a field by typing its name or by picking it from the screen.
If the field is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the field is displayed.
If you created the field by reading an Adams data set file, the field name is 'FIE'. If you created the field during preprocessing, you gave it a name at that time.
If a field is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a field under a different model, for instance, you may need to enter the model name as well. For example, you may specify field 'fld1' from model 'robot' by entering ".robot.fld1". If you type a "?", Adams View will list the fields available by default.
5. You may identify a joint by typing its name or by picking it from the screen.
If the joint is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the joint is displayed.
If you created the joint by reading an Adams data set or graphics file, the joint name is the letters JOI followed by the AdamsAdams data set joint ID number. The name of Adams JOINT/101 is JOI101, for example. If you created the joint during preprocessing, you gave it a name at that time.
If a joint is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a joint under a model, for instance, you may need to enter the model name as well. For example, you may specify joint 'lower_pivot' in model 'links' by entering ".links.lower_pivot". If you type a "?", Adams View will list the joints available by default.
6. You may identify a jprim by typing its name or by picking it from the screen.
If the jprim is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the jprim is displayed.
If you created the jprim by reading an Adams data set or graphics file, the jprim name is the letters JPR followed by the Adams data set jprim ID number. The name of Adams JPRIM/101 is JPR101, for example. If you created the jprim during preprocessing, you gave it a name at that time.
If a jprim is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a jprim under an analysis, for instance, you may need to enter the analysis name as well. For example, you may specify jprim 101 from the analysis named test by entering ".test.jpr101". If you type a "?", Adams View will list the jprims available by default.
7. You may identify a motion generator by typing its name or by picking it from the screen.
If the motion generator is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the motion generator is displayed.
If you created the motion generator by reading an Adams data set file, its name is the letters MOT followed by the Adams data set ID number. The name of Adams MOTION/101 is MOT101, for example. If you created the motion generator during preprocessing, you gave it a name at that time.
If a motion generator is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a motion generator under a model, for instance, you may need to enter the model name as well. For example, you may specify motion generator 'servo' in model 'links' by entering ".links.servo". If you type a "?", Adams View will list the motion generators available by default.
8. You may identify a sensor by typing its name or by picking it from the screen.
Since sensors do not have a geometric position, Adams View displays sensor icons at or near the model origin. If the sensor icon is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the sensor icon is displayed.
If you created the sensor by reading an Adams data set, the sensor name is the letters SEN followed by the Adams data set sensor ID number. The name of Adams SENSOR/101 is SEN101, for example. If you created the sensor during preprocessing, you gave it a name at that time.
If a sensor is owned by the default model, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a sensor under a different model, for instance, you may need to enter the model name as well. For example, you may specify sensor 'fluid_volume_limit' from model 'hydro' by entering ".hydro.fluid_volume_limit'". If you type a "?", Adams View will list the sensor available by default.
9. You may identify a single-component force by typing its name or by picking it from the screen.
If the single-component force is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the single-component force is displayed.
If you created the single-component force by reading an Adams data set or graphics file, the single-component force name is the letters SFO followed by the Adams data set single-component force ID number. The name of Adams SFORCE/101 is SFO101, for example. If you created the single-component force during preprocessing, you gave it a name at that time.
If a single-component force is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a single-component force under another model, for instance, you may need to enter the model name as well. For example, you may specify single-component force 'spring' from the model 'suspension' by entering ".suspension.spring". If you type a "?", AdamsAdams View will list the single-component forces available by default.
10. You may identify a spring-damper force by typing its name or by picking it from the screen.
If the spring-damper force is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the spring-damper is displayed.
If you created the spring-damper force by reading an AdamsAdams data set, the spring-damper name is the letters SPR followed by the Adams data set spring-damper ID number. The name of Adams SPRINGDAMPER/101 is SPR101, for example. If you created the spring-damper during preprocessing, you gave it a name at that time.
If a spring-damper is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. To identify a spring-damper under a different model, for instance, you may need to enter the model name as well. For example, you may specify spring-damper 'left' from model 'sla' by entering ".sla.left". If you type a "?", Adams View will list the spring-dampers available by default.
11. You may identify a group by typing its name.
If a group is available by default, you may identify it by entering its name only. If it is not, you must enter its full name. If you type a "?", Adams View will list the group available by default.
Cautions:
1. You must separate multiple beam names by commas.
2. You must separate multiple single-component force names by commas.
3. You must separate multiple spring-damper names by commas.
4. You must separate multiple group names by commas.
5. You must separate multiple bushing names by commas.
6. You must separate multiple joint names by commas.
7. You must separate multiple field names by commas.
8. You must separate multiple jprim names by commas
9. You must separate multiple motion-generator names by commas.
10. You must separate multiple sensor names by commas.
Tips:
1. If the beam is visible in one of your views, you may identify it by picking on any of the graphics associated with it.
2. You need not separate multiple beam picks by commas.
3. If the single-component force is visible in one of your views, you may identify it by picking on any of the graphics associated with it
4. You need not separate multiple single-component force picks by commas
5. If the spring-damper is visible in one of your views, you may identify it by picking on any of the graphics associated with it.