TSTEP1 read&write fix #851
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #850
There seems to be an issue with reading/writing TSTEP1 cards in the bdf. When reading a bdf, TSTEP1 instances are added to the model.tstepnls dictionary. This leads to issues further down the line as the code assumes all values in model.tstepnls are TSTEPNL cards. Parts of the code also assume that TSTEP1s are added to the model.tsteps dictionary, leading to conflicts.
The changes to the code now put TSTEP1 cards into the model.tsteps dictionary. I added a small test to verify that TSTEP1s are correctly read and written.