The CONTACT keyword cards are using different variable names than those specified in the Dyna manual.

[MiteshLalwala]

🔍 Before submitting the issue

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

🐞 Description of the bug

All contact cards, except for CONTACT_AUTOMATIC_SINGLE_SURFACE, are using variable names that differ from the standard Dyna nomenclature.

For CONTACT_AUTOMATIC_SURFACE_TO_SURFACE (and most other contacts), the cards() method returns the following results. The variable names in the second and last rows do not match the Dyna manual.
[StandardCard:$# cid heading,
StandardCard:$# surfa surfb surfatyp surfbtyp saboxid sbboxid sapr sbpr,
StandardCard:$# fs fd dc vc vdc penchk bt dt,
StandardCard:$# sfsa sfsb sast sbst sfsat sfsbt fsf vsf]

In contrast, for CONTACT_AUTOMATIC_SINGLE_SURFACE, the cards() method returns results that align with the manual:
[StandardCard:$# cid heading,
StandardCard:$# ssid msid sstyp mstyp sboxid mboxid spr mpr,
StandardCard:$# fs fd dc vc vdc penchk bt dt,
StandardCard:$# sfs sfm sst mst sfst sfmt fsf vsf]

📝 Steps to reproduce

💻 Which operating system are you using?

Windows

📀 Which ANSYS version are you using?

n/a

🐍 Which Python version are you using?

3.12

📦 Installed packages

ansys-api-dyna==0.4.2
ansys-api-platform-instancemanagement==1.1.2
ansys-dpf-core==0.13.4
ansys-dyna-core==0.7.0
ansys-platform-instancemanagement==1.1.2
ansys-tools-path==0.7.1
anyio==4.8.0
appdirs==1.4.4
argon2-cffi==23.1.0
argon2-cffi-bindings==21.2.0
arrow==1.3.0
asttokens==3.0.0
async-lru==2.0.4
attrs==25.1.0
babel==2.16.0
beautifulsoup4==4.12.3
bleach==6.2.0
cachetools==5.5.1
certifi==2024.12.14
cffi==1.17.1
charset-normalizer==3.4.1
click==8.1.8
colorama==0.4.6
comm==0.2.2
contourpy==1.3.1
cycler==0.12.1
debugpy==1.8.12
decorator==5.1.1
defusedxml==0.7.1
executing==2.2.0
fastjsonschema==2.21.1
fonttools==4.55.7
fqdn==1.5.1
google-api-core==2.24.1
google-api-python-client==2.160.0
google-auth==2.38.0
google-auth-httplib2==0.2.0
googleapis-common-protos==1.66.0
grpcio==1.70.0
h11==0.14.0
hollerith==0.6.0
httpcore==1.0.7
httplib2==0.22.0
httpx==0.28.1
idna==3.10
importlib_metadata==8.6.1
ipykernel==6.29.5
ipython==8.31.0
ipywidgets==8.1.5
isoduration==20.11.0
jedi==0.19.2
Jinja2==3.1.5
json5==0.10.0
jsonpointer==3.0.0
jsonschema==4.23.0
jsonschema-specifications==2024.10.1
jupyter==1.1.1
jupyter-console==6.6.3
jupyter-events==0.11.0
jupyter-lsp==2.2.5
jupyter_client==8.6.3
jupyter_core==5.7.2
jupyter_server==2.15.0
jupyter_server_terminals==0.5.3
jupyterlab==4.3.4
jupyterlab_pygments==0.3.0
jupyterlab_server==2.27.3
jupyterlab_widgets==3.0.13
kiwisolver==1.4.8
MarkupSafe==3.0.2
matplotlib==3.10.0
matplotlib-inline==0.1.7
mistune==3.1.1
nbclient==0.10.2
nbconvert==7.16.6
nbformat==5.10.4
nest-asyncio==1.6.0
notebook==7.3.2
notebook_shim==0.2.4
numpy==2.2.2
overrides==7.7.0
packaging==24.2
pandas==2.2.3
pandocfilters==1.5.1
parso==0.8.4
pillow==11.1.0
platformdirs==4.3.6
pooch==1.8.2
prometheus_client==0.21.1
prompt_toolkit==3.0.50
proto-plus==1.26.0
protobuf==5.29.3
psutil==6.1.1
pure_eval==0.2.3
pyasn1==0.6.1
pyasn1_modules==0.4.1
pycparser==2.22
Pygments==2.19.1
pyparsing==3.2.1
python-dateutil==2.9.0.post0
python-json-logger==3.2.1
pytz==2024.2
pyvista==0.44.2
pywin32==308
pywinpty==2.0.14
PyYAML==6.0.2
pyzmq==26.2.0
referencing==0.36.2
requests==2.32.3
rfc3339-validator==0.1.4
rfc3986-validator==0.1.1
rpds-py==0.22.3
rsa==4.9
scooby==0.10.0
Send2Trash==1.8.3
setuptools==75.8.0
six==1.17.0
sniffio==1.3.1
soupsieve==2.6
stack-data==0.6.3
terminado==0.18.1
tinycss2==1.4.0
tornado==6.4.2
tqdm==4.67.1
traitlets==5.14.3
types-python-dateutil==2.9.0.20241206
typing_extensions==4.12.2
tzdata==2025.1
uri-template==1.3.0
uritemplate==4.1.1
urllib3==2.3.0
vtk==9.3.1
wcwidth==0.2.13
webcolors==24.11.1
webencodings==0.5.1
websocket-client==1.8.0
wheel==0.45.1
widgetsnbextension==4.0.13
zipp==3.21.0

[kanthadya]

@MiteshLalwala, we are moving away from using words like slave and master in our keyword definitions and hence you will see surfa, surfb ( surface A, surface B) instead of ssid, msid (slave surface ID and master surface ID). I think slowly all cards will be migrated. In the mean time its better to check for both properties in your scripts

[MiteshLalwala]

@kanthadya, Okay. In that case, can we update the definition for CONTACT_AUTOMATIC_SINGLE_SURFACE to match with the other contact cards?

[kanthadya]

Yes thats correct

[koubaa]

@kanthadya could you please let me know when the manual is up-to-date so I can regenerate the keywords?