I was testing an ARTIQ device in a conda environment with artiq installed. I believe that the artiq environment is properly installed since I can successfully run artiq_master and artiq_dashboard in the anaconda prompt and launch the dashboard GUI as expected. However, when I try to submit an ARTIQ experiment, the error message displayed in the log window does not contained detailed information tracing back to the origin of the exception, as shown in the following figure.

Detailed error message is also missing in the corresponding prompt terminal in either artiq_master or artiq_dashboard, but it can be displayed when running the artiq program directly using artiq_run in the anaconda prompt. I wonder what may I have done wrong that preventing the dashboard GUI from displaying detailed error message that traces back the exception origin?

Any particular reason you think this is conda related?

    I also ran the same program on another Linux computer with artiq installed via Nix, and the dashboard shows the option to expand the detailed error message tracing back to the origin. Also, in the artiq_run terminal detailed error message can be displayed. Thus I believe the issue of missing detailed error message is not related to the code or to the ARTIQ device.

    sb10q I also ran the same program on another Linux computer with artiq installed via Nix, and the dashboard shows the option to expand the detailed error message tracing back to the origin. Also, in the artiq_run terminal detailed error message can be displayed. Thus I believe the issue of missing detailed error message is not related to the code or to the ARTIQ device.

    Please provide the full source code of an experiment that can be used to reproduce the problem, as well as any other relevant repro steps.

      sb10q After consulting with my colleagues, I realized that I was using a wrong device_db.py file. And after changing to the correct device_db.py file, the dashboard displays detailed message correctly. Does it mean that the dashboard log can only function correctly with the correct device_db.py file?

      No. Again, please provide the entire set of data necessary to reproduce the problem.