Running Labscript suite on new computer

[Tomáš Lamich]

Dear all,

We are migrating from and old version of labscript to the current one as well as moving to new hardware, however I encountered a problem with compilation for our very basic testing set-up, the code is as follows: 

from labscript import *

from labscript_devices.PrawnBlaster.labscript_devices import PrawnBlaster
from labscript_devices.NI_DAQmx.labscript_devices import NI_PCI_6713

PrawnBlaster(name='prawn', com_port='COM8', num_pseudoclocks=1, clock_frequency=20000000.0)

NI_PCI_6713(name='ni_card_1',parent_device=prawn.clocklines[0], clock_terminal='PFI0', MAX_name='Dev1')

start()
t0=10e-6
t=t0
t+=10
stop(t)

The console output is:

Warning: Cannot save version control data for imported scripts. Check that the hg and/or git command can be run from the command line.
Submitting run file 2022-01-17_0001_prawn_test_0.h5.
Couldn't submit job to control server: Could not connect to server: timed out
Compilation aborted.

How can I connect to the control server? We use only locally hosted service running on single PC.

Many thanks,

Tomas Lamich

[dihm....@gmail.com]

Hi Thomas,

I would suggest you have a careful look at your labconfig.ini file. It is what specifies where all the "servers" are, even when only using a single computer. Maybe an old setting has worked in, or the default values from a new install don't actually work for you situation.

If that doesn't do it, will probably need a little more info to go on. Mostly: are you using the runmanager GUI to run this?

-David

[Tomáš Lamich]

Hi David,

Thank you for the suggestion, I did the recommended changes in the lanconfig.ini file. The problem was that BLACS did not create the folder for the connection table.

Yes I was using the runmanager GUI for it.

As a follow up, do you have any suggestion how to deal with this warning: Warning: Cannot save version control data for imported scripts. Check that the hg and/or git command can be run from the command line.

I am using conda installation and I'm not sure if I'm missing a package or something else. I am running on windows, if that is of importance here.

Thanks.

-Tomas

--
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/5G2GZX1zeU0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/f5edd570-c997-473b-92ba-0861a3bd0053n%40googlegroups.com.

[dihm....@gmail.com]

Glad you were able to track down the issue. Initial setup is still something of a pain with the suite if you haven't done it a few times.

>  As a follow up, do you have any suggestion how to deal with this warning: Warning: Cannot save version control data for imported scripts. Check that the hg and/or git command can be run from the command line.

There are a few things you can do. What is happening is labscript will try to save versioning information for the actual script file you are compiling, if present, to the shot file. This can be helpful when trying to look back at old data with a script that changes regularly. To use this functionality you need to have the command line utility for the version control you use installed into your conda environment (so hg or git, both being available via conda). You can enable which one to use via the labconfig.ini file keys 'save_hg_info' or 'save_git_info'.

If you don't want to bother with that, you can tell runmanager to skip this check entirely by setting both to be false. This has an added benefit of generally speeding up compilation times.

-David