{section: How to Debug Complicated Class Ad expressions}
-Known to work with Condor version: 7.7.0 and later, and 7.5.6 and earlier.
+Known to work with HTCondor version: 7.7.0 and later, and 7.5.6 and earlier.
-The Condor ClassAd system is a powerful mechanism to describe policy and behavior. However, sometimes, debugging a complicated classad expression can be difficult, especially if the expression evaluates to UNDEFINED, for no obvious reason. The ClassAd builtin function "debug" is handy in this case. Debug is a ClassAd function which takes another classad function as an argument, evaluates it, and returns it. That is, wrapping any classad expression with debug() makes no changes whatsoever to that expression's semantics. What does change, though, is that if the daemon that evaluates that expression has D_FULLDEBUG on, informatino about the evaluation of that one classad expression is logged to that daemon's log file.
+The HTCondor ClassAd system is a powerful mechanism to describe policy and behavior. However, sometimes, debugging a complicated classad expression can be difficult, especially if the expression evaluates to UNDEFINED, for no obvious reason. The ClassAd builtin function "debug" is handy in this case. Debug is a ClassAd function which takes another classad function as an argument, evaluates it, and returns it. That is, wrapping any classad expression with debug() makes no changes whatsoever to that expression's semantics. What does change, though, is that if the daemon that evaluates that expression has D_FULLDEBUG on, informatino about the evaluation of that one classad expression is logged to that daemon's log file.
For example, consider a submit file with the requirements line
