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 orthotropic material properties for use in funtofem+caps2tacs #254

Merged
merged 1 commit into from
Sep 28, 2023

Conversation

sean-engelstad
Copy link
Contributor

  • I've added orthotropic materials to the caps2tacs materials module.
  • Marshall and I added MAT4, MAT5 thermal cards into the tacsAIM which have material IDs that are 100 + the material IDs for the elastic cards (so they are tied together with that property group).
  • We can now specify thermal properties for orthotropic materials in caps2tacs => funtofem (namely kappa1 - kappa3, and specific_heat)
  • Question: Can we add the material ID = 100 + mid checks into the default pytacs callback too? This would allow us to specify thermal properties from caps2tacs into pure TACS as well. @bburke38 and I think this would be a good idea, but what do you think @timryanb

@sean-engelstad sean-engelstad added the enhancement New feature or request label Sep 28, 2023
@timryanb
Copy link
Collaborator

timryanb commented Sep 28, 2023

I'd prefer to leave the matID + 100 procedure outside of pyTACS. I want to preserve NASTRAN compatibility there. I'd be concerned about cases with large numbers of material cards in the BDF file where two unrelated mat cards unintentionally get read together. I think the standard is fine to use in caps2tacs, since it's a more specific use-case.

@sean-engelstad sean-engelstad merged commit 243b7be into smdogroup:master Sep 28, 2023
5 checks passed
@sean-engelstad sean-engelstad deleted the orthotropic branch September 28, 2023 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants