mumc_configyaml>DEBUG

• Parent:
  • mumc_config.yaml

---

• Description

DEBUG: integer

MUMC DEBUG level.

• There are five DEBUG levels, with an increasing level of verboseness:

  • Level 0 - Disabled
  • Level 1 - Lowest DEBUG level
  • Level 2
  • Level 3
  • Level 4 - Highest DEBUG level

• All DEBUG levels greater than zero will have the following effects:

  • mumc_DEBUG.log will be created in the same directory as the mumc_config.yaml
  • All console_controls will be forced to show: true
  • There is a direct correlation between the amount of information printed to the console and the speed at which MUMC runs
    • The more information printed to the console; the slower MUMC will run
  • There is a direct correlation between the amount of information saved to mumc_DEBUG.log and the speed at which MUMC runs
    • The more information saved to mumc_DEBUG.log; the slower MUMC will run
  • Multiprocessing will be disabled

• The recommendation is to leave at DEBUG: 0, unless it is needed.

• Each time MUMC is run, the previous mumc_DEBUG.log is deleted if it exists.

• If MUMC is run without the DEBUG variable, MUMC will attempt to create a new mumc_config.yaml

Hint:

• At the top of the mumc_DEBUG.log there is a fully populated version of your mumc_config.yaml
• An example of a full mumc_config.yaml can also be found here

---

Example:

DEBUG: 0