[INSTRM-1891] axis limit error causes crash Created: 11/Mar/23  Updated: 14/Mar/23  Resolved: 14/Mar/23

Status: Won't Fix
Project: Instrument control development
Component/s: ics_sps_engineering_plotData
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: arnaud.lefur
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I think this was triggered by my turning off an axis which had no enabled traces.

/software/mhs/products/Linux64/ics_sps_engineering_plotData/1.3.4/python/sps_engineering_plotData/graph.py:212: RuntimeWarning: invalid value encountered in log10
  dmin = 1.0 * 10 ** (np.floor(np.log10(dmin)))
Traceback (most recent call last):
  File "/software/mhs/products/Linux64/ics_sps_engineering_plotData/1.3.4/python/sps_engineering_plotData/tab.py", line 99, in getData
    self.plotWindow.graph.updatePlot(timing)
  File "/software/mhs/products/Linux64/ics_sps_engineering_plotData/1.3.4/python/sps_engineering_plotData/graph.py", line 232, in updatePlot
    needDraw = self.updateLimits(axes, tmax, scaleY=(not self.isPanned))
  File "/software/mhs/products/Linux64/ics_sps_engineering_plotData/1.3.4/python/sps_engineering_plotData/graph.py", line 265, in updateLimits
    ax.set_ylim(self.calc_lim(newMin, newMax, logy=logy))
  File "/software/conda/envs/rubin3_ics/lib/python3.8/site-packages/matplotlib/axes/_base.py", line 4027, in set_ylim
    bottom = self._validate_converted_limits(bottom, self.convert_yunits)
  File "/software/conda/envs/rubin3_ics/lib/python3.8/site-packages/matplotlib/axes/_base.py", line 3614, in _validate_converted_limits
    raise ValueError("Axis limits cannot be NaN or Inf")
ValueError: Axis limits cannot be NaN or Inf
/software/mhs/products/Linux64/ics_sps_engineering_plotData/1.3.4/bin/plotdata: line 1: 17496 Aborted                 python -m sps_engineering_plotData.main "$@"


 Comments   
Comment by arnaud.lefur [ 14/Mar/23 ]

I actually fixed that bug last month.
But for some reason, you were not using the latest version (1.3.6)

Generated at Sat Feb 10 16:40:45 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.