search

labscript-suite-temp-2 / runmanager

runmanager is a graphical user interface (GUI) used to aid the compilation of labscript experiment scripts into hardware instructions to be executed on the hardware. Experiment parameters can be adjusted in the GUI, and lists of parameters can be used to create sequences of experiments, and scan over complex parameter spaces.
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

Engage Log #46

Open philipstarkey opened 7 years ago

philipstarkey commented 7 years ago

Original report (archived issue) by Jan Werkmann (Bitbucket: PhyNerd, GitHub: PhyNerd).

There should be a log file for engaged sequences so that one can find measurements from previous days/weeks more quickly. This shouldn't be too hard to do.

philipstarkey commented 7 years ago

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

That's a great idea. With auto diffs for what globals changed from the previous sequence. ...or even a diff for what changed in your labscript file each time too. That would be so handy.

philipstarkey commented 7 years ago

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

Given the star trek references I propose it be called "captain's log"

philipstarkey commented 7 years ago

Original comment by Jan Werkmann (Bitbucket: PhyNerd, GitHub: PhyNerd).

I would be already be happy without the whole diff stuff just being able to find stuff more quickly (the folder structure is kind of a mess in my opinion). But diffs would make this even better.

lol to the "captain's log". Sure let's call it that.

philipstarkey commented 7 years ago

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

At JQI they've changed the folder structure to have a new folder for each sequence, and the folders are just an integer that increment starting from zero each day. I think we have an issue filed about that somewhere - something I'm planning on at least making optional in the mainline repository, or just having it be default if others agree it's better.

If not diffs, what would you propose be in the log? Just timestamps, the labscript file and the number of shots?

philipstarkey commented 7 years ago

Original comment by Jan Werkmann (Bitbucket: PhyNerd, GitHub: PhyNerd).

jup saw that issue it's over at labscript if I'm not mistaking. I proposed this here also a few weeks ago.

timestamp, scriptname, folder that the sequence is stored in, amount of shots would be enough for the start.

But as I said the diffing stuff would also be great it just didn't come to mind when writing up this issue.