Repository navigation
Conversation
cquiroz
reviewed
Oct 7, 2026
| readRetries = 1 | ||
| ioTimeout = 5 seconds | ||
| # Delay after Flamingos2 reports observe completion. Use 0 seconds to skip it | ||
| f2PaddingDelay = 10 seconds |
Contributor
There was a problem hiding this comment.
why is the delay in prod different than on dev?
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
jluhrs
force-pushed
the
rel_4892_adjust_f2_end_delay
branch
from
October 7, 2026 17:52
aa2b76e to
c2f4738
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applie
2DCF
d while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The time delay after FLAMINGOS-2 observations is now configurable from app.conf file.
As a bit of context, sometimes F2 keywords have wrong values, which match the next observation. The current hypothesis is that F2 notifies the end of the observation before witting the affected keywords, or even before capturing the current values. As Seqexec applies the next configuration almost immediately, is it possible that by the time F2 captures the values they are already changed. A 10 seconds delay between the end-of-observation notification and the next step configuration proved to solve the problem. Now we are trying to figure out if a smaller delay would work.