profile
viewpoint
LGS Innovations, LLC LGSInnovations

LGSInnovations/sigplot 29

SigPlot provides fast interactive web-plotting for software defined radio.

LGSInnovations/node-dbus-network-manager 5

Interface to network manager DBUS interface

LGSInnovations/edison-debian-image 4

The ext4 partition to flash the Intel Edison, based on ubilinux

LGSInnovations/edison-mini-pcie 3

Hardware design for mini pci express block

LGSInnovations/jupyter-sigplot 3

Jupyter Notebook extension for SigPlot.js

LGSInnovations/react-sigplot 3

React wrapper for SigPlot.js

LGSInnovations/edison-gpio-example 2

Control GPIO via web interfaces

LGSInnovations/sigfile 2

Module to read signal data from files

LGSInnovations/angularjs-combo-box 1

angular 1.x directive allowing input in a natively styled select

startedLGSInnovations/sigplot

started time in 9 days

issue closedLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

All,

This is a bit of a shot in the dark, but ya'll have been outstandingly helpful to me with other Sigplot issues that I have run into, so I figured it would be worth asking...

Presently, I have a plot where the x values range from say 1500 to 1700. For some reason though, the tick mark labels are shown as things like 1.5, 1.6, etc. I can see in the readout that the corresponding x values really are things like 1500.12345 and such, but I can not for the life of me figure out how to get the tick mark labels to correspond. There is ample space for the full value to be displayed, I have even tried setting xdiv to 1 in order to guarantee as much.

The relevant code appears to be something in the vicinity of: https://github.com/LGSInnovations/sigplot/blob/480cec393280a41359924383d06bb6849eeab879/js/mx.js#L3132

but to be honest I have had a hard time making heads or tails of the source code. It seems very well written, just a bit dense to try and find a solid starting point as someone coming from the outside.

If anyone is willing to help me out once more then I'd be all the more grateful.

Thanks! -Kevin

closed time in 2 months

KevinPoole

issue commentLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

Eureka! I believe I figured it out.

Seems to be an undocumented flag that I discovered here: image so I added an xmult: 1 to my options and was able to achieve the desired effect.

Thanks again for the help troubleshooting!

KevinPoole

comment created time in 2 months

issue commentLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

Alright @maihde , so I have gotten set up with breakpoints and have the above info.

When I get to the line:

xlbl = mx.format_f(x * fmul, xlbl_maxlen, xlbl_maxlen / 2);

The following is true:

Inputs:
x: 1300
fmul: 0.001
xlbl_maxlen: 12

and subsequently:

Output:
xlbl: "          1.300000"

which checks out with what I have seen in practice.

And so to put my question in these terms specifically, I'm basically looking for how to get the above output to be 1300 instead of 1.300000 ... thanks for your help thus far.

KevinPoole

comment created time in 2 months

issue commentLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

@maihde this should prove to be very helpful information. I am going to dig further right now.

Where I left off yesterday was actually trying to get set up in such a way that I could put breakpoints into the relevant sigplot code. So once I get that setup I should be able to use the above information you have provided to try and answer your questions.

Regarding:

How you are determining the tic marks are at something like 1500.12345? Are you hovering the mouse and reading the values?

No, you are likely correct that the tic marks themselves are landing on "round" values ending in zeroes which are getting trimmed. I just mean that It is not as if my x values are truly ranging from 1.5 to 1.7 and that I had been able to confirm that by seeing values such as 1500.12345 in the readout.

More to come...

KevinPoole

comment created time in 2 months

issue commentLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

@KevinPoole thanks for the kind words, both about SigPlot and our assistance to you.

You are correct, the source code is pretty dense, lacks comments, and has a bunch of anachronisms because of its initial goal of pixel-perfect replication of the existing X-MIDAS plots (written in FORTRAN).

The tics are determined by mx.tics. The purpose of mx.tics is given a range dmin=1500 to dmax=1700 to create ndiv=5 tics. The code in mx.tics is a bit opaque and basically has a logic that was determine decades ago in the MIDAS plots as "what looks right". :)

Anyways, the result of mx.tics will be dtic1=1500 (i.e. the first tic) and dtic=50 the space between tics. If you put something in like dmin=1505,dmax=1733 you will get dtic1=1550,dtic=50. Can you put a breakpoint on mx.tics and tell me what both the input and output is?

