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

Fix bug in PreprocessCceWorldtube #6459

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

knelli2
Copy link
Contributor

@knelli2 knelli2 commented Jan 26, 2025

Proposed changes

Fixes #6450.

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

@@ -292,6 +292,9 @@ Here are some notes about the different options in the YAML input file:
simulation that provided the boundary dataset.
- `FixSpecNormalization` should always be `False` unless you are using a
particualy old version of SpEC
- `DescendingM` should always be `False`. This option is to maintain
Copy link
Contributor

Choose a reason for hiding this comment

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

This sentence could be confusing because DescendingM depends on how people provide their metric modal data. It can be True. I guess you are referring to the output Bondi modal data, which always have ascending m.

Copy link
Contributor Author

@knelli2 knelli2 Jan 28, 2025

Choose a reason for hiding this comment

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

Yes technically it can be true for metric modal data, but I think we want to encourage people to always have their data in ascending m order (unless it's from spec). Hence the strong language that it should always be False.

@@ -292,6 +292,9 @@ Here are some notes about the different options in the YAML input file:
simulation that provided the boundary dataset.
- `FixSpecNormalization` should always be `False` unless you are using a
particualy old version of SpEC
- `DescendingM` should always be `False`. This option is to maintain
compatibility with older versions of SpEC. Our
Copy link
Contributor

Choose a reason for hiding this comment

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

Current SpEC still dumps metric modal data with descending m (even though this option has been disabled in a default run). I would be more explicit here:

This option is to support metric modal data from SpEC.

@Sizheng-Ma
Copy link
Contributor

This executable can run properly.

The option FixSpecNormalization was incorrectly used to mean "file is
spec format" (aka descending m order). Adds a new option to the
Preprocess executable and input file to account for this
@knelli2 knelli2 force-pushed the preprocess_bug_fix branch from b771d8d to 4bc9457 Compare January 28, 2025 04:55
@Sizheng-Ma
Copy link
Contributor

Looks good.

@nilsdeppe nilsdeppe merged commit 51dbb85 into sxs-collaboration:develop Jan 28, 2025
20 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A bug in PreprocessCceWorldtube.cpp
3 participants