ts_num_gaps reports 0 stations when any other ts_ metric above it on the list is also selected

[gillian-earthscope]

If I select both ts_num_gaps (or ts_num_gaps_total) and any of the other ts_ metrics above it in the list on the query form, then ts_num_gaps displays as having 0 stations available. If I download the data, I see expected results with both metrics having values for all stations. The metrics that conflict with ts_num_gaps are ts_channel_continuity, ts_channel_up_time, ts_gap_length, ts_gap_length_total, ts_max_gap, and ts_max_gap_total. Other combinations of metrics with ts_num_gaps do not have this issue. If I edit the query by hand so that ts_num_gaps is listed first, then I also get expected results.

This returns 205 stations for ts_max_gap and 0 stations for ts_num_gaps:
http://ds.iris.edu/mustang/mustangular/#/map?net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_MAX_GAP,TS_NUM_GAPS

This works and returns 205 stations for each metric:
http://ds.iris.edu/mustang/mustangular/#/map?net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_NUM_GAPS,TS_PERCENT_AVAILABILITY

Also ok:
http://ds.iris.edu/mustang/mustangular/#/map?net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=SAMPLE_MEAN,TS_NUM_GAPS

If I manually switch the order of ts_num_gaps and ts_max_gap, then they both return 205 stations:
http://ds.iris.edu/mustang/mustangular/#/map?net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_NUM_GAPS,TS_MAX_GAP

[kyla-m]

I think this might be coming from MUSTANG.

If I make the request:
http://service.iris.edu/mustang/measurements/1/query?nodata=200&net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_MAX_GAP,TS_NUM_GAPS&output=json
I receive an error for TS_NUM_GAPS.

If I swap TS_NUM_GAPS and TS_MAX_GAP like you did:
http://service.iris.edu/mustang/measurements/1/query?nodata=200&net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_NUM_GAPS,TS_MAX_GAP&output=json
It works fine.

[gillian-earthscope]

I'll follow up on that. I only looked at the text and csv output, which was ok. I didn't think to try the json. Thanks, Gillian

…

----- Original Message ----- From: "Kyla Marczewski" <notifications@github.com> To: "pnsn/mustangular" <mustangular@noreply.github.com> Cc: "gillian" <gillian@iris.washington.edu>, "Author" <author@noreply.github.com> Sent: Thursday, December 20, 2018 10:19:16 AM Subject: Re: [pnsn/mustangular] ts_num_gaps reports 0 stations when any other ts_ metric above it on the list is also selected (#7) I think this might be coming from MUSTANG. If I make the request: http://service.iris.edu/mustang/measurements/1/query?nodata=200&net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_MAX_GAP,TS_NUM_GAPS&output=json I receive an error for TS_NUM_GAPS. If I swap TS_NUM_GAPS and TS_MAX_GAP like you did: http://service.iris.edu/mustang/measurements/1/query?nodata=200&net=TA&cha=BHZ&start=2018-12-01&end=2018-12-15&metric=TS_NUM_GAPS,TS_MAX_GAP&output=json It works fine.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #7 (comment)

[gillian-earthscope]

This issue has been fixed.