The function mx.drawaxis is where the actually drawing occurs. Around this line:

https://github.com/spectriclabs/sigplot/blob/a7ac8f6daa847adb83e6299d60c38e5486c900bf/js/mx.js#L3088

Is where the tics created by mx.tics are actually rendered using mx.format_f on:

https://github.com/spectriclabs/sigplot/blob/a7ac8f6daa847adb83e6299d60c38e5486c900bf/js/mx.js#L3112

If you put a break-point there what are the input values? My guess is that the tics are being drawn on round numbers (as described above) and the behavior of format_f is to trim unnecessary trailing zeros.

How you are determining the tic marks are at something like 1500.12345? Are you hovering the mouse and reading the values? If so, the discrepancy might simply be due the conversion of pixel coordinated to real coordinates, since pixels and real values may not always be aligned.

Let me know what you find.

KevinPoole

comment created time in 2 months

issue openedLGSInnovations/sigplot

How to alter the axis labels (tick mark labels) to be full value rather than decimal version

All,

This is a bit of a shot in the dark, but ya'll have been outstandingly helpful to me with other Sigplot issues that I have run into, so I figured it would be worth asking...

Presently, I have a plot where the x values range from say 1500 to 1700. For some reason though, the tick mark labels are shown as things like 1.5, 1.6, etc. I can see in the readout that the corresponding x values really are things like 1500.12345 and such, but I can not for the life of me figure out how to get the tick mark labels to correspond. There is ample space for the full value to be displayed, I have even tried setting xdiv to 1 in order to guarantee as much.

The relevant code appears to be something in the vicinity of: https://github.com/LGSInnovations/sigplot/blob/480cec393280a41359924383d06bb6849eeab879/js/mx.js#L3132

but to be honest I have had a hard time making heads or tails of the source code. It seems very well written, just a bit dense to try and find a solid starting point as someone coming from the outside.

If anyone is willing to help me out once more then I'd be all the more grateful.

Thanks! -Kevin

created time in 2 months

delete branch LGSInnovations/vue-sigplot

delete branch : dependabot/npm_and_yarn/url-parse-1.5.1

delete time in 2 months

pull request commentLGSInnovations/vue-sigplot

chore(deps): Bump url-parse from 1.4.7 to 1.5.1

Superseded by #20.

dependabot[bot]

comment created time in 2 months

PR closed LGSInnovations/vue-sigplot

chore(deps): Bump url-parse from 1.4.7 to 1.5.1 dependencies

Bumps url-parse from 1.4.7 to 1.5.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/unshiftio/url-parse/commit/eb6d9f51e395b7e47bf2594e457d541db21c713b"><code>eb6d9f5</code></a> [dist] 1.5.1</li> <li><a href="https://github.com/unshiftio/url-parse/commit/750d8e8a9d45dbce9ff09759f0fe4564cdd47d74"><code>750d8e8</code></a> [fix] Fixes relative path resolving <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/199">#199</a> <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/200">#200</a> (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/201">#201</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/3ac777474ba5dc48a7e33771cbb311fc6f69bef8"><code>3ac7774</code></a> [test] Make test consistent for browser testing</li> <li><a href="https://github.com/unshiftio/url-parse/commit/267a0c6f7ef1a58271be61611c5103daace602c9"><code>267a0c6</code></a> [dist] 1.5.0</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0"><code>d1e7e88</code></a> [security] More backslash fixes (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/197">#197</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d99bf4cf259b7378c855f786edc253e70405ffdc"><code>d99bf4c</code></a> [ignore] Remove npm-debug.log from .gitignore</li> <li><a href="https://github.com/unshiftio/url-parse/commit/422c8b5e4cac6a79cd35b4e86731476dcbeec7e4"><code>422c8b5</code></a> [pkg] Replace nyc with c8</li> <li><a href="https://github.com/unshiftio/url-parse/commit/933809d630c7b21399b4e5df59fccccd80033b21"><code>933809d</code></a> [pkg] Move coveralls to dev dependencies</li> <li><a href="https://github.com/unshiftio/url-parse/commit/190b2168035899a2a88f2dc2625963bf7e2f338f"><code>190b216</code></a> [pkg] Add .npmrc</li> <li><a href="https://github.com/unshiftio/url-parse/commit/ce3783f4ea25753cfa36376769c14e4e2fe6ea80"><code>ce3783f</code></a> [test] Do not test on all available versions of Edge and Safari</li> <li>Additional commits viewable in <a href="https://github.com/unshiftio/url-parse/compare/1.4.7...1.5.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+6 -6

