Closed b-r-hamilton closed 1 year ago
One more note: when I compare the globalmean_stepresponse
and my new stepresponse
, I don't compare the first timestep, because on my version of TMItransient, it was set to 0 after the fact. I see that that step has been removed in the new version of TMItransient, so I think that can be fixed in my current code (mostly writing this so I don't forget to change that)
Patch coverage: 94.73%
and project coverage change: +4.16%
:tada:
Comparison is base (
3c02ec0
) 41.11% compared to head (a505d08
) 45.28%. Report is 7 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This is my attempt at the code we discussed on Friday - I wrote a version of
globalmean_stepresponse
that takes in any type of analysis function that acts upon aField
, and wrote some tests to check that...stepresponse
) matches the output ofglobalmean_stepresponse
when the provided function ismean
stepresponse
function can be acted upon by theglobalmean_impulseresponse
. This works if the function provided tostepresponse
outputs a Float or a Vector (at each timestep), but does not work if the function outputs a Field because / isn't defined for a Field (also it seems like subtraction isn't working quite correctly for a Field, will write a MWE and post an issue on that when I get a chance)TMI.meanage
functionSome things that I didn't change but I think could be changed
globalmean_impulseresponse
could be renamed toimpulseresponse
because it's actually general enough to act upon any function (not just the global mean)Things that I'd like feedback on
stepresponse
? Right now it just takes in a Vector and unpacks it when it calls the evaluation function.