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

run simulations #9

Merged
merged 2 commits into from
Aug 31, 2024
Merged

run simulations #9

merged 2 commits into from
Aug 31, 2024

Conversation

tixianw
Copy link
Collaborator

@tixianw tixianw commented Aug 31, 2024

You can probably just delete the branch. Nothing changed much except small modification for running simulations.

Copy link
Owner

@hanson-hschang hanson-hschang left a comment

Choose a reason for hiding this comment

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

What does the +11 mean in the collect_br2_data.py?

@hanson-hschang
Copy link
Owner

@tixianw There is a conflict in merging. Once you resolve the conflict. You can merge and delete the branch.

@tixianw
Copy link
Collaborator Author

tixianw commented Aug 31, 2024

What does the +11 mean in the collect_br2_data.py?

For clockwise twist, there are 11 simulations. It's another 11 simulations but put twist input in counterclockwise twist.

@hanson-hschang hanson-hschang merged commit 03e53fc into main Aug 31, 2024
1 check failed
@hanson-hschang hanson-hschang deleted the feat/collect_data branch August 31, 2024 15:35
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