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

Where to set supercycling length? #13

Closed
bradyrx opened this issue Oct 2, 2018 · 4 comments
Closed

Where to set supercycling length? #13

bradyrx opened this issue Oct 2, 2018 · 4 comments
Labels
question Further information is requested

Comments

@bradyrx
Copy link

bradyrx commented Oct 2, 2018

Per @pwolfram , super-cycling should already be available for particles.

What is the most straightforward way to set (and thus vary) the super-cycling time length?

I checked Registry_lagrangian_particle_tracking.xml and didn't find anything related to it. However, I did find the super-cycling section in mpas_ocn_lagrangian_particle_tracking.F.

@pwolfram
Copy link
Owner

pwolfram commented Oct 8, 2018

@bradyrx, this is somewhat obscured. Great question! You need to change

config_AM_lagrPartTrack_compute_interval = 'dt'

to something like

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = '0000_01:00:00'

See MPAS-Dev/MPAS#1484 for more detail. Does this make more sense?

@pwolfram pwolfram added the question Further information is requested label Oct 8, 2018
@bradyrx
Copy link
Author

bradyrx commented Oct 10, 2018

@pwolfram ,

Before I send off these test cases, I want to make sure I'm doing this right. (Note the linked PR is broken)

Does config_dt modify the global time step? I haven't set this explicitly, so it currently runs at whatever default is. I imagine then that compute_interval should be a multiple of config_dt?

Assuming this is all correct, would these test cases work?

no supercycling

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = 'dt'

1 hour supercycling

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = '0000_01:00:00'

4 hour supercycling

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = '0000_04:00:00'

8 hour supercycling

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = '0000_08:00:00'

@pwolfram
Copy link
Owner

@bradyrx, config_dt modifies the global time step. config_AM_lagrPartTrack_compute_interval is the LIGHT time step and this should be effectively n*config_dt, e.g.,

config_dt = '00:10:00'
config_AM_lagrPartTrack_compute_interval = '0000_01:00:00'

I believe the test cases should work, please let me know.

I've requested getting you access to MPAS-Dev/MPAS#1484

@pwolfram
Copy link
Owner

@bradyrx, please let me know when you are satisfied here and please feel free to close when this is the case. Thanks!

@bradyrx bradyrx closed this as completed Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants