ndscope issueshttps://git.ligo.org/cds/software/ndscope/-/issues2024-03-01T22:03:21Zhttps://git.ligo.org/cds/software/ndscope/-/issues/334modifier key to restrict zoom to one axis or the other2024-03-01T22:03:21ZJameson Rollinsjameson.rollins@ligo.orgmodifier key to restrict zoom to one axis or the otherthis might help with issues with zoom using the axis onlythis might help with issues with zoom using the axis onlyhttps://git.ligo.org/cds/software/ndscope/-/issues/331request that pan (past) in online mode goes offline2024-02-29T00:10:38ZDhruva Ganapathyrequest that pan (past) in online mode goes offlinehttps://git.ligo.org/cds/software/ndscope/-/issues/330please provide gap after t0 in online mode2024-02-29T00:09:37ZDhruva Ganapathyplease provide gap after t0 in online modehttps://git.ligo.org/cds/software/ndscope/-/issues/327opportunistically download channel list2024-02-15T16:57:49ZJameson Rollinsjameson.rollins@ligo.orgopportunistically download channel listFor many/most invocations of ndscope the full channel list is not needed. For external servers the list can be very large. We should only download it opportunistically as needed, not on every invocation.For many/most invocations of ndscope the full channel list is not needed. For external servers the list can be very large. We should only download it opportunistically as needed, not on every invocation.https://git.ligo.org/cds/software/ndscope/-/issues/325trigger behavior funny when zooming/scrolling with new online axis locking2024-01-27T01:22:25ZJameson Rollinsjameson.rollins@ligo.orgtrigger behavior funny when zooming/scrolling with new online axis lockingThe trigger was supposed to reset t0 to the trigger point. But this induces some kind of odd behavior with the new locking of t=0 to the right axis edge of the plot.
Generally the trigger probably needs to be reworked to also address #...The trigger was supposed to reset t0 to the trigger point. But this induces some kind of odd behavior with the new locking of t=0 to the right axis edge of the plot.
Generally the trigger probably needs to be reworked to also address #291. Maybe move the trigger into the individual plot, and mark the trigger value with the vertical InfLine?https://git.ligo.org/cds/software/ndscope/-/issues/321request to change the default auto scaling to 99% ( or 98%)2024-01-19T17:22:50ZSheila Dwyerrequest to change the default auto scaling to 99% ( or 98%)The autoscale feature where you can set the limit to 99% is really useful. Could that be the default scaling? I am finding myself clicking through every plot and changing it to that now.
Alternatively, is there a way to request that...The autoscale feature where you can set the limit to 99% is really useful. Could that be the default scaling? I am finding myself clicking through every plot and changing it to that now.
Alternatively, is there a way to request that from the command line?https://git.ligo.org/cds/software/ndscope/-/issues/320display value of channel in legend2023-11-01T19:23:13ZSheila Dwyerdisplay value of channel in legendIt would be helpful to display the value of a channel in the legend, as was done in StripTool (I'd suggest not displaying the scaled value, but the actual value of the channel). This way people can read the value even if the channel is ...It would be helpful to display the value of a channel in the legend, as was done in StripTool (I'd suggest not displaying the scaled value, but the actual value of the channel). This way people can read the value even if the channel is scaled. This also helped address the concern Jamie raised in issue #201
As it is, with the data scaled by the channel, users are often unaware of the actual value of a channel.https://git.ligo.org/cds/software/ndscope/-/issues/319Does not display all added channels2023-10-06T23:07:45ZRobert SchofieldDoes not display all added channels![tmp3](/uploads/30c4b1d028e5813ad74dc688b4e76699/tmp3.png)![tmp3](/uploads/30c4b1d028e5813ad74dc688b4e76699/tmp3.png)https://git.ligo.org/cds/software/ndscope/-/issues/316channel auto-prefix IFO2023-07-06T22:15:14ZJameson Rollinsjameson.rollins@ligo.orgchannel auto-prefix IFOShould be able to specify channels like ":GRD-ISC_LOCK_STATE_N", and have it fill in the IFO prefix automatically.Should be able to specify channels like ":GRD-ISC_LOCK_STATE_N", and have it fill in the IFO prefix automatically.https://git.ligo.org/cds/software/ndscope/-/issues/308add scipy as conda dependency2023-03-01T18:38:16ZJameson Rollinsjameson.rollins@ligo.orgadd scipy as conda dependencythis would be a good convenience for matlab usersthis would be a good convenience for matlab usershttps://git.ligo.org/cds/software/ndscope/-/issues/307Cannot Use Crosshair nor Change Time Axis Format in "Online" Mode (and want t...2023-02-27T18:44:56ZJeffrey KisselCannot Use Crosshair nor Change Time Axis Format in "Online" Mode (and want to) [ndscope 0.17.0]I'm not sure if this is a recent degradation in functionality or it never was a part of the functionality, but one cannot (can no longer?) enable the crosshair feature or change the time axis in online mode. Offline mode works fine. I'm...I'm not sure if this is a recent degradation in functionality or it never was a part of the functionality, but one cannot (can no longer?) enable the crosshair feature or change the time axis in online mode. Offline mode works fine. I'm using ndscope 0.17.0 in the LHO control room.https://git.ligo.org/cds/software/ndscope/-/issues/303Request to add a spectra feature2023-01-07T17:58:59ZArnaud PeleRequest to add a spectra feature Is it possible to add a spectra feature on ndscope ? This would be a very handy tool for quickly checking spectral content of time series. Is it possible to add a spectra feature on ndscope ? This would be a very handy tool for quickly checking spectral content of time series.https://git.ligo.org/cds/software/ndscope/-/issues/295Can yaml file turn legend off or define its position2023-07-06T18:36:40ZDavid BarkerCan yaml file turn legend off or define its positionThe default legend location causes it to obscure the delta-t text. Is there a command line or yaml directive to either defined the legend's origin or turn it off altogether?The default legend location causes it to obscure the delta-t text. Is there a command line or yaml directive to either defined the legend's origin or turn it off altogether?https://git.ligo.org/cds/software/ndscope/-/issues/291trigger does not use transformed data2024-01-27T01:21:53ZJameson Rollinsjameson.rollins@ligo.orgtrigger does not use transformed dataThe trigger uses the raw data, not the data with scale or offset applied.
This is also true for the level reset, which tries to set the level based on the available data, but it doesn't include applied scale or offset.The trigger uses the raw data, not the data with scale or offset applied.
This is also true for the level reset, which tries to set the level based on the available data, but it doesn't include applied scale or offset.https://git.ligo.org/cds/software/ndscope/-/issues/288Option to remove SI Scaling2022-08-18T03:23:43ZErik von ReisOption to remove SI ScalingSetting SI scaling to False stops PyQTGraph from adding an arbitrary "power of 10" scale to the Y axis.
Scaling is caused by the auto-prefixing feature, which can change the SI prefix on units, but will also change scaling if there are ...Setting SI scaling to False stops PyQTGraph from adding an arbitrary "power of 10" scale to the Y axis.
Scaling is caused by the auto-prefixing feature, which can change the SI prefix on units, but will also change scaling if there are no units assigned to the axis.
```python
plot.getAxis('left').enableAutoSIPrefix(False)
```
AutoSIPrefix is default to Truehttps://git.ligo.org/cds/software/ndscope/-/issues/286Strange behavour after I zoomed in far2022-07-06T17:44:54ZCamilla ComptonStrange behavour after I zoomed in farOpened using `ndscope -t 1338571919 -t 1338571999 H1:SUS-ETMY_L3_LOCK_BIAS_OUTPUT H1:SUS-ETMY_L3_DRIVEALIGN_L2L_OUTPUT H1:SUS-ETMY_L3_LOCK_BIAS_SWSTAT H1:SUS-ETMY_L3_LOCK_BIAS_OFFSET H1:SUS-ETMY_L3_LOCK_BIAS_OUT16 &
`
When I zoomed fa...Opened using `ndscope -t 1338571919 -t 1338571999 H1:SUS-ETMY_L3_LOCK_BIAS_OUTPUT H1:SUS-ETMY_L3_DRIVEALIGN_L2L_OUTPUT H1:SUS-ETMY_L3_LOCK_BIAS_SWSTAT H1:SUS-ETMY_L3_LOCK_BIAS_OFFSET H1:SUS-ETMY_L3_LOCK_BIAS_OUT16 &
`
When I zoomed far in y into to H1:SUS-ETMY_L3_LOCK_BIAS_SWSTAT amd then zoomed in x the data jumped from changing to being all at the 265.47 value.
See attachments. I also have a video.
![ndscope_issue_2](/uploads/dbd32164b0fea5da72faf922f54f5d17/ndscope_issue_2.png)
![ndscope_issuezoom](/uploads/f1dd0ee9a9e50e2b0a91f3e159d83a6b/ndscope_issuezoom.png)
[ndscopeissue.hdf5](/uploads/7469e2058f8f96c46a0dde4d393c9ec6/ndscopeissue.hdf5)
[ndscopeissue_2.hdf5](/uploads/24387943b3d80f2887d75813a6dc315b/ndscopeissue_2.hdf5)https://git.ligo.org/cds/software/ndscope/-/issues/285time axis text cut off at the bottom2024-01-16T19:21:48ZDavid Barkertime axis text cut off at the bottomIf you select a two-row time axis (e.g. absolute local) the lower part of the text is cut off. Resizing the window does not correct this.![Screen_Shot_2022-07-05_at_15.25.44](/uploads/a0df0e62e6021eb0c8dea720fc796ab9/Screen_Shot_2022-07-...If you select a two-row time axis (e.g. absolute local) the lower part of the text is cut off. Resizing the window does not correct this.![Screen_Shot_2022-07-05_at_15.25.44](/uploads/a0df0e62e6021eb0c8dea720fc796ab9/Screen_Shot_2022-07-05_at_15.25.44.png)https://git.ligo.org/cds/software/ndscope/-/issues/282inconsistent template generation from within scope and from command line2022-06-29T17:49:07ZJameson Rollinsjameson.rollins@ligo.orginconsistent template generation from within scope and from command lineThere is inconsistency in how the templates are generated from the command line and from the `NDScope.get_template()` method. In particular, they are creating templates with different variables set. We should use a common function for ...There is inconsistency in how the templates are generated from the command line and from the `NDScope.get_template()` method. In particular, they are creating templates with different variables set. We should use a common function for template generation for all uses, so that templates are generated consistently.
This is somewhat related to #247ndscope 0.16https://git.ligo.org/cds/software/ndscope/-/issues/280better way to distinguish between min/max trend data2022-06-22T16:57:58ZJameson Rollinsjameson.rollins@ligo.orgbetter way to distinguish between min/max trend dataIt would be nice if we had a better way to distinguish between the min/max trend traces. This is more important now that we have the ability to turn of the min/max/mean trend traces, as there's currently no indication in the plot which ...It would be nice if we had a better way to distinguish between the min/max trend traces. This is more important now that we have the ability to turn of the min/max/mean trend traces, as there's currently no indication in the plot which traces are on or off.
One suggestion would be to use different line style for min, max, and mean. Or to use a marker for min and max, like something like an up arrow for max and a down arrow for min. Need to test out some alternatives...https://git.ligo.org/cds/software/ndscope/-/issues/279feature request: An option to show a marker for each data point, that can be ...2022-06-21T21:50:12ZPatrick Thomasfeature request: An option to show a marker for each data point, that can be clicked to get its exact valueRelated to issue #13.Related to issue #13.