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

one-degree tripole support #186

Open
dabail10 opened this issue Sep 18, 2018 · 13 comments
Open

one-degree tripole support #186

dabail10 opened this issue Sep 18, 2018 · 13 comments

Comments

@dabail10
Copy link
Contributor

I didn't see an issue here already, but this was on a to do list somewhere. I looked into what it would take and the main problem I see is that the forcing would have to be remapped onto the tx1 grid. We have a tool somewhere that does this right? I was thinking the COREII forcing.

@dabail10 dabail10 self-assigned this Sep 18, 2018
@eclare108213
Copy link
Contributor

I wrote to Ed Blockley and he responded this morning with a file containing a one-degree tripoleT grid and related info. I'm not sure whether we would need to remap 'realistic' data, since we're mainly testing the boundary conditions, not the physics. If it's easy, then do it...

@eclare108213
Copy link
Contributor

@dabail10 has the grid info, @rallard77 has JRA55 forcing... have a chat!

@dabail10
Copy link
Contributor Author

So, we finally put 2 and 2 together here and David Hebert got me the JRA55 on the tx1 grid as well as an initial state for this. We need to deal with the space issues for the forcing before I can add these.

@dabail10 dabail10 mentioned this issue Apr 14, 2020
16 tasks
@dabail10
Copy link
Contributor Author

Part of this is resolved. I need to add the data to Zenodo.

@dabail10
Copy link
Contributor Author

I also have two initial files here. One that has used bilinear interpolation, and the other that has used nearest neighbor. @daveh150 did you give me these? Have you tested the code with either?

@daveh150
Copy link
Contributor

daveh150 commented May 12, 2020 via email

@rallard77
Copy link
Contributor

rallard77 commented May 12, 2020 via email

@dabail10
Copy link
Contributor Author

I will test both and make sure they work. I guess the bilinear is probably the preferred way to start the model?

@dabail10
Copy link
Contributor Author

Ok. The nearest neighbor file is a problem. It aborts in the thermo right away:
(init_vertical_profile)Starting thermo, zTsn > Tmax
(init_vertical_profile)zTsn= 158.567848688701
(init_vertical_profile)Tmax= 2.428923153931408E-003
(init_vertical_profile)zqsn -18516.5183268217 -110220000.000000
110201483.481673
(icepack_warnings_setabort) T :file icepack_therm_vertical.F90 :line
817
(init_vertical_profile) init_vertical_profile: Starting thermo, zTsn > Tmax

@dabail10
Copy link
Contributor Author

Same problem with the nearest neighbor file. I will put this on hold for a bit. I will run a 10 year run with the tx1 grid and the JRA55 forcing from the default initialization. Then I will use this restart as the default.

@daveh150
Copy link
Contributor

daveh150 commented May 12, 2020 via email

@apcraig
Copy link
Contributor

apcraig commented Mar 23, 2021

I think we can close this? tx1 is being tested regularly with the JRA55 forcing. And the tx1 forcing dataset is on zenodo,

https://zenodo.org/record/4495070#.YFoqkeZlDpk

@dabail10
Copy link
Contributor Author

The idea was also to add an initial file. We're almost there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants