The code is not particularly long, but it seems like almost every type has its own module, which makes it harder to get an overview.
A few of the composite types are defined with abstract types as fields, such as FNNyquistPulse. That is not optimal: http://docs.julialang.org/en/latest/manual/performance-tips/#avoid-fields-with-abstract-type On Monday, September 12, 2016 at 2:16:52 PM UTC+2, Steven G. Johnson wrote: > > It would be much easier to give pereformance tips if you could boil it > down to a single self-contained function that you want to make faster, > rather than requiring us to read through four or five different submodules > and lots of little one-line functions and types. (There's nothing wrong > with having lots of functions and types in Julia, it is just that this > forces us to comprehend a lot more code in order to make useful > suggestions.) >
