Error handling & support

The causalchamber package can raise two types of errors

LabError	This indicates an error on our side, e.g., due to a hardware failure or an internal server error.
UserError	These can arise during normal operation of the system—e.g., you reached the limit of queued experiments—or result from an error on your side, such as setting incorrect credentials or submitting an invalid instruction.

In either case, if an error persists or you are stuck, please let us know so we can help you. You can reach us at [e-mail] or through any of the support channels provided during onboarding.

See Troubleshooting for a list of common issues and how to solve them.

Example

Let's trigger a UserError by sending an invalid instruction to a chamber.

import causalchamber.lab as lab

# Open a real-time connection
chamber = lab.Chamber(chamber_id = 'lt-demo-ch4lu',
                      config = 'standard',
                      credentials_file = '.credentials')

# Submit an invalid instruction (value out of range)
chamber.set('red', 999)

This raises the following exception

---------------------------------------------------------------------------
UserError                                 Traceback (most recent call last)
[Trace details omitted]
UserError: (code 400) Line 1: Value 999 for variable 'red' is above maximum 255
  Trace codes
      (chamber: c687d22c-d07e-4aec-8ef1-0fd3ae40b188)
    (scheduler: cc512e6c-c11f-43d2-afdb-030b3bae9847)

Besides a description of the error and the traceback, the exception also provides trace codes, e.g., the uuid strings c687d22c-d07e-4aec-8ef1-0fd3ae40b188 and cc512e6c-c11f-43d2-afdb-030b3bae9847. These allow us to track your request through our entire stack.

Reporting errors

The best way to report an error is to send us the complete error trace, including the traceback and trace codes.

You can report an error through [e-mail] or any of the support channels provided during onboarding.