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.

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

max_columns_of_data ignored for simulations loaded from file #2420

Open
wpbonelli opened this issue Jan 18, 2025 · 1 comment
Open

max_columns_of_data ignored for simulations loaded from file #2420

wpbonelli opened this issue Jan 18, 2025 · 1 comment
Assignees
@wpbonelli
Labels
bug

Comments

@wpbonelli
Copy link
Member

Discussed in #2419

Flopy only respects MFSimulation.simulation_data.max_columns_of_data when the simulation is created from scratch, not when it is loaded.

This is rooted in some hairy logic involving two other (evidently user-facing, and not mutually exclusive) options max_columns_user_set and max_columns_auto_set. Are these necessary?

When one sets an option, flopy should respect it. If for some reason it can't, warn or raise an error
@wpbonelli wpbonelli added the bug label Jan 18, 2025
@wpbonelli wpbonelli self-assigned this Jan 18, 2025
@wpbonelli
Copy link
Member Author

relevant history in #1157

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

@wpbonelli wpbonelli

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wpbonelli