-
Notifications
You must be signed in to change notification settings - Fork 8
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
[telemac] added telemac support #176
base: master
Are you sure you want to change the base?
Conversation
let me battle with CI before starting reviewing it. There is no rush anyway |
I might have broken SCHISM tests with
So I don't mess up with the other CIs |
I think that:
|
I updated all the lock files. The CI seems to be happy. The telemac are marked as XPASS though. @tomsail did you expect them to fail for some reason? |
No sorry this is an error. I had put it at the beginning and forgot to take it off. Since the 4 tests (3 TELEMAC2D and 1 TOMAWAC) pass without problems I can remove it now. |
@tomsail if you have any updates on your local branch you can push them. We will need to rebase and we will need to regenerate lock files etc. |
@pmav99 let me know if you want me to rebase or if you want to check it too |
I still need to regroup the telemac options in parameters, and standardize them with the ones used for SCHISM. If you compare the specific parameters for SCHISM and TELEMAC in the same dictionary: model = {
...
"parameters": {
"dt": 400,
"rnday": 30,
"hotout": 0,
"ihot": 0,
"nspool": 9,
"ihfskip": 36,
"hotout_write": 108,
}, # FOR SCHISM
"tstep": 400, # for telemac
"meteo_input360": True, # if meteo files longitudes go from from 0 to 360
} For example here I'll correct this in the next days |
c970f85
to
8f14cb3
Compare
fail with python 3.12 is normal. |
PR is good to go. |
No description provided.