Support for ETBLOCK

[duhd1993]

🔍 Before submitting the issue

• [X] I have searched among the existing issues
• [X] I am using a Python virtual environment

🐞 Description of the bug

As described here, https://discuss.ansys.com/discussion/2365/unable-to-read-cdb-file-in-pyprimemesh, Ansys 2023 added ETBLOCK, and is using it in favour of ET

📝 Steps to reproduce

Cannot read cdb file generated by Ansys APDL 2023

💻 Which operating system are you using?

Linux

📀 Which ANSYS version are you using?

R2023

🐍 Which Python version are you using?

3.7

📦 Installed packages

NA

[akaszynski]

Addressed in https://github.com/akaszynski/mapdl-archive/pull/9

@germa89, please note that repository is effectively a fork of this one that removes the binary result reader and focuses on reading in blocked archive files written from either Mechanical or APDL.

I didn't feel comfortable removing that feature in this library as the binary reader is still used, and the refactor of the archive writer was quite significant.

[germa89]

Personally, I think this is fine.

Any future plants to re-merge it back? Feel free to ping me for assistance then.

[akaszynski]

Any future plants to re-merge it back? Feel free to ping me for assistance then.

I don't mind pushing the changes back to this repository time permitting.

BTW, inspecting ETBLOCK reveals

- `Field 1` - A user selected element type identifier.
- `Field 2` - Identifier number for the element (e.g. 186 for SOLID186)
- `Fields 3-20` - KEYOPT values (ranging from 1 to 18) specific to the given element type in field 2.