Replies: 2 comments 5 replies
-
@bonfils2 - thanks for raising this. One quick question – the slope/intercept is pretty straightforward to calculate with existing libraries – it seems like the main addition would be the error metrics (if existing libraries don't do this). If I had x[time] and y[time, lat, lon], this function would return a slope[lat, lon], intercept[lat, lon], and p-value field [lat, lon]. Is that right? @tomvothecoder - can this discussion stay here or should it move to one of the feature discussion threads? |
Beta Was this translation helpful? Give feedback.
-
Just to get some updates: are we getting some progress in porting the |
Beta Was this translation helpful? Give feedback.
-
Hi all, I think that it would a great idea to convert (or plan to convert) the “genutil.statistics.linearregression” function from cdat (https://cdat.llnl.gov/documentation/utilities/utilities-2.html ) into xcdat. This function was very useful, easy to use on a 3D field, and loaded with options to compute the p-value with or without adjustment for standard error or critical t-value (a calculation that was implemented years ago in cdat after one of Ben Santer’s papers on that topic).
Beta Was this translation helpful? Give feedback.
All reactions