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.

Sign up for GitHub

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

Jump to bottom

[GeoMechanicsApplication] Serialization of all geo components #13054

Open

rfaasse opened this issue Jan 29, 2025 · 0 comments

Contributor

rfaasse commented Jan 29, 2025 •

edited

Loading

As developer, I would like to assess the impact of consistently serializing all geo components, such that I can estimate and plan a way to do this.

This investigation will entail:

Listing all C++ classes + members that will need serialization
Document a general strategy to start implementing serialization consistently
Create a unit test for the serialization of one class to get a blueprint and be able to estimate the effort for testing.
Document the possibilities of a strategy of how to make sure the serialization stays complete

rfaasse added this to Kratos Product Backlog

rfaasse converted this from a draft issue

indigocoral moved this from 📑 Product Backlog to 📋 Sprint Backlog in Kratos Product Backlog

indigocoral moved this from 📋 Sprint Backlog to 📑 Product Backlog in Kratos Product Backlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment