LoadCase ids - keys in dictionary not same as keys of isubcase_name_map

[Vybornak2]

Hello,
I do not know, if this is intentional or not, but in some of the models I am getting different keys in these objects:

op2.op2_results.stress.ctira3_stress
op2.isubcase_name_map

is this expected behavior?

Actual output

ctira3_stress keys:
dict_keys([
    (1, 1, 1, 0, 0, '', ''),
    (2, 1, 1, 0, 0, '', ''),
    (3, 1, 1, 0, 0, '', ''),
    (4, 1, 1, 0, 0, '', ''),
    (5, 1, 1, 0, 0, '', ''),
    (6, 1, 1, 0, 0, '', ''),
    (31, 1, 1, 0, 0, '', ''),
    (32, 1, 1, 0, 0, '', ''),
    (33, 1, 1, 0, 0, '', ''),
    (34, 1, 1, 0, 0, '', ''),
    (35, 1, 1, 0, 0, '', ''),
    (36, 1, 1, 0, 0, '', ''),
    (37, 1, 1, 0, 0, '', ''),
    101
])

isubcase_name_map keys:
dict_keys([1, 2, 3, 4, 5, 6, 31, 32, 33, 34, 35, 36, 37, 101, 0])

[SteveDoyle2]

The documentation describes it. The result can’t be squashed though you results aren’t anything special…

…

On Mon, Oct 21, 2024 at 7:09 AM Vybornak2 ***@***.***> wrote: Hello, I do not know, if this is intentional or not, but in some of the models I am getting different keys in these objects: op2.op2_results.stress.ctira3_stress op2.isubcase_name_map is this expected behavior? Actual output ctira3_stress keys: dict_keys([ (1, 1, 1, 0, 0, '', ''), (2, 1, 1, 0, 0, '', ''), (3, 1, 1, 0, 0, '', ''), (4, 1, 1, 0, 0, '', ''), (5, 1, 1, 0, 0, '', ''), (6, 1, 1, 0, 0, '', ''), (31, 1, 1, 0, 0, '', ''), (32, 1, 1, 0, 0, '', ''), (33, 1, 1, 0, 0, '', ''), (34, 1, 1, 0, 0, '', ''), (35, 1, 1, 0, 0, '', ''), (36, 1, 1, 0, 0, '', ''), (37, 1, 1, 0, 0, '', ''), 101 ]) isubcase_name_map keys: dict_keys([1, 2, 3, 4, 5, 6, 31, 32, 33, 34, 35, 36, 37, 101, 0]) — Reply to this email directly, view it on GitHub <#805>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAICUWPDHLPO3YN2XRYHAZTZ4UDIPAVCNFSM6AAAAABQKIU7NSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYDENRYGE3TGOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Vybornak2]

Thank you for explanation, could you please by any chance provide this piece of documentation? Unfortunately I do not understand what these values in dictionary keys stands for. And I did not find related documentation. Even some brief information would help of course :).

Thank you kindly for your time and responses.

[SteveDoyle2]

Here you got. By default, everything is in this form. At the end of processing, the code attempts to squish the keys, but fails if there are multiple choices for a given subcase. https://pynastran-git.readthedocs.io/en/latest/quick_start/op2_pandas_multi_case.html#

…

On Mon, Oct 21, 2024 at 7:45 AM Vybornak2 ***@***.***> wrote: Thank you for explanation, could you please by any chance provide this piece of documentation? Unfortunately I do not understand what these values in dictionary keys stands for. And I did not find related documentation. Even some brief information would help of course :). Thank you kindly for your time and responses. — Reply to this email directly, view it on GitHub <#805 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAICUWMKGJIFRLI7F3BANL3Z4UHQRAVCNFSM6AAAAABQKIU7NSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWHA4TQMRQGA> . You are receiving this because you commented.Message ID: ***@***.***>

[Vybornak2]

Thank you :)