Code hacking

[dkokron]

I've been doing some performance profiling of a NOAA application called HAFS. The profiling report is pointing me to a file that gets generated during the build (see below). I'd like to influence the content of this file to see if I can reduce execution time. I have searched the source tree and reviewed various log files. Everything points to framework/scripts/ccpp_prebuild.py being my starting point, but the trail goes dark after that. Does anyone have a short tutorial on how to hack the file generation machinery?

build_fv3_32bit/FV3/ccpp/physics/ccpp_FV3_HAFS_v1_gfdlmp_tedmf_nonsst_time_vary_cap.F90

[climbfuji]

If you “hack” your build system to suppress calling ccpp_prebuild.py and don’t clean before/after building, then you can manually modify the auto-generated files to insert the profiling statements.

…

On Mar 10, 2023, at 12:52 PM, dkokron ***@***.***> wrote: I've been doing some performance profiling of a NOAA application called HAFS. The profiling report is pointing me to a file that gets generated during the build (see below). I'd like to influence the content of this file to see if I can reduce execution time. I have searched the source tree and reviewed various log files. Everything points to framework/scripts/ccpp_prebuild.py being my starting point, but the trail goes dark after that. Does anyone have a short tutorial on how to hack the file generation machinery? build_fv3_32bit/FV3/ccpp/physics/ccpp_FV3_HAFS_v1_gfdlmp_tedmf_nonsst_time_vary_cap.F90 — Reply to this email directly, view it on GitHub <#464>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5C2RNS4YUYCUPYFUPCIK3W3OA7VANCNFSM6AAAAAAVW4K73E>. You are receiving this because you are subscribed to this thread.

[dkokron]

Thank for the tips. I'm doing more than inserting profiling statements into the auto-generated code. I'll be modifying user code. The question pertains to how to get those changes to be auto-generated in the future.

[climbfuji]

For this you'll have to peruse the ccpp_prebuild code itself. There is no documentation for it. You'll probably want to start with ccpp_prebuild.py, which in the main routine calls individual steps of the process one by one. You can fast-forward to where it goes to generate the caps and the API (all that code is in mkstatic.py). mkstatic.py uses a mixture of templates (at the top of the API, suite and group classes) with variable substitutions, and additional code generated in between by the class routines.

[dkokron]

I see. Thank you.