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

Remove TrainMode #47

Merged
merged 3 commits into from
Jun 19, 2024
Merged

Remove TrainMode #47

merged 3 commits into from
Jun 19, 2024

Conversation

dreamer2368
Copy link
Collaborator

@dreamer2368 dreamer2368 commented Jun 19, 2024

This PR partially addresses the issue #40 .

There were two TrainMode: UNIVERSAL that trains POD per each component; and INDIVIDUAL that trains POD per each subdomain.

While TrainMode::INDIVIDUAL may provide a little convenience in limited cases, it rather complicates the code implementation significantly, which is becoming a road block for adding more essential features. More fundamentally, TrainMode::INDIVIDUAL can be supported 100% from TrainMode::UNIVERSAL, thus being redundant.

Now TrainMode is removed from the entire code, simplifying some workflow.

@dreamer2368 dreamer2368 changed the title SubmeshTopologyHandler treats each subdomain as unique component. Remove TrainMode Jun 19, 2024
@dreamer2368 dreamer2368 marked this pull request as ready for review June 19, 2024 20:48
@dreamer2368 dreamer2368 merged commit 83597be into main Jun 19, 2024
2 checks passed
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.

1 participant