Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: state machine programming
From: emmanuel_mayssat@lynceantech.com
To: Ralph Lange <Ralph.Lange@bessy.de>
Cc: EPICS tech-talk <tech-talk@aps.anl.gov>
Date: Sun, 30 May 2010 14:10:51 -0700
> Through exec() calls a state machine can call any program or script
> written in any language on your system. You find that too low level?!
> Could you explain your definition of high level in that context?

end_stations_protocol:
  align sample with beam
  detector_acquire_image
  move_grid
  rotate_sample
  detector_acquire_image
  move_grid
  insert_sample_3
  collect_data_set
  remove_sample_from_field_of view
  send_email_to_experimenter
  move_data_files_to_long_term_file_server

each command is drag-and-dropped by the experimenter (not a programmer)
sequence can be changed by the experimenter function of what he wants to do
He should be able to work independently of programmers

synchroton-turn-on:
  turn_on_injector_laser
  warm_up_modulator_1
  condition_magnet
  insert_screen_2
  start_injector_feedback  
  ...

Of course, each of those states can be further broken down and later refined
(I can easily see a state machine with 500+ states)
interpreted languages are better, no compilation needed 
+ you can program a sequence on the fly (no downtime required)

Can your sequencer to do that?

> I probably am over-interpreting your mails, but I do get the impression
> that you possibly are shopping for interesting solutions while not
> having nailed down your requirements, which IMHO should be done as early
> as possible in the process. 

For a software tool like a sequencer, I always consider flexibility ... a requirement.

-- 
Emmanuel

Replies:
Re: state machine programming Ralph Lange
References:
state machine programming emmanuel_mayssat
Re: state machine programming Ben Franksen
Re: state machine programming emmanuel_mayssat
Re: state machine programming Ralph Lange

Navigate by Date:
Prev: Re: state machine programming Eric Norum
Next: Re: state machine programming Claude Saunders
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: state machine programming Eric Norum
Next: Re: state machine programming Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·