Am Wed, 22 Nov 2023 10:07:01 +0100
schrieb Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>:
> I would probably go for the database solution, because of the full
> transparency and online modifiable functionality (good when developing).
This sounds indeed like what I would have chosen based on your
description.
So my description was biased. Yep, that happens.
Small database is a good approach for your size of problem. On the same IOC is good, as you don't have to handle disconnects.
The seq record is nice for short delays, but it doesn't handle long delays well (that need things like cancel, retrigger, progress bar).
> In case you eventually have a generic database solution, please consider
> posting it to https://github.com/epics-docs/database-examples, which is a
> good place to share such patterns.
Thanks for the pointers. Looks like a simple counter is already there.
...
How would "posting" something work there? Just open an new issue, come up with a pull request...?
Open a PR, yes. (A separate issue is not really necessary when adding.)
Cheers,
~Ralph
