Re: [MSNoise] advice on processing database subsets

Hi again, Thanks for the comments. Here's what I did to set just a singe day for processing, so that I can test the parameter settings. I looked into the API code and needed to import from msnoise_table_def.py, but it seems to work OK: from msnoise.api import connect from msnoise_table_def import Job set_day = '2013-10-14' jobtype = 'CC' session = connect() jobs_set = session.query(Job).filter(Job.jobtype == jobtype).filter(Job.day == set_day) jobs_set.update({Job.flag: 'T'}) jobs_unset = session.query(Job).filter(Job.jobtype == jobtype).filter(Job.day != set_day) jobs_unset.update({Job.flag: 'D'}) session.commit() So now I have a jobs table with just the day I want set to 'T'. I hoped I was ready to try 'msnoise compute_cc', but it seems to want me to set Filters first. This appears to be referring to the MCWS filter parameters? I am a little surprised since I thought MCWS would come later, and don't understand how the CC computation would be dependent on the MCWS filter parameters. To tell you the truth, at the moment I am more interested in using the msnoise cross-correlations as input to a tomography algorithm, rather than in MCWS itself. In any case I am keen to look at the CC to see that they make sense, before i move to anything else. Would it be possible to please advise on whether there is a way to do compute_cc without having to worry about the MCWS parameters? Thanks, - Phil Thomas Lecocq wrote: