Subject: Working with large volumes of data in Igor
In-Reply-To: <CAGjoBTUaSjy7z6OaAv4AXXt=+Jaj9bQ_uff63GMFN84nG0dm8w@mail.gmail.com>
References: <CAGjoBTUaSjy7z6OaAv4AXXt=+Jaj9bQ_uff63GMFN84nG0dm8w@mail.gmail.com>
Message-ID: <CACTDJ6gZtD8oGGXHYomMG24bDYphDo_6smJbHLDwQim-UpN+6w@mail.gmail.com>

Albert :

On Tue, May 21, 2019 at 3:22 PM Albert Aumentado <
aaumentado at imprintenergy.com> wrote:

>
> I realize the solution might mean shifting to a different tool altogether
> (Python-based or MatLab) or maybe PC hardware improvements (I am on Igor
> Pro 8 with a Win10/16GB RAM/Intel Core i7).


Better hardware might improve things at the margins, but this sounds like a
decent system hardware wise.


> However, I have a feeling that
> there may be better ways of working in Igor that I am not yet aware.
>
> That's almost certainly true.

However, you haven't given enough information about what you are trying to
do and what the performance bottleneck(s) is/are (or what you think they
are) for us to provide any specific advice.

Based on what you described, you are working with a larger number of waves
and traces than the vast majority of users, but there are users with
similar amounts of data, and we are often able to help users rewrite code
to gain substantial improvements.

If you'd prefer you can use Help->Contact Support (or email
support at wavemetrics.com) if you want to interact directly with us.

Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://info-igor.org/attachments/20190521/3a8cf9c6/attachment.html>