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

[MPM] Change application name #12011

Merged
merged 56 commits into from
Mar 13, 2024
Merged

[MPM] Change application name #12011

merged 56 commits into from
Mar 13, 2024

Conversation

ncrescenzio
Copy link
Contributor

This PR changes the name of the application implementing the Material Point Method from ParticleMechanicsApplication to MPMApplication

@antonialarese
@KratosMultiphysics/technical-committee

Copy link
Member

@philbucher philbucher left a comment

Choose a reason for hiding this comment

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

I dont have any objections, but I strongly recommend to add backward compatibility
Otherwise you are breaking every single existing case out there
And speaking from experience, others are not happy abt this ;)

@@ -78,13 +78,13 @@
}]
},
"print_output_process" : [{
"python_module" : "particle_json_output_process",
"kratos_module" : "KratosMultiphysics.ParticleMechanicsApplication",
"python_module" : "mpm_json_output_process",
Copy link
Member

Choose a reason for hiding this comment

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

e.g. this is not backward compatible

{
"type" : "solver_wrappers.kratos.particle_mechanics_dirichlet_wrapper",
"type" : "solver_wrappers.kratos.mpm_dirichlet_wrapper",
Copy link
Member

Choose a reason for hiding this comment

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

same

@ncrescenzio
Copy link
Contributor Author

@philbucher so should I duplicate all the python files, keeping both the one with the old name and the new one?

@philbucher
Copy link
Member

I would add wrappers with the old name, that create an object of the new type.
There you can issue deprecation warnings so that users can update at their own pace (maybe include a date in the message)

Copy link
Member

@philbucher philbucher left a comment

Choose a reason for hiding this comment

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

no objections, looking good from my side.

I am still a bit worried about the backward compatibility, seems like many things have changed

My suggestion is to only update some tests, and leave others with the old input. This way you are sure that the backward compatibility that you implement is working properly

@ncrescenzio
Copy link
Contributor Author

@philbucher as you suggested, I also added the wrappers with the old names of python processes and left the old inputs in the tests.

@philbucher
Copy link
Member

cool, looks good from my side

I leave the approval to an active user of the App, maybe @VeronikaSinger ?

@VeronikaSinger
Copy link
Contributor

Thanks @philbucher for the review and thanks @ncrescenzio for the renaming of the application. I approve

@ncrescenzio
Copy link
Contributor Author

Thanks @philbucher @VeronikaSinger!

@ncrescenzio ncrescenzio merged commit 0f83a7f into master Mar 13, 2024
17 of 21 checks passed
@ncrescenzio ncrescenzio deleted the mpm/change-application-name branch March 13, 2024 09:39
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.

4 participants