Lyse Error and Usage

[Alex M.]

Hello all,

I am trying to run a simple single-shot test routine on lyse for the first time, and I am encountering several errors.

Firstly, I got an error in lyse saying that the config file could not be loaded. I understand that this may be an issue from running lyse for the first time, and could be solved by closing and reopening lyse, but this did not work for me.

Additionally, when I try to send the shot file to lyse from BLACS using the Analyse button, it seems to not do anything. However, I can manually access the shot using the green plus button in lyse.

I have attached screen shots of these two errors. Any help is greatly appreciated!

Thank you,

Alexander

[dihm....@gmail.com]

Alexander,

For the BLACS issue, you need to provide the IP address of the computer that is running lyse. If lyse is on the same computer as BLACS, type localhost into that box.

For the lyse error, you are only having issues loading prior state. Lyse is running just fine despite it. When you closed lyse, it should have asked if you want to save the state: be sure you answer yes to that. If you are still having problems, look at the contents of the lyse config file it is trying to load. It may be that the path is wrong or there is some error in the file itself somehow.

-David

[Alex M.]

Hello David,

Thank you for the help with the BLACs error. I tried looking for the config file that seemed to be responsible for the lyse GUI state error, but I couldn't find it. To try to solve this problem, I deleted the appsavedconfigs folder, closed out of all python processes related to labscript, and started everything, including lyse, again to see if the config folder would be created. However, this did not occur. Lyse also never prompted me to save the state, even when closing out multiple times.

Is there a way to ensure that the appropriate config file for lyse is created in appsavedconfigs?

best,

Alexander

[David Meyer]

Alex,

There is a file menu option for saving/loading configs. But I would call that an option of last resort. The config should be saved automatically, though it only prompts if it has actually changed. Closing lyse multiple times without the prompt means it has a config file somewhere that it is using. There are a couple of places you should check to ensure paths are consistent. The overall goal is to check every possible path definition explicitly to figure out why the file isn't being found correctly.

- Check your experiment config file for where it says the lyse config file should be.

- Make sure you are running lyse from where you think you are. This is a common issue if there are multiple installations of labscript on the same computer. You can check by opening a python interpreter in your environment, importing lyse, then printing lyse.__file__ to see what directory the installation you have imported from.

- Make sure you are using the correct labscript profile location. Similar issues occur if you have multiple installations with distinct profiles. You may also need to recreate the profile from scratch if things have become very messed up. In that case, save the old folder somewhere else and selectively move over your files after creating the profile from scratch.

- You should also add a print statement in the source code near where the error is raising from that prints the directory it is loading the file from. You can also add prints to inspect the contents of whatever file is loaded.

- As a fail safe, you can always search your drive for the file name (lyse.ini, I believe). There should only be one.

-David

--
You received this message because you are subscribed to a topic in the Google Groups "the labscript suite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/labscriptsuite/zMzVqFPY4fA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to labscriptsuit...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/labscriptsuite/5d4b644c-90c5-436a-8cf4-69286059437dn%40googlegroups.com.

[Alex M.]

Hello David,

Ah, I see. Seems it was a path error. Now lyse is working and the GUI state is being saved. Thanks for all the help!

best,

Alex

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, visit https://groups.google.com/d/msgid/labscriptsuite/CALWn_A8i%2BiFQM_2GDBXh5AHy5s2wDpRU66pMwPcW2EjBTNL6Og%40mail.gmail.com.