Open ambarb opened 4 years ago
note that pyCHX.Two_Time_Correlation_Functions.auto_two_Array
exists for frame and photon list data. The difference between this function and the one in chx_correlation
is that all possible lags are calculated (aka, brute force) in .pyCHX.Two_Time_Correlation_Functions.auto_two_Array
.
@yugangzhang @afluerasu Nexus XPCS results file is going with c-style arrays like you have in the new functions. For this function (either V1, V2 or skbeam), it is a f-style array, but the striding is short on the last index.
The function is broken here so if need to fix the function for your paper (multi-tau style two-time), then you may consider putting it in the "right shape"
pyCHX.chx_correlation.two_time_corr
don't edit unless needed now by CHXpyCHX._v2.chx_correlation.two_time_corr
is equivalent to what is found in sckit-beam. This function is unique in that it allows for a mult-tau - like calcuation of the two-time autocorrelation function.This function used in a CSX environment runs into a IndexError exception. All the other basic functions that are simliar between sckit-beam and pyCHX work as expected.
pyCHX._v2.chx_correlation.two_time_corr
.As discussed with @afluerasu, @yugangzhang 's code here is unique and is nice to keep. Paper pending. Note that xi-cam is using this function in skbeam.