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

fixes #304 #370

Merged
merged 1 commit into from
Mar 3, 2025
Merged

fixes #304 #370

merged 1 commit into from
Mar 3, 2025

Conversation

o-smirnov
Copy link
Member

@JSKenyon would you please test with your basic selfcal workflow, changing info to self? I've tested with TRON and it seems to work, but there the use of info is minimal.

@o-smirnov o-smirnov requested a review from JSKenyon March 2, 2025 10:13
Copy link
Collaborator

@JSKenyon JSKenyon left a comment

Choose a reason for hiding this comment

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

Looks uncontroversial.

@o-smirnov
Copy link
Member Author

As long as it works. My only mild concern was having two namespaces somehow become proper duplicates. The way I assign them to SubstitutionNS, info and self do refer to the same object, and we don't do deep copies anywhere, so this shouldn't be an issue.

@o-smirnov o-smirnov merged commit 7676505 into master Mar 3, 2025
4 checks passed
@o-smirnov o-smirnov deleted the issue-304 branch March 3, 2025 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants