21 May
2019
21 May
'19
4:01 a.m.
Thanks Thomas!
-ashton
On Tue, May 14, 2019 at 1:42 AM Thomas Lecocq <Thomas.Lecocq(a)seismology.be>
wrote:
Hi Ashton,
Yep, in :master: the workflow has changed, you need to
$ msnoise stack -r
$ msnoise reset STACK
$ msnoise stack -m
and this will again change before release, most probably by changing the
ref stack so it doesn't change the job status
Thomas
On 12/05/2019 20:48, Flinders, Ashton wrote:
--
Ashton F. Flinders, Ph.D
Presidential Management Fellow
U.S. Geological Survey
Hawaiian Volcano Observatory
(808) 224 4367
* Python 3.6 w/ latest pull of msnoise from git.
* first run through the complete workflow with on a new project
* CC step seems to complete fine, although I should note I'm not saving
the
full CC files
Problem. When I run the stack (msnoise stack -r -m) for the first time
everything just gets flags as in progress, but never actually completes
before the code exits. No stack folder is made, and no data written. I
get
one of these messages for each CC-pair;
2019-05-12 04:56:05.085438 msnoise [pid 11389][INFO]: There are STACKS
jobs
for some days to recompute for HV.MLOD:HV.TRAD
any idea whats going on?
Thanks!
ashton
--
Dr. Thomas Lecocq
Geologist - Seismologist
Seismology - Gravimetry
Royal Observatory of Belgium
*
* * * * *
* * * *
---------
http://www.seismology.be
http://msnoise.org
http://twitter.com/#!/Seismologie_be
https://www.facebook.com/seismologie.be
_______________________________________________
MSNoise mailing list
MSNoise(a)mailman-as.oma.be
http://mailman-as.oma.be/mailman/listinfo/msnoise