Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ErrorIfDataTooBig to BBH pipeline #6014

Merged
merged 1 commit into from
May 23, 2024

Conversation

knelli2
Copy link
Contributor

@knelli2 knelli2 commented May 21, 2024

Proposed changes

These variables and thresholds were used in SpEC.

Upgrade instructions

Code review checklist

  • The code is documented and the documentation renders correctly. Run
    make doc to generate the documentation locally into BUILD_DIR/docs/html.
    Then open index.html.
  • The code follows the stylistic and code quality guidelines listed in the
    code review guide.
  • The PR lists upgrade instructions and is labeled bugfix or
    new feature if appropriate.

Further comments

@knelli2 knelli2 added the small Only changes a few lines of code, does a rename or is otherwise quick to review label May 21, 2024
@knelli2 knelli2 added this to the BBH Pipeline Automation milestone May 21, 2024
Events:
- ErrorIfDataTooBig:
Threshold: 100
VariablesToCheck: [SpacetimeMetric]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: why not monitor the constraints during the ringdown? No need to hold up the PR aboutt this, I'm just surprised

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't actually know, but if I were to venture a guess it'd be because the constraint violations at t=Ringdown may be pretty large initially and then settle down quickly, so that initial violation could have been over the threshold? But then why not just delay the trigger? I'm not really sure. We should ask @markscheel at the BBH meeting today.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! I think SpEC actually monitors the constraints outside the horizons, but that's obviously harder to do.

@nilsvu nilsvu merged commit 12933c3 into sxs-collaboration:develop May 23, 2024
22 checks passed
isaaclegred pushed a commit to isaaclegred/spectre that referenced this pull request May 23, 2024
…too_big

Add ErrorIfDataTooBig to BBH pipeline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
small Only changes a few lines of code, does a rename or is otherwise quick to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants