Dashboard Experiment Names/Scanning

RyanEverly

Hi,

I'm setting up the management system by going through chapter 8 of the documentation. I'm at the point where I am able to put new experiments into the artiq-work folder and then add/commit/push them. The new experiments pop up in the dashboard explorer but I have to run 'artiq_client scan-repository' for newly pushed experiments to show up. I followed the steps to have the master automatically scan the repository when a new commit is made but it isn't working. I made a new file ~/artiq-master/repository/hooks/post-receive with the same contents as the documentation. I'm not exactly sure what type of file this should be so I made it the same as all of the other files in the ~/hooks directory (.sample).

Also when I scan the repository, the original mgmt_tutorial.py experiment shows as MgmtTutorial while my other 2 experiments show up as Tutorial and Tutorial1 even though those are not the names.

Has anyone had problems like this? If so, any help is appreciated.

fsagbuya

RyanEverly
Try to create the file as is without the .sample extension. Via command line:

cd ~/artiq-master/repository/hooks/
touch post-receive

Then edit the file as per the documentation and set the required permissions.

chmod 755 ~/artiq-master/repository/hooks/post-receive

multi131

I think for us it's the case that we need to manually rescan (right-click in the experiments explorer and hit 'Scan repository HEAD') if the repo we get experiments from is a bare repo. If it's a non-bare repo I think the auto-rescan works. Others prob know more about what's actually going on here, but maybe it's that.
The names of the experiments in the explorer can be different from the file names. They usually show up as the class name or as the name defined below the class in a comment, like this:

class CMOT_sequence(EnvExperiment):
	"""V1.1 Rb CMOT sequence & imaging"""
	def build(self):
		...

This shows up as V1.1 Rb CMOT sequence & imaging. Without the comment it shows up as CMOT_sequence.

Not 100% certain if all this is accurate.
Malte

RyanEverly

Yes, that was the problem for naming the experiments. It turns out since there might be multiple experiments in a file, class names are used instead of the file name. Also it looks like creating a basic file, with a file type 'File', and giving it the correct permission works. Thanks for the help!