Skip to content

[GeoMechanicsApplication] Use standard import mechanism for staged analyses#13707

Merged
markelov208 merged 6 commits intomasterfrom
geo/13408-standard-import-mechanism
Aug 15, 2025
Merged

[GeoMechanicsApplication] Use standard import mechanism for staged analyses#13707
markelov208 merged 6 commits intomasterfrom
geo/13408-standard-import-mechanism

Conversation

@markelov208
Copy link
Contributor

@markelov208 markelov208 commented Aug 7, 2025

📝 Description
A brief description of the PR.

Please mark the PR with appropriate tags:

  • replaced "input_type": "mdpa" in all ProjectParameters_stage[2,3,...].json on "input_type": "use_input_model_part"

@markelov208 markelov208 self-assigned this Aug 7, 2025
@markelov208 markelov208 requested a review from a team as a code owner August 7, 2025 18:14
Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up! I think it's almost ready to go, I found some mdpa files that can probably be removed since they're not referenced anymore.

Also: Do you know what the reason is that you had to revert the one in test_nodal_hydraulic_head?

@markelov208
Copy link
Contributor Author

markelov208 commented Aug 11, 2025

Thanks for picking this up! I think it's almost ready to go, I found some mdpa files that can probably be removed since they're not referenced anymore.

Also: Do you know what the reason is that you had to revert the one in test_nodal_hydraulic_head?

Hi Richard, many thanks for the review. You are absolutely right and some mdpa files can be removed and removed now. Concerning the 'test_nodal_hydraulic_head', as far as I understand this is a parametrised test and not staged test. Kind regards

@markelov208 markelov208 requested a review from rfaasse August 11, 2025 16:18
Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for processing the review comments and removing the redundant mdpa files. I think you removed a bit too much from the project param settings though, so if you could revert that part (see also my comment for more clarity), we are ready to merge this 👍

"solver_type": "U_Pw",
"model_part_name": "PorousDomain",
"domain_size": 2,
"model_import_settings": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you revert the removal of the settings in the json? We still need the model_import_settings with the use_import_model_part (like you changed it before), it's just that we don't need the mdpa file itself anymore. This also holds for the other project params where you deleted this.

The tests still pass, that's true, but the reason we want to have use_input_model_part as input type, is to be able to simplify some code in the geomechanicsanalysis later (related to the orchestrator based workflow), so we still need it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Unfortunately, model_import_settings cannot be empty, so "input_type": "mdpa" is added. mdpa can be omitted.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As in the other parameter files, the input_type should be put to use_input_model_part, such that the importer knows not to search for an mdpa file. Sorry if that wasn't clear (see next comment for clarity). The same holds for the other ones.

Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor thing left, sorry for the confusion here, I tried to be more clear in this review

"solver_type": "U_Pw",
"model_part_name": "PorousDomain",
"domain_size": 2,
"model_import_settings": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As in the other parameter files, the input_type should be put to use_input_model_part, such that the importer knows not to search for an mdpa file. Sorry if that wasn't clear (see next comment for clarity). The same holds for the other ones.

Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks, ready to go!

@markelov208 markelov208 merged commit ca63a81 into master Aug 15, 2025
10 checks passed
@markelov208 markelov208 deleted the geo/13408-standard-import-mechanism branch August 15, 2025 13:42
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.

[GeoMechanicsApplication] Use standard import mechanism for staged analyses

2 participants