Skip to content

Conversation

@Leguark
Copy link
Member

@Leguark Leguark commented May 10, 2025

Description

Changed InterpolationOptions constructor to use a factory method from_args() instead of direct instantiation. This change affects multiple files where InterpolationOptions was being created directly. Added a new test file test_serialize_model.py to verify serialization and deserialization of InterpolationOptions objects. Also expanded the development log with detailed notes about model saving requirements.

Relates to #serialization-support

Checklist

  • My code uses type hinting for function and method arguments and return values.
  • I have created tests which cover my code.
  • The test code either 1. demonstrates at least one valuable use case (e.g. integration tests)
    or 2. verifies that outputs are as expected for given inputs (e.g. unit tests).
  • New tests pass locally with my changes.

Copy link
Member Author

Leguark commented May 10, 2025

Leguark added 2 commits May 12, 2025 08:30
Replaced direct instantiation of `InterpolationOptions` with the `from_args` class method across multiple modules and tests for consistency and improved clarity. Updated related examples and fixtures to align with this change.
Added validation logic for `kernel_function` fields to ensure proper deserialization from string inputs to enums. Enhanced default JSON serialization by including additional encoders and adjusted relevant field exclusions.
Upgraded gempy_engine dependency to the latest version for improved functionality and bug fixes. Ensure compatibility by updating local environments accordingly.
@Leguark Leguark changed the title [WIP] Getting the first example of InterpolationOptions serializable [ENH] Replace InterpolationOptions constructor with from_args method for serialization May 14, 2025
@Leguark Leguark marked this pull request as ready for review May 14, 2025 11:42
@graphite-app graphite-app bot added the gempy 3 Will come with the next major update label May 14, 2025
@graphite-app
Copy link
Contributor

graphite-app bot commented May 14, 2025

Graphite Automations

"Add gempy label" took an action on this PR • (05/14/25)

1 label was added to this PR based on Miguel de la Varga's automation.

Relax version constraints to include development versions. This ensures compatibility with the latest updates while avoiding breaking changes in the next major release.
Copy link
Member Author

Leguark commented May 19, 2025

Merge activity

  • May 19, 7:20 AM EDT: A user started a stack merge that includes this pull request via Graphite.
  • May 19, 7:24 AM EDT: Graphite couldn't merge this PR because it failed for an unknown reason.
  • May 19, 7:25 AM EDT: A user started a stack merge that includes this pull request via Graphite.
  • May 19, 7:28 AM EDT: Graphite couldn't merge this PR because it failed for an unknown reason.
  • May 19, 7:29 AM EDT: A user started a stack merge that includes this pull request via Graphite.

@Leguark Leguark merged commit 57072cb into main May 19, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gempy 3 Will come with the next major update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants