Ivar had a dataset in his script that would link BMag and R, which are both time series with TSB. The result is also a TSB, but it is not trimmed, and he would see several orbits' worth of data on his half-orbit plots.
I am reminded of this bug when using the mash-up tool to look at DST vs Kp. It always shows six months, even if the timerange is just one month.
Try the mash up script: vap+inline:dst=getDataSet('vap+cdaweb:ds=OMNI2_H0_MRG1HR&id=DST1800&timerange=2015-12-06+06:09+to+2016-02-02+20:24')&kp=getDataSet('vap+cdaweb:ds=OMNI2_H0_MRG1HR&id=KP1800&timerange=2015-12-06+06:09+to+2016-02-02+20:24')&kp=synchronizeOne(dst,kp)&link(dst,kp)&timerange=July+2016
I am reminded of this bug when using the mash-up tool to look at DST vs Kp. It always shows six months, even if the timerange is just one month.
Try the mash up script: vap+inline:dst=getDataSet('vap+cdaweb:ds=OMNI2_H0_MRG1HR&id=DST1800&timerange=2015-12-06+06:09+to+2016-02-02+20:24')&kp=getDataSet('vap+cdaweb:ds=OMNI2_H0_MRG1HR&id=KP1800&timerange=2015-12-06+06:09+to+2016-02-02+20:24')&kp=synchronizeOne(dst,kp)&link(dst,kp)&timerange=July+2016
And advance to Aug 2016. Notice nothing changes.
Said another way:
This prints "2016-07-01 00:00 to 2016-12-31 23:00"...
Last edit: Jeremy Faden 2017-04-27
I'm putting in an experimental trimToTsbRange function that will trim the data when there are rank 1 timetags found within the data.
This appears to work without causing any new problems.