1 comment

1 changed file

dependabot[bot]

pr closed time in 2 months

PR opened LGSInnovations/vue-sigplot

chore(deps): Bump url-parse from 1.4.7 to 1.5.3

Bumps url-parse from 1.4.7 to 1.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/unshiftio/url-parse/commit/ad444931666a30bad11472d89a216461cf16cae2"><code>ad44493</code></a> [dist] 1.5.3</li> <li><a href="https://github.com/unshiftio/url-parse/commit/c7984617e235892cc22e0f47bb5ff1c012e6e39f"><code>c798461</code></a> [fix] Fix host parsing for file URLs (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/210">#210</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/201034b8670c2aa382d7ec410ee750ac6f2f9c38"><code>201034b</code></a> [dist] 1.5.2</li> <li><a href="https://github.com/unshiftio/url-parse/commit/2d9ac2c94067742b2116332c1e03be9f37371dff"><code>2d9ac2c</code></a> [fix] Sanitize only special URLs (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/209">#209</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/fb128af4f43fa17f351d50cf615c7598c751f50a"><code>fb128af</code></a> [fix] Use <code>'null'</code> as <code>origin</code> for non special URLs</li> <li><a href="https://github.com/unshiftio/url-parse/commit/fed6d9e338ea39de2d68bb66607066d71328c62f"><code>fed6d9e</code></a> [fix] Add a leading slash only if the URL is special</li> <li><a href="https://github.com/unshiftio/url-parse/commit/94872e7ab9103ee69b958959baa14c9e682a7f10"><code>94872e7</code></a> [fix] Do not incorrectly set the <code>slashes</code> property to <code>true</code></li> <li><a href="https://github.com/unshiftio/url-parse/commit/81ab967889b08112d3356e451bf03e6aa0cbb7e0"><code>81ab967</code></a> [fix] Ignore slashes after the protocol for special URLs</li> <li><a href="https://github.com/unshiftio/url-parse/commit/ee22050a48a67409aa5f7c87947284156d615bd1"><code>ee22050</code></a> [ci] Use GitHub Actions</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d2979b586d8c7751e0c77f127d9ce1b2143cc0c9"><code>d2979b5</code></a> [fix] Special case the <code>file:</code> protocol (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/204">#204</a>)</li> <li>Additional commits viewable in <a href="https://github.com/unshiftio/url-parse/compare/1.4.7...1.5.3">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+6 -6

0 comment

1 changed file

pr created time in 2 months

pull request commentLGSInnovations/sigfile

chore(deps): bump tmpl from 1.0.4 to 1.0.5

Codecov Report

Merging #33 (4ef7177) into master (f86c63e) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   67.12%   67.12%           
=======================================
  Files           5        5           
  Lines         435      435           
  Branches       73       73           
=======================================
  Hits          292      292           
  Misses        126      126           
  Partials       17       17           

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update f86c63e...4ef7177. Read the comment docs.

dependabot[bot]

comment created time in 2 months

PR opened LGSInnovations/sigfile

chore(deps): bump tmpl from 1.0.4 to 1.0.5

Bumps tmpl from 1.0.4 to 1.0.5. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/daaku/nodejs-tmpl/commits/v1.0.5">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+4 -4

0 comment

1 changed file

pr created time in 2 months

create barnchLGSInnovations/sigfile

branch : dependabot/npm_and_yarn/tmpl-1.0.5

created branch time in 2 months

create barnchLGSInnovations/react-sigplot

branch : dependabot/npm_and_yarn/tmpl-1.0.5

created branch time in 2 months

PR opened LGSInnovations/react-sigplot

build(deps): bump tmpl from 1.0.4 to 1.0.5

Bumps tmpl from 1.0.4 to 1.0.5. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/daaku/nodejs-tmpl/commits/v1.0.5">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+12 -27

