Re: [ARTIQ] changing "experiment" terminology

[Sebastien Bourdeauducq]

On Friday, December 11, 2015 04:21 PM, Robert Jördens wrote:

I don't follow. Even the most complicated experiment is just a bunch
of DDS frequency settings, TTL line settings, rotating wall changes
and a bit of gated edge counting.


My thinking is that the word "experiment" evokes something more advanced 
than a routine clearing of a Numpy array, one DDS frequency setting for 
debugging/setup purposes, or even a temperature/laser power control loop 
used in housekeeping, etc.

___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq

Re: [ARTIQ] changing "experiment" terminology

[Sebastien Bourdeauducq]

On Friday, December 11, 2015 04:36 PM, Sebastien Bourdeauducq wrote:

My thinking is that the word "experiment" evokes something more advanced


Or more precisely: something that produces science results directly.
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq

Re: [ARTIQ] changing "experiment" terminology

[Robert Jördens]

On Fri, Dec 11, 2015 at 1:37 AM, Sebastien Bourdeauducq  wrote:
> On Friday, December 11, 2015 04:36 PM, Sebastien Bourdeauducq wrote:
>> My thinking is that the word "experiment" evokes something more advanced
> Or more precisely: something that produces science results directly.

That is not a very useful requirement.
What about an experiment that is aborted and thus does not produce any
results, science or not?

-- 
Robert Jordens.
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq

Re: [ARTIQ] changing "experiment" terminology

[Sebastien Bourdeauducq]

On Friday, December 11, 2015 01:21 PM, Robert Jördens wrote:

The three items you list above are exactly what an experiment would
do. Why would setting DDS frequencies, configuring the rotating wall
clearing/building a reference histogram_not_  be something done in an
Experiment?


They are each a separate, stand-alone program. One program to set DDS 
frequencies (replacement for DDS bus injection). One program to clear 
the reference histogram (typically associated with a shortcut). One 
program to configure the rotating wall (Joe has one that does only this 
AFAIK). I think an "experiment" should be more complicated than those 
simple, housekeeping/debugging tasks.


___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq

Re: [ARTIQ] changing "experiment" terminology

[Robert Jördens]

On Thu, Dec 10, 2015 at 8:32 PM, Sebastien Bourdeauducq  wrote:
> a number of "experiments" used with ARTIQ are actually not experiments at
> all: they are small programs that e.g. clear the reference histogram, set
> DDS frequencies, configure the rotating wall, etc.
>
> I think we should come up with a better term for those. Peter proposes
> "applications" and I'm ok with that. Any comments?

I don't think Application is an improvement over Experiment. After
all, most of them are certainly not what I would call an Application.
The three items you list above are exactly what an experiment would
do. Why would setting DDS frequencies, configuring the rotating wall
clearing/building a reference histogram _not_ be something done in an
Experiment?
If you really need a new name, Program seems correct but Experiment is
IMHO still better. It does not collide with existing terminology
(artiq_gui seems to be an Application, artiq_run might be a Program by
some definition).

-- 
Robert Jordens.
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq