mac os x + netcdf + pykst

Barth Netterfield barth.netterfield at
Mon Nov 20 20:11:53 UTC 2017

Ahhh... a Mac OSX user!

We now have a nightly build for Mac OSX:

Triggered by your query, I just updated the kst web site to reflect this.

Can you try that one and let me know

i) if it works at all? (and if you do get it to work, a web-site 
compatible mini-blurb on how to install it? I don't use macs, so I have 
no idea how to install this).

ii) if it had netcdf

iii) if the newest version of pyKst works with it (and if you had to 
make changes, what those changes were).

I will attempt to fix anything you find here.



On 2017-11-19 10:45 PM, Peter Barry wrote:
> Fellow kst-ers,
> I am having a bit of trouble installing/configuring kst on os x, and I 
> hope you can provide some guidance.
> My goal is to use kst to read netCDF files and take advantage of the 
> python scripting using pykst. I’m on a macbook pro running os x 
> 10.10.5, with python 2.7 run from anaconda package with Qt5 installed. 
> Here is what i’ve tried so far:
> - Installed pykst manually, as per the instructions from 
> - this appears to run in an ipython.
> - Installed the kst v2.0.8 .dmg binary, and ran the first scripting 
> example (the sine wave) from the docs, which, after some simple 
> modifications to, worked without issue. However, there 
> appears to be no support for netcdf files (i.e. no netcdf reader shown 
> in Data Sources in Help - Debug Dialog)
> - Installed the v2.0.7 .dmg binary (after uninstalling v2.0.8). This 
> version appears to contain support for netcdf, with the reader present 
> in Data Sources, recognises netcdf format (but config is greyed out) 
> and i’m able to open and view example files. However, when I run the 
> python example script, after a few noSuchFun() calls, kst crashes and 
> closes.
> - Attempted to install from source, but failed. I downloaded the git 
> repo, ran cmake, and got an error after Qt5 was found, which claimed 
> that Qt4 was required.
> Of course, the other option would be to use the dirfile format. 
> However, the application will require writing data from 3000 sensors 
> at a rate of ~500 Hz, and its my understanding that with dirfiles, 
> each sensor would require its own file, and i’m not sure if 3000 open 
> files at once is a good idea (i’m happy to switch if that assumption 
> isn’t valid).
> Any help would be appreciated. Let me know if there is any other 
> information that would be helpful.
> Thanks, Pete

C. Barth Netterfield

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Kst mailing list