| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Question about "indirect processing" mentioned in documentation for the SSEQ |
| From: | "Wang, Andrew via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | Mark Rivers <rivers at cars.uchicago.edu> |
| Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
| Date: | Sun, 7 Aug 2022 18:57:08 +0000 |
|
Hi Mark,
That helps clear up what WAIT does in SSEQ. I guess this has led me down a rabbit hole of trying to understand how asynchronous record processing described in Chapter 5 ties into the overall operation of SSEQ. I'll pose
my follow-up questions in another email to Tech-Talk.
From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Sunday, August 7, 2022 3:58 AM To: Wang, Andrew <wang126 at llnl.gov> Cc: Mooney, Tim M. <mooney at anl.gov>; EPICS tech-talk <tech-talk at aps.anl.gov> Subject: Re: Question about "indirect processing" mentioned in documentation for the SSEQ > I could
be wrong but does SSEQ only wait for "rec_1" to complete processing without waiting for "rec_2" before moving onto the other LNKn/DLYn/DOLn groups?
No, it will wait for rec_2 as well. The mechanism used waits for all records that are directly processed as a result of rec_1 processing.
Mark
Sent from my iPhone
On Aug 7, 2022, at 1:39 AM, Wang, Andrew via Tech-talk <tech-talk at aps.anl.gov> wrote:
|