-
Notifications
You must be signed in to change notification settings - Fork 28
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
Update LFRic transformation signature? #2739
Comments
Thanks @sergisiso, I like this proposal a lot. Presumably, if we were dealing with a named invoke (i.e. a |
Yes, I didn't discuss it here but there are some scripts that use |
Yes, please - change that, I always hated the exposure of the PSy structure. For a while, maybe the FileContainer could provide a compatibility layer?
That would avoid the effort of having to all scripts when the next release comes out? These function could print a |
Ok, I will start implementing this |
Since we are talking about 3.0, one aspect that I wanted to discuss is if we should also update the LFRic scripts signature in this major release to use the root psyir node as scprit input argument (like in the generic transformation scripts).
Instead of:
it would be:
The main advantage is that it hides the PSy->Invokes->Invoke->InvokeSchedule structure:
Other minor advantages are:
psyir.walk(Routines)
instead ofinvoke.schedule.root.walk(Routines)
that we do now)What do @arporter @hiker @christophermaynard @TeranIvy think?
The text was updated successfully, but these errors were encountered: