-
Notifications
You must be signed in to change notification settings - Fork 1
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 for pulling results and update warning message #369
Fix bug for pulling results and update warning message #369
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script worked as intended.
Warning message was updated.
Meshresults and barresults were pulled
@peterjamesnugent to confirm, the following actions are now queued:
There are 2 requests in the queue ahead of you. |
@peterjamesnugent to confirm, the following actions are now queued:
There are 1 requests in the queue ahead of you. |
The check |
@BHoMBot check ready-to-merge |
@peterjamesnugent to confirm, the following actions are now queued:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes work as intended, Changes approved.
Issues addressed by this PR
Closes #285
Test files
https://burohappold.sharepoint.com/:u:/s/BHoM/ESo_WOJCO0JPhMzd9EQr6PwBzgelLv1pb2NWXvIwQcg_KQ?e=BaB2gm
Changelog
BarResults
andMeshResults
were unable to pull whenCaseIds
were not provided due to a change fromint
tolong
MeshStress
that incorrectly referred toAxial strain
Additional comments
@StephennipBH the original issue related to Lusas 19 but I suspect they fixed the problem in a minor version update.