0 comment

1 changed file

pr created time in 2 months

issue commentLGSInnovations/sigplot

Display currently "selected" intensity value with raster plots

@KevinPoole I think I found the issue. If the minimum z value was zero it would cause the 'show-z' method to not display anything. https://github.com/spectriclabs/sigplot/commit/905903e4b649021d47ca61b44e69ecbcf45835c6

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

@KevinPoole I've added a new mode to layer1d this is more clearly for XY drawing. Historically, XY plots were done by sending in "complex" format data and rendering in "IR" mode. This new feature achieves the same effect without resorting to an esoteric method.

https://github.com/spectriclabs/sigplot/tree/feature/layer1d-xy-mode https://github.com/spectriclabs/sigplot/blob/9c7958a063762a369196cb8c2ec8cc28b00b56bf/test/tests.interactive-symbols.js#L175

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

@KevinPoole try this example: https://jsfiddle.net/68hkc0dx/1/

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

@maihde if there were a way to provide a series of X/Y coordinate points and have them plotted as a connected line then that would solve my dilemma perfectly!

Thanks very much!

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

Also, if this is a work-related project, it might be nice to connect so that we can better understand your needs and requirements. Feel free to email me directly at mihde@spectric.com.

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

Kevin, there isn't a way to do variable xdelta, but there is a way to provide a series of X/Y coordinate pairs. I'll dig up an example for you and respond here.

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

For now I have gone with the interpolation approach, and while not ideal, I am quite pleased to see how snappy it performs even with 43k + 15.6k data points. very impressive

KevinPoole

comment created time in 3 months

issue openedLGSInnovations/sigplot

Plotting array layer of data with varied xdelta values

Hi Sigplot team,

You all have been very helpful helping me with a couple of other issues I have worked through, so I thought I might push my luck with my latest question...

I have a situation where I need to plot a set of values, and want them connected with a line, but the values are not guaranteed to have a consistent xdelta. To give a trivial illustration:

x  | y
-----
0  | 1
2  | 5
5  | 10
6  | 7
10 | 11

so x is guaranteed to monotonically increase, but the gaps from one value to the next vary. I was wondering if there is a way to accomplish this with sigplot? I have seen the xdelta and xstart options which are all relevant to my problem space, but do not seem to aid this particular issue.

A work around I have considered, is linearly interpolating the data so that it ends up having a constant xdelta but this would require inserting "fake data" and I would rather avoid this if at all possible.

Your assistance is, as always, greatly appreciated!

created time in 3 months

IssuesEvent

issue commentLGSInnovations/sigplot

Display currently "selected" intensity value with raster plots

Hi @maihde - actually, no. Perhaps closing the issue was the wrong approach. Truthfully what happened is that this particular problem fell in priority for me at the moment.

Also, we're using the react-sigplot library from NPM so I was not positive how to take your suggested next steps.

I will reopen the issue - sorry for the confusion.

KevinPoole

comment created time in 3 months

issue commentLGSInnovations/sigplot

Display currently "selected" intensity value with raster plots

@KevinPoole - due to the fact that you closed this, am I to assume that you have resolved the issue?

KevinPoole

comment created time in 3 months

issue closedLGSInnovations/sigplot

Display currently "selected" intensity value with raster plots

Hey all,

First, a very cool tool. Appreciate you all making this available.

I am putting this as a feature request but it may really just be a request for slightly more detailed documentation.

All I want to do, is when hovering over a raster plot, to be able to see what the value is of any given pixel I am hovered over (the Z value basically, the intensity). If necessary I could do this in some sort of custom way with event listeners (at least, I think I could. I could do something similar to the mouse events example - https://sigplot.lgsinnovations.com/sigplot-2.0/tryout.html - and try to figure out where I am in the raster grid and then correlate that to the value in the source data) but it just seems like the sort of thing that sigplot must surely support out of the box and I simply can not figure out how. I would expect to be able to see a z (and corresponding dz value) in the bottom left of the plot window, or at least to be able to optionally toggle on such a thing, but again I can not figure out how.

Thanks in advance for any assistance you can offer!

closed time in 3 months

KevinPoole

startedLGSInnovations/sigplot

started time in 3 months

more