There are many handy tools implemented in ADCME for analysis, benchmarking, input/output, etc.

## Debugging and Printing

Add the following line before Session and change tf.Session to see verbose printing (such as GPU/CPU information)

tf.debugging.set_log_device_placement(true)

tf.print can be used for printing tensor values. It must be binded with an executive operator.

# a, b are tensors, and b is executive
op = tf.print(a)
b = bind(b, op)

## Debugging Python Codes

If the error comes from Python (through PyCall), we can print out the Python trace with the following commands

debug(sess, o)

where o is a tensor.

The debug function traces back the Python function call. The above code is equivalent to

import traceback
try:
except Exception:
print(traceback.format_exc())

This Python script can be inserted to Julia and use interpolation to invoke Julia functions (in the comment line).

This technique can also be applied to other TensorFlow codes. For example, we can use this trick to debug "NotFoundError" for custom operators

using ADCME, PyCall
py"""
import tensorflow as tf
import traceback
try:
except Exception:
print(traceback.format_exc())
"""

## Profiling

Profiling can be done with the help of run_profile and save_profile

a = normal(2000, 5000)
b = normal(5000, 1000)
res = a*b
run_profile(sess, res)
save_profile("test.json")
• Open Chrome and navigate to chrome://tracing

Below shows an example of profiling results.

## Suppress Debugging Messages

If you want to suppress annoying debugging messages, you can suppress them using the following command

• Messages originated from Python

By default, ADCME sets the warning level to ERROR only. To set other evels of messages, choose one from the following:

tf.compat.v1.logging.set_verbosity(tf.compat.v1.logging.DEBUG)
tf.compat.v1.logging.set_verbosity(tf.compat.v1.logging.INFO)
tf.compat.v1.logging.set_verbosity(tf.compat.v1.logging.WARNING)
tf.compat.v1.logging.set_verbosity(tf.compat.v1.logging.ERROR)
tf.compat.v1.logging.set_verbosity(tf.compat.v1.logging.FATAL)
• Messages originated from C++

In this case, we can set TF_CPP_MIN_LOG_LEVEL in the environment variable. Set TF_CPP_MIN_LOG_LEVEL to 1 to filter out INFO logs, 2 to additionally filter out WARNING, 3 to additionally filter out ERROR (all messages).

For example,

ENV["TF_CPP_MIN_LOG_LEVEL"] = "3"
using ADCME # must be called after the above line

d = Diary("test")
activate(d)