Hi all,
I have some data that I have written into an array via [array read textFile.txt(.
This works fine, but is there a way of zooming in on the data along the x-axis? I was thinking along the lines of changing the array size, or only showing data items between two points on the x-axis...

Thanks loads,
Tommy

William Brent's [tabletool] can spit out values of a certain range from a table, pretty much what you want, if I understood you post...
http://williambrent.conflations.com/pages/research.html
scroll down till you see 'tabletool'

@alexandros Thanks, But unfortunately for my work it needs to use Pd-extended objects only. It does seem to be what I'm after though..., Do you have any other suggestions?

Hi,

What about creating two arrays, one which will store the whole data, and the other which will only store and show a certain part of the first array (thus zooming in)? The problem with pd is that although you can set a smaller range to be shown by right clicking in an array and selecting properties (you will see x and y ranges), the data points will be shown even if located outside the graph, which is just horrible...

Best,
Gilberto

How about this? It's based on Gilberto's suggestion, using two arrays. zoom.pd uses [multisl], which needs PD extended to run, but zoom_basic.pd should run on vanilla.

zoom.zip

@LiamG This is fantastic, Liam, that's exactly what I had in mind. And here is a version containing a small alteration, which allows us to zoom in the y-axis as well: zoom.zip

Take care,
Gilberto

@gsagostinho

Nice addition, Gilberto.

You can actually make the x-axis zoom work in real time, like Gilberto's y-axis, by taking out the first list object, so it looks like this:

[multisl]
|
[list-sort asc]
|
[zl rev]
|
etc.

This way, you don't need to bang limit markers--they will update in real time. Things get jumpy when you select larger areas, though, because you are sending very large numbers to the [until] object every time you move a marker. Perhaps you could make it so that array2 only receives the new data points to add or subtract when the selection is changed, rather than receiving a total set each time? This would make it run smoother, although I don't know whether it's possible.

@LiamG So what about using a metro object to constantly bang it then? This way, the object can be updated at a relatively fast pace (let's say something like 50ms) without getting into troubles. And of course, one can turn the metro off when not using it. What do you think?

Gilberto