[MSNoise] Fwd: Re: Stuck in Compute_cc step

[Thomas Lecocq]

Sébastien,

(FW to the ML, as this could be useful for many):

Le 13/05/2014 16:10, Sébastien Carniato a écrit :
> Hi Thomas,
> thank you for your quick answer !
>
> Indeed, it works when I use only Decimate. I have to check again, but 
> I think indeed that my data stream are using the same sample rate.
You can also check that with the SQLiteManager (group data_availability 
by "sampling_rate")
> I have a bench of other questions :
>
> *Question 1 : *So now that compute_cc works :), _I would like to know 
> if the correlations computed are stored_, and in that case where ? I 
> put the output folder on my desk with the configurator, but nothing  
> was created so far...
If you set "keep_all" to "Y", the 30 minutes CC are stored in the 
CROSS_CORRELATION folder, named "hh_mm.cc", and these are miniseed files 
(I know, bad naming, this is going to change in the future).
>
> *Question 2 :* My data are not continuous. Indeed they are a lot of 
> days missing, and the maximum length of recording is one day and a 
> half. _Is it a problem for running MSNoise_ ?
Well, MSNoise does correlate M minutes (30 minutes by default) windows, 
if data is missing, the CC will be corrupted (NaN or infs) and will not 
be stored. So, normally no problem. BUT, expect results to be quite 
strange if you have ony like 20% of the day filled with good data.
>
> *Question 3 :* The only way to get a filter is to create one with the 
> sqlite manager. Is it normal ?
No, there is a bug in the Configurator which doesn't show any empty line.
> *
> *
> *Question 4 : *and the last one : Now when I launch compute_cc, i get 
> the error :
>
> 2014-05-13 16:04:21,314 [INFO] *** Starting: Compute CC ***
> 2014-05-13 16:04:21,354 [INFO] Will compute ZZ
> 2014-05-13 16:04:21,479 [INFO] New CC Job: 2011-01-18 (6 pairs with 3 
> stations)
> AN.LF1:AN.LF1
> 2014-05-13 16:04:21,595 [DEBUG] Processing pair: AN.LF1 vs AN.LF1
> <msnoise_table_def.Station object at 0x4a06ed0>
> <msnoise_table_def.Station object at 0x4a06ed0>
> s03compute_cc.py:407: DeprecationWarning: using a non-integer number 
> instead of an integer will result in an error in the future
>   trames2hWb[i] = np.zeros(Nfft)
> s03compute_cc.py:407: DeprecationWarning: using a non-integer number 
> instead of an integer will result in an error in the future
>   trames2hWb[i] = np.zeros(Nfft)
> /home/stag01/Bureau/MSNoise-1.2.3/myCorr.py:68: RuntimeWarning: 
> invalid value encountered in divide
>   corr /= np.real(normFact)
> Traceback (most recent call last):
>   File "s03compute_cc.py", line 412, in <module>
>      "%Y-%m-%d", time.gmtime(basetime + itranche * min30 / fe))
> NameError: name 'basetime' is not defined
>
> Do you know what can be the source of the problem ?
Well, first, you should not do Autocorrelation with this version of 
MSNoise. It'll work normally, but the result is wrong. I'll push a new 
release very soon that corrects that. But, this problem seems 
independent.  Reading your next mail, it could be related to the file 
reading part, but it does look strange...

Best regards,

Thomas