Skip to content

[ENH] Add interpolation options type selection and improve documentation | GEN-12034 #1020

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 7 commits into from
May 3, 2025

Conversation

Leguark
Copy link
Member

@Leguark Leguark commented May 2, 2025

Description

Enhanced the create_geomodel function to support different interpolation options types through a new enum-based approach. Added InterpolationOptionsType enum with DENSE_GRID and OCTREE options to allow users to explicitly choose their preferred interpolation method. The function now dynamically creates appropriate interpolation options based on the selected type.

Updated the function documentation to be more comprehensive, explaining the purpose and behavior of each parameter in detail. Removed the test_QA directory and updated dependencies to use the latest versions of gempy_engine (~2025.1.1) and gempy_viewer (~2025.1.0).

Modified the marching cubes test to use the new dense grid options initialization method instead of manually configuring interpolation options.

Relates to #interpolation-options-enhancement

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.

@Leguark Leguark mentioned this pull request May 2, 2025
4 tasks
Copy link
Member Author

Leguark commented May 2, 2025

@Leguark Leguark changed the title [TEST] Adding tests for options preset [ENH] Add interpolation options type selection and improve documentation May 2, 2025
@Leguark Leguark marked this pull request as ready for review May 2, 2025 10:19
@graphite-app graphite-app bot added the gempy 3 Will come with the next major update label May 2, 2025
Copy link

graphite-app bot commented May 2, 2025

Graphite Automations

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

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

@Leguark Leguark changed the title [ENH] Add interpolation options type selection and improve documentation [ENH] Add interpolation options type selection and improve documentation | GEN-12034 May 2, 2025
@Leguark Leguark changed the base branch from outlier_issue to graphite-base/1020 May 2, 2025 10:25
@graphite-app graphite-app bot changed the base branch from graphite-base/1020 to main May 2, 2025 10:26
Leguark added 3 commits May 2, 2025 12:30
Replaces hardcoded interpolation initialization with an enum-based system (`InterpolationOptionsType`) for flexibility. Removes unused tests and updates dependencies to `gempy_engine~=2025.1`.
Leguark added 4 commits May 2, 2025 16:00
Updated the gempy_viewer dependency to ensure compatibility by using an exact version specification. This helps to avoid potential issues arising from unintended updates.
This update fixes a potential issue in the gempy_engine dependency. Ensures compatibility and correctness with the latest patched version.
Copy link
Member Author

Leguark commented May 3, 2025

Merge activity

  • May 3, 3:48 AM EDT: A user started a stack merge that includes this pull request via Graphite.
  • May 3, 3:50 AM EDT: Graphite couldn't merge this PR because it failed for an unknown reason.
  • May 3, 3:51 AM EDT: A user started a stack merge that includes this pull request via Graphite.

@Leguark Leguark merged commit 717ca35 into main May 3, 2025
2 checks passed
@Leguark Leguark linked an issue May 3, 2025 that may be closed by this pull request
# for free to join this conversation on GitHub. Already have an account? # 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.

Fix outliers
1 participant