Welcome to Adams/Solver Subroutines - Kxcad.net

More documents

Recommendations

Info

8 Adams/Solver Unsupported Subroutines and Their Alternates ADAMS_DECLARE_THREADSAFE A call to the ADAMS_DECLARE_THREADSAFE subroutine informs Adams/Solver (C++) that the user-written subroutine is threadsafe and that multiple threads can execute this user-written subroutine simultaneously. Use Called By Any user-written subroutine Prerequisite None Calling Sequence CALL ADAMS_DECLARE_THREADSAFE () Input Arguments None Output Arguments None Extended Definition Instead of: Use: DEQINF SYSFNC FNCDEP SYSARY; SYSFNC INFO SYSARY; SYSFNC SPLINE AKISPL; CUBSPL ANLMOD GETMOD Adams/Solver (C++) includes the option of threaded (parallel) execution. That is, multiple threads are permitted to execute portions of the code simultaneously. On machines with multiple processors, this can result in a significant reduction in the wall time required for a simulation to complete. This parallel capability places restrictions on the way the code is written to ensure that different threads do not adversely interact with each other. Code that is written in such a way is threadsafe. Care has been take to ensure that relevant portions of Adams/Solver (C++) are threadsafe, but no such assumption can
Welcome to Adams/Solver Subroutines be made about user-written subroutines. Consequently, by default, all user-written subroutines are executed serially. By default, no user-supplied subroutine will take advantage of the parallel capabilities of Adams/Solver (C++). Because complex models often use user-written subroutines extensively, it can greatly improve performance to execute these in parallel, as well. If this is to be done, you must ensure that the userwritten subroutine and its dependants are threadsafe. If so, the user-written subroutine can indicate this with a call to ADAMS_DECLARE_THREADSAFE. This call should occur during subroutine initialization (iflag = true). Adams/Solver (C++) then permits threads to make simultaneous calls to that user-written subroutine. For more information, see the PREFERENCES statement. Writing Threadsafe Code While a complete guide to writing parallel code is left to other texts, a few general points are covered here. Code can be made thread-safe by eliminating any possibility for data (program variables) to be shared between different threads. For example, if all variables in a user-written subroutine were either passed in as arguments or are dynamically allocated local variables, then that user-written subroutine would be threadsafe. Coding in such a manner, however, is often not practical. There may be a need for a user-written subroutine to access constant tabular data or other parameters, which is most efficiently implemented as global data and shared by multiple threads. To allow for this, during subroutine initialization, all userwritten subroutines are run serially. In addition, calls to REQSUBs are always performed serially. General Guidelines 1. The only data that can be modified at any time is: Dynamically allocated local variables. Static or global variable that are uniquely indexed so there is no possibility that two threads will modify them simultaneously. For example, a user-written subroutine with a static array of data could safely modify the array element that is uniquely mapped to the ID of the current modeling element being evaluated. Because each thread is evaluating a different modeling element, the threads will not access the same array element at the same time. 2. All data that will be shared by multiple threads must be allocated and set during subroutine initialization. At other times, this data may be read, but must not be written to. 3. No special coding practices need to be followed inside a REQSUB. FORTRAN-Specific Guidelines 1. Some FORTRAN compilers (such as Digital/Compaq Visual FORTRAN) statically allocate local variables by default. This is avoided by using a compiler option (/automatic) that causes all local variables to be allocated on the stack (unless the SAVE statement is used). 9
Page 1 and 2: Welcome to Adams/Solver Subroutines
Page 3 and 4: Compilers and Linkers Welcome to Ad
Page 5 and 6: Utility Subroutines About Utility S
Page 7: Subroutine: Does the following: Uns
Page 11 and 12: Input Arguments Welcome to Adams/So
Page 13 and 14: RETURN END AKISPL Welcome to Adams/
Page 21 and 22: Use Called By Any user-written subr
Page 23 and 24: T1( x - x0) = x - x0 CUBSPL , Welco
Page 25 and 26: Output Arguments Extended Definitio
Page 27 and 28: Extended Definition Welcome to Adam
Page 29 and 30: Input Arguments Output Arguments We
Page 31 and 32: Input Arguments Output Arguments Ex
Page 33 and 34: Input Arguments Welcome to Adams/So
Page 35 and 36: Use Welcome to Adams/Solver Subrout
Page 37 and 38: GETCPU retrieves CPU time used so f
Page 39 and 40: GETMOD returns the current analysis
Page 41 and 42: Use Called by Any user-written subr
Page 43 and 44: Prerequisite Welcome to Adams/Solve
Page 49 and 50: C C Inputs: C INTEGER ID C C Output
Page 55 and 56: Output Arguments Welcome to Adams/S
Page 57 and 58: C = [-A-1B] Welcome to Adams/Solver
Page 59 and 60:
Output Arguments Welcome to Adams/S
Page 61 and 62:
Prerequisite STRING statement in da
Page 63 and 64:
Prerequisites None Calling Sequence
Page 65 and 66:
function. Welcome to Adams/Solver S
Page 67 and 68:
Calling Sequence CALL IMPACT (x, x'
Page 69 and 70:
Output Arguments Extended Definitio
Page 71 and 72:
Input Argument Welcome to Adams/Sol
Page 73 and 74:
Input Argument Welcome to Adams/Sol
Page 75 and 76:
Use Called By Any user-written subr
Page 77 and 78:
Use Called By SPLINE_READ Calling S
Page 79 and 80:
Input Arguments Welcome to Adams/So
Page 81 and 82:
`S232' Space-two: 2-3-2 `S313' Spac
Page 83 and 84:
Welcome to Adams/Solver Subroutines
Page 85 and 86:
Callng Sequence CALL SHF (x, x0, a,
Page 87 and 88:
Page 89 and 90:
Calling Sequence CALL STEP5 (x, x0,
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
C INTEGER IPAR(2), N_UVX, N_UVY, N_
Page 105 and 106:
CALL NMODES(FBDYID,NQ,ERRFLG) STRIN
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
F(M 1 (q), M 2 (q), ..., M N (q)) W
Page 113 and 114:
Examples Welcome to Adams/Solver Su
Page 115 and 116:
SUBROUTINE SFOSUB (ID, TIME, PAR, N
Page 117 and 118:
DO 100 J = 1 , 6 DFDDIS(I,J)=0.D0 D
Page 119 and 120:
Page 121 and 122:
Use Called By Any user-written subr
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
User-Written Subroutines Welcome to
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
C - Evaluate Normal Force component
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Output Arguments Welcome to Adams/S
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
C X rotational field torque C ... F
Page 169 and 170:
}; int NPAR; const double* PAR; int
Page 171 and 172:
Using the DFLAG Variable Welcome to
Page 173 and 174:
C RESULT(2) = ... RESULT(3) = ... R
Page 175 and 176:
GSE_UPDATE Calling Sequence Welcome
Page 177 and 178:
Page 179 and 180:
Use Corresponding Statement Welcome
Page 181 and 182:
Output Arguments scale A double-pre
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Use Corresponding Command Calling S
Page 191 and 192:
Page 193 and 194:
C ENDIF C C - Create request inform
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
* * SENSOR struct sAdamsSensorEval
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
FORTRAN - Prototype Welcome to Adam
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
C C C C C C C C C C C C C C VALUES(
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
C - Derivatives of prior first deri
Page 227 and 228:
Page 229 and 230:
C C - Subroutine initialization ---
Page 231 and 232:
Page 233 and 234:
*/ struct sAdamsVforce { int ID; in
Page 235 and 236:
FORTRAN - Prototype Welcome to Adam
Page 237 and 238:
Examples For an example of this sub
show all

Welcome to Adams/Solver Subroutines - Kxcad.net

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?