-
Notifications
You must be signed in to change notification settings - Fork 0
/
2-Inputs_Outputs.txt
43 lines (37 loc) · 1.73 KB
/
2-Inputs_Outputs.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
----####-------------------------------------------####---
For real variables the subroutine
DEBUGGER_REAL should be used.
----####-------------------------------------------####---
The input for the debugger is:
DEBUGGER(VARIABLE,NUMBER OF LINES, NUMBER OF COLUMNS, CHARACTER NAME, LINE NUMBER, TYPE OF OUTPUT)
a) For example in the case of a matrix:
call debugger_real(ddsdde,ntens,ntens,"JACOBIAN",288,0)
b) For example in the case of a vector:
call debugger_real(stress,ntens,1,"STRESS",173,0)
c) For example in the case of a scalar:
call debugger_real(celent,1,1,"CHARACTERISTIC LENGTH",69,0)
The TYPE OF OUTPUT, should always be INTEGER, and can be:
a) 0
For non-formating number presentation, may dependend on the operating system and compiler.
Caution is advise for a correct presentation.
b) 1
For Scientific number presentation, may dependend on the operating system and compiler.
Caution is advise
c) 2
For Scientific number presentation. According to Fortran 90 standards for all compilers.
The line number is optional, but a number is required.
Recomending using the line number of your IDE code to help debugging.
----####-------------------------------------------####---
For integer variables the subroutine
DEBUGGER_integer should be used.
----####-------------------------------------------####---
The same input as the real debugger subroutine
The TYPE OF OUTPUT, should always be INTEGER, and can be:
a) 0
May dependend on the operating system and compiler.
Caution is advise for a correct presentation.
b) 1
May dependend on the operating system and compiler.
Caution is advise
c) 2
According to Fortran 90 standards for all compilers.