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

How to run models with ats using modflowapi #24

Open
hjia1005 opened this issue Jul 6, 2023 · 0 comments
Open

How to run models with ats using modflowapi #24

hjia1005 opened this issue Jul 6, 2023 · 0 comments

Comments

@hjia1005
Copy link

hjia1005 commented Jul 6, 2023

I used modflowapi to run my current models, just experimenting at this stage, not updating anything. My callback_function is simple as below:

def callback_function(sim, callback_step):
    if callback_step == Callbacks.initialize:
        print(sim.models)
        
    if callback_step == Callbacks.stress_period_start:
        print('start of stress period') 
        
    if callback_step == Callbacks.stress_period_end:
        print(f'end of stress period')
        
    if callback_step == Callbacks.timestep_start:
        print(f"start of time step")
        
    if callback_step == Callbacks.timestep_end:
        print(f"end of time step")

Initially, it was successful with some, but not with others. Then (actually after many runs) I realized the issue was with ats. If I deactivate ats, every model runs properly, even the very complex ones. It is quite amazing. However, in the function run_simulation , I see the 'ats' option.

image

I would like to ask how ats works with modflowapi?

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

No branches or pull requests

1 participant