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

Gempy v2023.1.0 #796

Merged
merged 85 commits into from
Jun 20, 2023
Merged

Gempy v2023.1.0 #796

merged 85 commits into from
Jun 20, 2023

Conversation

Japhiolite
Copy link
Collaborator

Description

this PR includes changes by Andrew concerning switch to Aesara and multiple bugfixes

Relates to #706 #754

Checklist

  • My code follows the PEP 8 style guidelines.
  • My code uses type hinting for function and method arguments and return values.
  • My code contains descriptive and helpful docstrings
    which are formatted per the Google Python Style Guidelines.
  • I have created tests which entirely 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 and existing tests pass locally with my changes.

AndrewAnnex and others added 30 commits June 27, 2022 14:32
…y_v3

# Conflicts:
#	test/input_data/save_model/test_save_model/test_save_model_surfaces.csv
@Japhiolite Japhiolite requested a review from Leguark June 20, 2023 08:42
@Leguark Leguark merged commit f0fd684 into main Jun 20, 2023
2 of 4 checks passed
@Leguark Leguark deleted the gempy_v2023.1.0 branch June 25, 2024 07:23
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