-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msnoise cc stack -m test fails #319
Comments
Okay so turns out it's just a change in behaviour when number of 1-days CCFs is less than mov_stack size. i.e. for the tests, which use only 1-day of data, having mov_stack = 5 would not return an error in old codes as it would output the 1-day CCF in the place of the 5-day stack based on setting low and high indexing. old code:
whereas in the new code, it returns an error if mov_stack is larger than number of ccfs, which is why test failing i.e. new code:
So not an issue really, but still tests should be updated so will leave open (and have updated title). Perhaps to include 2 days of data and set mov_stack = 2 for example... or even just mov_stack = 1? |
I'm thinking of adding a larger test dataset, but that should be automagically downloaded with https://github.com/fatiando/pooch , making the default code base super light (and not 30 MB as now). Include more than 5 days of data, and also horizontal components, what do you think? |
pooch is a fact now :) |
Testing the new stack command, i am getting errors due to the data not being found for the moving stack. Can see this also when running msnoise utils test:
I haven't looked into the specifics of the .nc files at this stage, but can see that in STACKS2 directory being created (running a different example) that i have only one 001 day file per station-pair and channel. If this is similar to hdf5 files, i guess this is expected.
msnoise cc stack_old runs fine, but i guess then mwcs and stretching (new and old) both based on STACKS2 directory (at least seems that way based on --help documentation and compute_dtt_old not outputting anything).
The text was updated successfully, but these errors were encountered: