Skip to content
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

Add contact result properties #1961

Merged
merged 3 commits into from
Dec 17, 2024
Merged

Conversation

janvonrickenbach
Copy link
Contributor

This is required so that force_elemental_nodal is correctly computed for contact results in pydpf-post. As far as I can see this dictionary is only used to lookup metadata on request and does not impact the available results directly. The scripting name is taken from dataProcessingDoc.html in the dpf core repo.

Copy link

codecov bot commented Dec 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.37%. Comparing base (af30b32) to head (f8f82d2).
Report is 3 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1961      +/-   ##
==========================================
- Coverage   88.42%   88.37%   -0.06%     
==========================================
  Files          89       89              
  Lines       10265    10251      -14     
==========================================
- Hits         9077     9059      -18     
- Misses       1188     1192       +4     

@janvonrickenbach janvonrickenbach merged commit 4fcf544 into master Dec 17, 2024
46 checks passed
@janvonrickenbach janvonrickenbach deleted the jvonrick/add_contact_results branch December 17, 2024 12:17
@PProfizi
Copy link
Contributor

PProfizi commented Jan 6, 2025

Hi @cbellot000 should this dictionary even exist? Shouldn't that information be given by the server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants