-
Notifications
You must be signed in to change notification settings - Fork 11
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
get_grid_sizerequested tile index 1 is out of bounds (1:0) when running model config produced with regional-mom6 #189
Comments
this is a weird one! Never seen it before. My suspicion is that it's to do with the 'ntiles' dimension in the bathymetry file, but that could be totally wrong. I don't understand what ntiles does, just that MOM seemed to want it. @angus-g or @micaeljtoliveira might know. Which executable are you using? Can you confirm that your executable works with the output of the demo notebook? |
Hi Ash, Tried using the demo notebook config and I'm getting the same error. SO, most probably something to do with my MOM6 installation... Might try recompiling it after checking if some of the cpp flags and similar are wrong (hybrid of your setup-mom6 ninja stuff for NCI combined with what sense I could make from the default MOM6 ubuntu install...). |
Hi @croachutas The workflow on Setonix is a little different to Gadi, but we can work you through it. Happy to chat at AMSA or otherwise. Let me know. |
Hi Chris, |
Since it looks like the error isn't tied to the package but the specific MOM6 install (@croachutas confirmed that the example notebook doesn't work) I'll close this issue |
Hi,
I recently downloaded the current version of regional-mom6, got it working on my workstation and setup a test high resolution config for south eastern Tasmania. I've looked at the resulting input files and they look correct but when I go to run with a MOM6 program built with sis2 coupling (tested and working on several of the MOM6 examples) I get the following output:
I'm unclear on what this get_grid_sizerequested error means and if it's something wrong with MOM6 or something wrong with the config produced with regional-mom6.
Any ideas?
The text was updated successfully, but these errors were encountered: