Errors encountered when opening the "labscript-suite" components

[SOUMYA ROY]

Hi all,

I was trying to install the "labscript-suite" in my PC according to the instructions given here- https://docs.labscriptsuite.org/en/latest/installation/regular-anaconda/. After installing when I tried to open the components like-  BLACS, runviewer, runmanager, etc., errors were showing. Here, I have attached a screenshot of the errors showing. I tried to find in web for any solutions, but I did not find anything helpful.

I am very new to this "labscript-suite" interface and I will be grateful if anyone can give me some suggestions regarding this problem.

Best regards,

Soumya.

[Chris Billington]

Hi Soumya,

It looks like the file storing the encryption key used by labscript for network communication doesn't exist. This file would normally be generated when you run labscript-profile-create.

There is a problem with the latest zeromq package from Anaconda, which means it does not include cryptography support. Perhaps when labscript-profile-create attempted to generate a key, it was not able to because of this (you may have seen an error about this when you ran labscript-profile-create).

You may want to try downgrading zeromq:

conda install zeromq=4.3.4

Then I would suggest you simply delete the "C:\Users\Soumya Roy\labscript-suite" directory (assuming you have not created any files in here that you care about) and run  labscript-profile-create again. If you get errors whilst running it, include them in your reply and we'll try to figure out what else might be going wrong.

Regards,

Chris

--
You received this message because you are subscribed to the Google Groups "the labscript suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/0e6d20fa-1b7e-4480-a3ed-d1daa9751c47n%40googlegroups.com.

[SOUMYA ROY]

Hi Chris,

Thank you for your suggestions! I did as you suggested and I am now able to open the "runviewer" and "runmanager" in my PC without any errors. However, when I try to open the "BLACS" and "lyse", different errors are showing for each of them (attached screenshots). It will be great if you kindly see them once and give me some suggestions regarding these.

Best regards,

Soumya.

[dihm....@gmail.com]

Soumya,

The lyse error is just a symptom of the first run of lyse. If you close it and open again, I believe it will go away.

The BLACS error is due to not having a compiled connection table configured. You need to carefully follow the first run instructions outlined in the docs to clear that up.

-David

[SOUMYA ROY]

Hi David,

Thank you for the suggestions! I have solved the previous problem in the BLACS. Now, I am able to open all the components of "labscript-suite" without any errors. Now, I am trying to run the labscript-file (shown in screenshot) in the runmanager and I have noticed that there are some errors occurring (shown in screenshot). I am still trying to solve these errors and it will be helpful if you can give me some suggestions regarding these also. 

[Chris Billington]

Hi Soumya,

The compilation itself is succeeding, and the error is occuring when the resulting shot file is sent to BLACS to be run on the hardware. This error indicates that there is a mismatch between your lab connection table (the file BLACS uses to know what hardware is available), and the connection table part of the labscript file you are compiling (in this case, the labscript file only contains a connection table and nothing more).

To ensure they match, follow the instructions for compiling a connection table similar to what you said you've done already, but include in the connection table the same lines as in the labscript file you are trying to compile. In this case since the labscript file you are trying to compile is actually just a connection table and nothing more, you should use it verbatim as your lab connection table.

When later you want to compile labscript shots that use different hardware, you will need to keep your lab connection table up to date with whatever hardware you want to use, such that it always contains all hardware that is used by any labscript shots you want to run.

Regards,

Chris

To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/c4e4180d-6420-47a0-9f9a-79253a7985a1n%40googlegroups.com.